Use Cases
- Debug webhook delivery issues
- Audit webhook event history
- Recover missed webhook events after downtime
- Verify event payloads during integration testing
Common Event Types
patient.insurance.added
- Insurance successfully added to patientpatient.insurance.failed
- Insurance addition failedappointment.created
- Appointment createdappointment.updated
- Appointment updatednote.created
- Clinical note created
Query Parameters
- event_type (string, optional): Filter by event type (e.g., “patient.insurance.added”, “appointment.created”)
- status (string, optional): Filter by event status (“success”, “failed”, “pending”)
- start_date (string, optional): Filter events created on or after this date (ISO 8601 format: YYYY-MM-DD)
- end_date (string, optional): Filter events created on or before this date (ISO 8601 format: YYYY-MM-DD)
- page (integer, optional): Page number (default: 1, min: 1)
- page_size (integer, optional): Number of events per page (default: 50, max: 100)
- sort (string, optional): Sort order. Use “created” for ascending (oldest first) or “-created” for descending (newest first). Default: “-created”
Example Requests
Get Recent Events
Filter by Event Type
Filter by Date Range
Filter by Status
Get Page 2
Example Response
Response Fields
Top-Level Fields
- success (boolean): Whether the request was successful
- webhook_events (array): Array of webhook event objects
- pagination (object): Pagination metadata
Event Object Fields
- event_id (string): Unique event identifier
- access_token_reference_id (string): The reference ID associated with your access token
- created_at (string): ISO 8601 timestamp of event creation
- event_type (string): Event type (e.g., “patient.insurance.added”, “appointment.created”)
- job_id (string): Job ID if this event is related to an asynchronous operation
- webhook_url (string): The URL the event was sent to.
- status (string): Event status (“success”, “failed”, “pending”). This refers to whether the event was delivered to your endpoint.
- data (object): Event-specific payload data
Pagination Object
- current_page (integer): Current page number
- total_pages (integer): Total number of pages
- total_count (integer): Total number of events matching the filter
- page_size (integer): Number of items per page
The
data
field in each event contains event-specific information that varies depending on the event type. Refer to the webhook events documentation for details on each event type’s payload structure.Pagination
This endpoint supports page-based pagination:- Make an initial request with optional
page
andpage_size
parameters - Check the
pagination
object in the response fortotal_pages
- Request subsequent pages by incrementing the
page
parameter - Continue until you reach
total_pages
Authorizations
Query Parameters
Filter by event type (e.g., "patient.insurance.added", "appointment.created")
Filter by event status
Available options:
success
, failed
, pending
Filter events created on or after this date (ISO 8601 format: YYYY-MM-DD)
Filter events created on or before this date (ISO 8601 format: YYYY-MM-DD)
Page number (default: 1, min: 1)
Required range:
x >= 1
Number of events per page (default: 50, max: 100)
Required range:
1 <= x <= 100
Sort order. Use 'created' for ascending (oldest first) or '-created' for descending (newest first). Default: '-created'
Available options:
created
, -created