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

Elation Health Cardiac Centers API

The Cardiac Centers API from Elation Health — 4 operation(s) for cardiac centers.

Elation Health Cardiac Centers API is one of 126 APIs that Elation Health publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 4 operations across 4 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 3 base URLs: https://sandbox.elationemr.com/api/2.0, https://sandbox.elationemr.com, https://api.app.elationemr.com.

4 operations 4 paths 2 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.app.elationemr.com/api/2.0
Authentication
OAuth 2.0, OAuth 2.0
Resource Areas
1

Authentication & Security 2

Elation Health Cardiac Centers API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (sec0) using the clientCredentials flow. It supports OAuth 2.0 (oauth2) using the clientCredentials flow, exposing 4 scopes.

Paths & Operations 4

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

Cardiac Centers 4
GET
/cardiac_centers/
Find Cardiac Centers
find-cardiac-centers 4 params → 200400
GET
/cardiac_centers/{id}
Get Cardiac Center
get-cardiac-center 2 params → 200400
GET
/api/2.0/cardiac_centers/
List Cardiac Centers
cardiac_centers_list 6 params → 200
GET
/api/2.0/cardiac_centers/{id}/
Retrieve Cardiac Center
cardiac_centers_retrieve 1 param → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are CardiacCenter (14 properties), PaginatedCardiacCenterList (4 properties). Each schema is shown below with its type and property counts.

PaginatedCardiacCenterList
object
4 properties 1 required
CardiacCenter
object
14 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

elation-health-cardiac-centers-api-openapi.yml Raw ↑

Other APIs Elation Health publishes across the network.

Elation Health Allergies API
Elation Health Appointments API
Elation Health Authentication API
Elation Health Billing API
Elation Health Insurance API
Elation Health Lab Orders API
Elation Health Medications API
Elation Health Messaging API
Elation Health Patients API
Elation Health Physicians API
Elation Health Practices API
Elation Health Problems API
Where this information came from

This is an independent, third-party profile of Elation Health Cardiac Centers 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.