Elation Health

Elation Health Service Locations API

The Service Locations API from Elation Health — 4 operation(s) for service locations.

GitHub OpenAPI

Operations 12

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /service_locations List service locations (legacy endpoint) · Find Service Location #
Ask an LLM
“What service locations does my practice have, per the legacy endpoint?”
“Can I see all practice addresses from the original service locations path?”
Tell an agent
List my service locations from the legacy endpoint.
Show every practice address on the old service locations path.
POST /service_locations Add a service location (legacy endpoint) · Create Service Location #
Ask an LLM
“How do I add a new office location for my practice through the legacy endpoint?”
“Can I flag a new service location as primary using the original path?”
Tell an agent
Create legacy service location {name} at {address}, {city}, {state} for practice {practice}.
Add an old-endpoint location {name} in {city}, {state} with phone {phone}.
GET /service_locations/{id} Get a service location (legacy endpoint) · Get Service Location #
Ask an LLM
“How do I look up one service location by id on the legacy path?”
“What address and place of service does the original endpoint return for a location?”
Tell an agent
Get legacy service location {id}.
Show location {id} from the older service locations endpoint.
PATCH /service_locations/{id} Change a service location's contact info (legacy) · Update Service Location #
Ask an LLM
“Can I update just the phone or fax of a location with the legacy PATCH?”
“How do I make a different location primary on the unversioned path?”
Tell an agent
Patch legacy location {id} with phone {phone} and fax {fax}.
Set old-endpoint location {id} as primary {primary}.
PUT /service_locations/{id} Replace a service location (legacy PUT) · Update Service Location #
Ask an LLM
“Can I overwrite a whole service location with the legacy PUT?”
“Which legacy call requires resending the full address of a location?”
Tell an agent
Replace legacy service location {id} with address {address}, {city}, {state}.
Overwrite old-endpoint location {id} in full, naming it {name}.
DELETE /service_locations/{id} Delete a service location (legacy endpoint) · Delete Service Location #
Ask an LLM
“How do I remove a closed office location using the legacy endpoint?”
“Can I delete a service location through the original path?”
Tell an agent destructive · confirm first
Delete legacy service location {id}.
Remove location {id} via the old endpoint.
GET /api/2.0/service_locations/ List service locations (v2.0) · List Service Locations #
Ask an LLM
“How do I page through service locations in the 2.0 API?”
“Can I sort version 2.0 service locations?”
Tell an agent
List v2.0 service locations.
List 2.0 service locations ordered by {order_by}, {limit} per page.
POST /api/2.0/service_locations/ Add a service location (v2.0) · Create Service Location #
Ask an LLM
“How do I create a service location with a timezone in version 2.0?”
“Which fields are required for a new location in the 2.0 API?”
Tell an agent
Create v2.0 service location {name} at {address} in {state} for practice {practice}.
Add 2.0 location {name} with place of service code {pos} and timezone {tz}.
DELETE /api/2.0/service_locations/{id}/ Delete a service location (v2.0) · Delete Service Location #
Ask an LLM
“How do I delete a service location through the 2.0 API?”
“Can I remove an office we closed in version 2.0?”
Tell an agent destructive · confirm first
Delete v2.0 service location {id}.
Remove location {id} using the 2.0 endpoint.
GET /api/2.0/service_locations/{id}/ Get a service location (v2.0) · Retrieve Service Location #
Ask an LLM
“How do I fetch one service location in the 2.0 API?”
“Does the v2.0 location record include its timezone and status?”
Tell an agent
Get v2.0 service location {id}.
Retrieve location {id} from the 2.0 API.
PATCH /api/2.0/service_locations/{id}/ Update some service location fields (v2.0) · Partially Update Service Location #
Ask an LLM
“Can I change only a location's timezone in the 2.0 API?”
“Which v2.0 call updates a location's email without resending the address?”
Tell an agent
Patch v2.0 location {id} timezone to {tz}.
Update the email on 2.0 service location {id} to {email}.
PUT /api/2.0/service_locations/{id}/ Replace a service location (v2.0 PUT) · Update Service Location #
Ask an LLM
“Can I fully replace a service location in version 2.0?”
“Which 2.0 call overwrites every service location field?”
Tell an agent
Replace v2.0 service location {id} named {name} at {address}, {state}.
Overwrite 2.0 location {id} for practice {practice}.

Documentation

📖
Documentation
https://docs.elationhealth.com/docs/oauth
📖
APIReference
https://docs.elationhealth.com/reference/get-token
📖
Documentation
https://docs.elationhealth.com/reference/scopes
📖
Documentation
https://docs.elationhealth.com/docs/api-overview
📖
APIReference
https://docs.elationhealth.com/reference
📖
APIReference
https://docs.elationhealth.com/reference/insurance-eligibility
📖
APIReference
https://docs.elationhealth.com/reference/message-threads
📖
Documentation
https://docs.elationhealth.com/docs/webhooks
📖
APIReference
https://docs.elationhealth.com/reference/event-subscriptions
📖
Documentation
https://help.elationhealth.com/articles/rest/overview/api-overview
📖
APIReference
https://help.elationhealth.com/api-reference
📖
Authentication
https://help.elationhealth.com/articles/rest/overview/oauth

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/openapi/elation-health-service-locations-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-service-location-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-patched-service-location-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/json-schema/elation-health-paginated-service-location-list-schema.json

Other Resources

🔗
Webhooks
https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/asyncapi/elation-health-events-webhooks.yml
🔗
OAuthScopes
https://help.elationhealth.com/articles/rest/overview/scopes
🔗
ChangeLog
https://help.elationhealth.com/articles/rest/changelog/changelog

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/elation-health:elation-health-service-locations-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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

OpenAPI Specification

elation-health-service-locations-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Elation Health Service Locations API
  version: '1.0'
  description: 'Operations tagged Service Locations across 2 of this provider''s published API definitions: elation-api-settings.json, elation-health-api-full-openapi.yaml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://sandbox.elationemr.com/api/2.0
- description: Sandbox Server
  url: https://sandbox.elationemr.com
- description: Production Server
  url: https://api.app.elationemr.com
tags:


# --- truncated at 32 KB (53 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/elation-health/refs/heads/main/openapi/elation-health-service-locations-api-openapi.yml