How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
EMIS Health

EMIS Health CORS API

The CORS API from EMIS Health — 40 operation(s) for cors.

Documentation Provider Profile APIs.io OpenAPI GitHub

EMIS Health CORS API is one of 12 APIs that EMIS Health publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include CORS. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 40 operations across 40 paths. It is described by OpenAPI 3.2.0, at version 1.2.

Requests are made against the base URL https://api.platform.emis-x.uk/partner.

40 operations 40 paths 0 schemas 40 OPTIONS

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.2
Base URL
https://api.platform.emis-x.uk/partner
Authentication
HTTP Bearer, OAuth 2.0
Resource Areas
1

Authentication & Security 2

EMIS Health CORS API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer). It supports OAuth 2.0 (OAuth2CodeEMIS-X-GP-PAPI) using the authorizationCode flow, exposing 7 scopes.

Paths & Operations 40

Across 40 paths, the API surfaces 40 operations — 40 OPTIONS. Each is listed below with its method, path, parameters, and response codes.

CORS 40
OPTIONS
/api/v1/appointments/BookAppointment
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/CancelAppointment
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/GetAppointmentConfiguration
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/GetAppointmentSessions
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/GetArrivedPatients
CORS pre-flight request
→ 204
OPTIONS
/api/v1/medicalRecord/GetAttachments
CORS pre-flight request
→ 204
OPTIONS
/api/v1/medicalRecord/GetAttachmentsV2
CORS pre-flight request
→ 204
OPTIONS
/api/v1/medicalRecord/GetBase64AttachmentData
CORS pre-flight request
→ 204
OPTIONS
/api/v1/medicalRecord/GetBase64AttachmentDataV2
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/GetBookedPatients
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/GetBookedPatientsV2
CORS pre-flight request
→ 204
OPTIONS
/api/v1/patientMatching/GetChangedPatients
CORS pre-flight request
→ 204
OPTIONS
/api/v1/patientMatching/GetChangedPatientsMR
CORS pre-flight request
→ 204
OPTIONS
/api/v1/medicalRecord/GetCodedRecord
CORS pre-flight request
→ 204
OPTIONS
/api/v1/medicalRecord/GetConsultation
CORS pre-flight request
→ 204
OPTIONS
/api/v1/medicalRecord/GetEvents
CORS pre-flight request
→ 204
OPTIONS
/
CORS pre-flight request
→ 204
OPTIONS
/api/v1/patientMatching/GetMatchedPatients
CORS pre-flight request
→ 204
OPTIONS
/api/v1/medicalRecord/GetMedicalRecord
CORS pre-flight request
→ 204
OPTIONS
/api/v1/medicalRecord/GetMedicationIssues
CORS pre-flight request
→ 204
OPTIONS
/api/v1/organisation/GetOrganisation
CORS pre-flight request
→ 204
OPTIONS
/api/v1/organisation/GetOrganisationV2
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/GetPatientAppointments
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/GetPatientAppointmentsV2
CORS pre-flight request
→ 204
OPTIONS
/api/v1/patient/GetPatientDemographics
CORS pre-flight request
→ 204
OPTIONS
/api/v1/search/GetPatientSearches
CORS pre-flight request
→ 204
OPTIONS
/api/v1/patientMatching/GetPatientSequence
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/GetSentInPatients
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/GetSlotsForSession
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/GetSlotsForSessionV2
CORS pre-flight request
→ 204
OPTIONS
/api/v1/user/GetUserById
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/AddSlotComment
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/SetAppointmentStatus
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/SetAppointmentStatusEx
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/SetSlotNotes
CORS pre-flight request
→ 204
OPTIONS
/api/v1/appointments/SetSlotType
CORS pre-flight request
→ 204
OPTIONS
/api/v1/medicalRecord/UpdateAttachment
CORS pre-flight request
→ 204
OPTIONS
/api/v1/medicalRecord/UpdateConsultationVisibility
CORS pre-flight request
→ 204
OPTIONS
/api/v1/medicalRecord/FileRecord
CORS pre-flight request
→ 204
OPTIONS
/swagger/*
CORS pre-flight request
→ 204

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emis-health-cors-api-openapi.yml Raw ↑

Other APIs EMIS Health publishes across the network.

EMIS-X App Launch
AE Profile APIs.io
EMIS-X Analytics
AE Profile APIs.io
EMIS Health Appointments API
AE Profile APIs.io
EMIS Health Health API
AE Profile APIs.io
EMIS Health Medical Record API
AE Profile APIs.io
EMIS Health Organisation API
AE Profile APIs.io
EMIS Health Patient API
AE Profile APIs.io
EMIS Health Patient Matching API
AE Profile APIs.io
EMIS Health Search API
AE Profile APIs.io
EMIS Health Swagger API
AE Profile APIs.io
EMIS Health User API
AE Profile APIs.io
#CORS
← Back to E APIs
API Details
ID
emis-health:emis-health-cors-api
Base URL
https://api.platform.emis-x.uk/partner
Docs
https://docs.partner.emis-x.uk/papi-overview
Provider
EMIS Health
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=emis-health-cors-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/emis-health-cors-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of EMIS Health CORS API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.