Elation Health · OpenAPI Overlay 1.0.0
API Evangelist conversational phrasing for Elation Health Thread Members API
12 actions
12 updates
phrasing
extends
openapi/elation-health-thread-members-api-openapi.yml
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.
What the actions change
x-apievangelist-phrasing
Targets 12
$.info
$.paths['/thread_members/{id}/'].get
$.paths['/thread_members/{id}/'].patch
$.paths['/thread_members/'].get
$.paths['/thread_members/'].post
$.paths['/thread_members/{id}'].delete
$.paths['/api/2.0/thread_members/'].get
$.paths['/api/2.0/thread_members/'].post
$.paths['/api/2.0/thread_members/{id}/'].get
$.paths['/api/2.0/thread_members/{id}/'].put
$.paths['/api/2.0/thread_members/{id}/'].delete
$.paths['/api/2.0/thread_members/{id}/'].patch
OpenAPI Overlay
# 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 Thread Members API
version: 1.0.0
extends: openapi/elation-health-thread-members-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: 11
- target: $.paths['/thread_members/{id}/'].get
update:
x-apievangelist-phrasing:
intent: Get a message thread member (legacy endpoint)
effect: read
questions:
- Can I look up one participant of a message thread on the legacy path?
- Does the older thread member lookup show when they acknowledged the message?
instructions:
- text: Open thread member {id} using the legacy endpoint.
slots:
id: path.id
- text: Show the status of old-path thread member {id}.
slots:
id: path.id
method: generated
generated: '2026-09-26'
- target: $.paths['/thread_members/{id}/'].patch
update:
x-apievangelist-phrasing:
intent: Update a thread member's status (legacy PATCH)
effect: write
questions:
- How do I mark a message thread as acknowledged for a member with the legacy PATCH?
- Can the older endpoint record the time a staff member acknowledged a thread?
instructions:
- text: Using the legacy PATCH, set thread member {id} to status {status}.
slots:
id: path.id
status: requestBody.status
- text: Record that old-path thread member {id} acknowledged at {ack_time}.
slots:
id: path.id
ack_time: requestBody.ack_time
method: generated
generated: '2026-09-26'
- target: $.paths['/thread_members/'].get
update:
x-apievangelist-phrasing:
intent: Find thread members (legacy endpoint)
effect: read
questions:
- Which message threads is a given user a member of, per the legacy search?
- Can I find thread members for a patient who haven't acknowledged yet with the older lookup?
instructions:
- text: Using the legacy lookup, find thread members for user {user} with status {status}.
slots:
user: query.user
status: query.status
- text: Find old-path thread members on patient {patient}'s threads in group {group}.
slots:
patient: query.patient
group: query.group
method: generated
generated: '2026-09-26'
- target: $.paths['/thread_members/'].post
update:
x-apievangelist-phrasing:
intent: Add someone to a message thread (legacy endpoint)
effect: write
questions:
- How do I add a user to an existing message thread through the legacy endpoint?
- Can I add a whole staff group to a thread the old way?
instructions:
- text: Via the legacy endpoint, add user {user} to thread {thread}.
slots:
user: requestBody.user
thread: requestBody.thread
- text: Add group {group} as an old-path member of thread {thread}.
slots:
group: requestBody.group
thread: requestBody.thread
method: generated
generated: '2026-09-26'
- target: $.paths['/thread_members/{id}'].delete
update:
x-apievangelist-phrasing:
intent: Remove a thread member (legacy endpoint)
effect: destructive
questions:
- Is there a legacy call to take someone off a message thread?
- What happens when I delete a thread member on the original path?
instructions:
- text: Delete thread member {id} with the legacy endpoint.
slots:
id: path.id
- text: Take old-path member {id} off the message thread.
slots:
id: path.id
method: generated
generated: '2026-09-26'
- target: $.paths['/api/2.0/thread_members/'].get
update:
x-apievangelist-phrasing:
intent: List thread members in API 2.0
effect: read
questions:
- How do I list everyone on a specific message thread in the 2.0 API?
- Can API 2.0 filter thread members by acknowledgment status?
instructions:
- text: List 2.0 members of thread {thread}.
slots:
thread: query.thread
- text: List API 2.0 thread members for user {user} with status {status}, {limit} per page.
slots:
user: query.user
status: query.status
limit: query.limit
method: generated
generated: '2026-09-26'
- target: $.paths['/api/2.0/thread_members/'].post
update:
x-apievangelist-phrasing:
intent: Create a thread member in API 2.0
effect: write
questions:
- How do I add a participant to a message thread with the 2.0 API?
- Is a status required when adding a new thread member?
instructions:
- text: In API 2.0, add user {user} to thread {thread} with status {status}.
slots:
user: requestBody.user
thread: requestBody.thread
status: requestBody.status
- text: Create a 2.0 thread membership for group {group} with status {status}.
slots:
group: requestBody.group
status: requestBody.status
method: generated
generated: '2026-09-26'
- target: $.paths['/api/2.0/thread_members/{id}/'].get
update:
x-apievangelist-phrasing:
intent: Retrieve a thread member in API 2.0
effect: read
questions:
- How do I retrieve a single thread member by ID in API 2.0?
- Does a 2.0 thread member show which thread it belongs to?
instructions:
- text: Retrieve API 2.0 thread member {id}.
slots:
id: path.id
- text: Get the thread and acknowledgment time of 2.0 member {id}.
slots:
id: path.id
method: generated
generated: '2026-09-26'
- target: $.paths['/api/2.0/thread_members/{id}/'].put
update:
x-apievangelist-phrasing:
intent: Replace a thread member in API 2.0
effect: write
questions:
- Can I replace a thread member record in full with a 2.0 PUT?
- What does a full thread member replacement require?
instructions:
- text: Replace 2.0 thread member {id} with status {status}.
slots:
id: path.id
status: requestBody.status
- text: 'Overwrite API 2.0 thread member {id}: user {user}, thread {thread}, status {status}.'
slots:
id: path.id
user: requestBody.user
thread: requestBody.thread
status: requestBody.status
method: generated
generated: '2026-09-26'
- target: $.paths['/api/2.0/thread_members/{id}/'].delete
update:
x-apievangelist-phrasing:
intent: Delete a thread member in API 2.0
effect: destructive
questions:
- How do I remove a participant from a thread in the 2.0 API?
- Can I delete a thread membership by its ID in API 2.0?
instructions:
- text: Delete API 2.0 thread member {id}.
slots:
id: path.id
- text: Remove 2.0 membership {id} from its message thread.
slots:
id: path.id
method: generated
generated: '2026-09-26'
- target: $.paths['/api/2.0/thread_members/{id}/'].patch
update:
x-apievangelist-phrasing:
intent: Partially update a thread member in API 2.0
effect: write
questions:
- Can I set only the acknowledgment time on a thread member in API 2.0?
- Is there a 2.0 PATCH to change a thread member's status?
instructions:
- text: Patch 2.0 thread member {id} with ack time {ack_time}.
slots:
id: path.id
ack_time: requestBody.ack_time
- text: Partially update API 2.0 thread member {id} to status {status}.
slots:
id: path.id
status: requestBody.status
method: generated
generated: '2026-09-26'
Work with this as data
Every overlay 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 openapi overlays
4 MCP tools reach this
find_overlaysBrowse and filter every overlay in the catalog.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.
Call it yourself
curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/elation-health-thread-members-api-phrasing-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?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.
A second provider on the same verified email joins the account you already have.