Elation Health Contacts API

The Contacts API from Elation Health — 8 operation(s) for contacts.

Documentation GitHub OpenAPI

Operations 14

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 /contacts/search/ Search referral contacts (legacy endpoint) · Search Contacts #

Ask an LLM

“Can I search my referral contacts by specialty and state with the older contacts search endpoint?”

“Is there a legacy way to look up outside providers by name and city?”

Tell an agent

Using the legacy contacts search, find contacts matching {q} in {city}.

Run the older contact search for {specialties} specialists in state {state}.

POST /contacts/ Add a referral contact (legacy endpoint) · Create Contact #

Ask an LLM

“How do I add an outside physician to my contacts through the legacy create endpoint?”

“Can I record a specialist's fax and Direct address when creating a contact the old way?”

Tell an agent

Through the legacy endpoint, add contact {first_name} {last_name} with specialty {specialty}.

Create an old-style contact for {first_name} {last_name} with fax {fax} and Direct address {direct_address}.

GET /contacts/ List contacts by NPI (legacy endpoint) · List Contacts #

Ask an LLM

“How do I look up a contact by NPI number on the legacy contacts list?”

“Can the original contacts listing filter on a provider's NPI?”

Tell an agent

On the legacy contacts list, find the contact with NPI {npi}.

Pull the old-style contacts listing for my practice.

PUT /contacts/{id}/ Replace a contact's details (legacy PUT) · Update Contacts #

Ask an LLM

“How do I overwrite every field on a contact with the legacy PUT endpoint?”

“Can I mark an existing contact as accepting new patients through the older full update?”

Tell an agent

With the legacy PUT, replace contact {id} so its phone is {phone} and email is {email}.

Fully rewrite legacy contact {id} with address {address}, {city}, {state} {zip}.

PATCH /contacts/{id}/ Patch a contact's details (legacy PATCH) · Update Contacts #

Ask an LLM

“Can I change just one field on a contact using the legacy PATCH endpoint?”

“What's the older way to fix a contact's fax number without resending everything?”

Tell an agent

Using the legacy PATCH, change the fax on contact {id} to {fax}.

Patch legacy contact {id} to set accepting new patients to {accepting_new_patients}.

DELETE /contacts/:id/ Delete a contact (legacy endpoint) · Delete Contacts #

Ask an LLM

“Is there a legacy endpoint for removing a contact from my address book?”

“Can the older contacts API delete an outdated referral contact?”

Tell an agent destructive · confirm first

Remove the outdated contact through the legacy delete endpoint.

Delete that old referral contact with the original contacts API.

GET /contacts/{contact_id}/ Fetch one contact (legacy endpoint) · Fetch Contact #

Ask an LLM

“How do I fetch a single contact by its contact ID on the legacy path?”

“What details does the older fetch-contact endpoint return for one provider?”

Tell an agent

Fetch contact {contact_id} from the legacy contacts endpoint.

Show me the old-style record for contact {contact_id}.

GET /api/2.0/contacts/ List contacts in API 2.0 · List Contacts #

Ask an LLM

“How do I page through all my practice's contacts in the 2.0 API?”

“Can the API 2.0 contacts list be narrowed to one NPI?”

Tell an agent

List my contacts in API 2.0, {limit} at a time starting at offset {offset}.

In the 2.0 contacts list, find whoever has NPI {npi}.

POST /api/2.0/contacts/ Create a contact in API 2.0 · Create Contact #

Ask an LLM

“How do I create a new referral contact with the 2.0 API?”

“Which fields are required to add a contact, like credentials and contact type?”

Tell an agent

In API 2.0, create a {contact_type} contact {first_name} {middle_name} {last_name}, {credentials}, for practice {practice}.

Add organization {org_name} as a 2.0 contact with NPI {npi} and phone {phone}.

GET /api/2.0/contacts/search/ Search contacts in API 2.0 · Search Contacts #

Ask an LLM

“Can I search the 2.0 contacts directory for cardiologists in a given city?”

“How do I find a referral contact by name with the current search endpoint?”

Tell an agent

Search API 2.0 contacts for {q}, returning {limit} results.

Find 2.0 contacts specializing in {specialties} located in {city}, {state}.

DELETE /api/2.0/contacts/{id}/ Delete a contact in API 2.0 · Delete Contact #

Ask an LLM

“How do I permanently delete a contact with the 2.0 API?”

“Can I remove a duplicate referral contact by its ID?”

Tell an agent destructive · confirm first

Delete API 2.0 contact {id}.

Remove duplicate contact {id} from the 2.0 directory.

GET /api/2.0/contacts/{id}/ Retrieve a contact in API 2.0 · Retrieve Contact #

Ask an LLM

“How do I get one contact's full details by ID in the 2.0 API?”

“Does retrieving a contact show whether they accept insurance?”

Tell an agent

Retrieve API 2.0 contact {id}.

Get the specialty and fax for 2.0 contact {id}.

PATCH /api/2.0/contacts/{id}/ Partially update a contact in API 2.0 · Partially Update Contact #

Ask an LLM

“Can I update only a contact's email in the 2.0 API without replacing the whole record?”

“How do I flag a contact as verified with a partial update?”

Tell an agent

In API 2.0, change only the email on contact {id} to {email}.

Partially update 2.0 contact {id} to set is_verified to {is_verified}.

PUT /api/2.0/contacts/{id}/ Replace a contact in API 2.0 · Update Contact #

Ask an LLM

“How do I replace an entire contact record in the 2.0 API?”

“Which fields must I resend when doing a full contact replacement?”

Tell an agent

Replace 2.0 contact {id} as {contact_type} {first_name} {middle_name} {last_name}, {credentials}, at practice {practice}.

Overwrite API 2.0 contact {id} with the corrected NPI {npi}.

Elation Health Contacts API

Operations 14

Documentation

Specifications

Schemas & Data

Other Resources

Work with this as data

MCP server

Tools for apis

Call it yourself

Get an API key

OpenAPI Specification