Generated by API Evangelist
Written by API Evangelist tooling for Elation Health's API. It is a proposal applied on top of the contract, not a document Elation Health publishes.
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
title: API Evangelist conversational phrasing for Elation Health Cardiac Centers API
version: 1.0.0
extends: openapi/elation-health-cardiac-centers-api-openapi.yml
actions:
- target: $.info
update:
x-apievangelist-phrasing:
method: generated
generated: '2026-09-26'
generator: build-phrasing.py
label: Generated by API Evangelist
operations: 4
- target: $.paths['/cardiac_centers/'].get
update:
x-apievangelist-phrasing:
intent: Find cardiac centers (legacy)
effect: read
questions:
- How do I find cardiac testing centers by company on the older endpoint?
- Can I search legacy cardiac centers by location name?
instructions:
- text: Find legacy cardiac centers run by company {company}.
slots:
company: query.company
- text: Search older cardiac centers at location {location_name} for practice {practice}.
slots:
location_name: query.location_name
practice: query.practice
method: generated
generated: '2026-09-26'
- target: $.paths['/cardiac_centers/{id}'].get
update:
x-apievangelist-phrasing:
intent: Get a cardiac center (legacy)
effect: read
questions:
- How do I look up one cardiac center by ID on the older route?
- Where is a given legacy cardiac center located?
instructions:
- text: Get legacy cardiac center {id}.
slots:
id: path.id
- text: Show the address of older cardiac center record {id}.
slots:
id: path.id
method: generated
generated: '2026-09-26'
- target: $.paths['/api/2.0/cardiac_centers/'].get
update:
x-apievangelist-phrasing:
intent: List cardiac centers with paging
effect: read
questions:
- How do I page through cardiac centers in the v2.0 API?
- Can I sort /api/2.0 cardiac centers?
instructions:
- text: List v2.0 cardiac centers for company {company}, {limit} per page.
slots:
company: query.company
limit: query.limit
- text: Page through /api/2.0 cardiac centers from offset {offset} ordered by {order_by}.
slots:
offset: query.offset
order_by: query.order_by
method: generated
generated: '2026-09-26'
- target: $.paths['/api/2.0/cardiac_centers/{id}/'].get
update:
x-apievangelist-phrasing:
intent: Retrieve a cardiac center from v2.0
effect: read
questions:
- How do I fetch a single cardiac center by ID from /api/2.0?
- What details come back for one v2.0 cardiac center?
instructions:
- text: Retrieve v2.0 cardiac center {id}.
slots:
id: path.id
- text: Pull the /api/2.0 details for cardiac site {id}.
slots:
id: path.id
method: generated
generated: '2026-09-26'
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.