AsyncAPI channel · August Health
· August Health Webhooks
{subscriberEndpoint}
HTTPS endpoint registered by the integration partner in the webhooks portal.
Channel address
{subscriberEndpoint}
Operations
receive
receiveEvents
Receive August Health EHR events on a subscribed endpoint.
Messages
billing.statement_issued
Billing statement issued
Content-Type:
person.admission_created
Resident admission created
Content-Type:
person.admission_deleted
Resident admission deleted
Content-Type:
person.admission_updated
Resident admission updated
Content-Type:
person.admissions_agreement_completed
Admission agreement completed
Content-Type:
person.assessment_finalized
Assessment finalized
Content-Type:
person.away
Resident marked away
Content-Type:
person.diet_changed
Resident diet changed
Content-Type:
person.discharge_created
Resident discharge created
Content-Type:
person.discharge_deleted
Resident discharge deleted
Content-Type:
person.discharge_updated
Resident discharge updated
Content-Type:
person.level_of_care_changed
Resident level of care changed
Content-Type:
person.return
Resident returned
Content-Type:
person.room_transfer
Resident room transfer
Content-Type:
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.
Work with this as data
Every channel here is available over the APIs.io API and to AI agents over MCP.