Skip to main content

Event Types

Webhooks deliver structured JSON payloads to the endpoint via HTTP POST. This page describes the payload format and the available event categories.

Payload Structure​

The following is an example payload for an inbound message event:

{
  "uuid": "webhook-event-uuid",
  "channel": "text",
  "direction": "inbound",
  "created_at": "2024-01-15T10:30:00Z",
  "from": "+15551234567",
  "to": "+15559876543",
  "content": "Message content here",
  "token": "token-identifier",
  "last_status": "delivered"
}

Field Reference​

FieldTypeDescription
uuidstringUnique event identifier
channelstringCommunication channel: text, email, or voice
directionstringinbound or outbound
created_atstringISO 8601 timestamp of when the event was created
fromstringSender identifier (phone number, email address, etc.)
tostringRecipient identifier (phone number, email address, etc.)
contentstringMessage body
tokenstringToken identifier associated with the event
last_statusstringCurrent delivery status of the message

Event Categories​

Messages​

Message events fire for inbound and outbound communications across all supported channels:

  • Text: SMS and MMS messages
  • Email: inbound and outbound email
  • Voice: voice call events

Events​

Event notifications are triggered by scheduling and case event updates within the system.

Payments​

Payment events are delivered when payment transactions are processed.

Checkins​

Checkin events fire when individuals check in to scheduled appointments, court dates, or other tracked events.

Form Submissions​

Form submission events are triggered when a form is completed and submitted through an eCourtDate portal or link.

Chatbot Chats​

Chatbot chat events fire for conversations handled by eCourtDate AI chatbots, including new chats, messages, and session completions.

Separate from the standalone Chatbots API

These events cover the AI chatbots built into the eCourtDate platform. The standalone Chatbots API has its own webhooks, ingest.completed and crawl.completed, which report knowledge-base indexing jobs and are signed with an X-ECD-Signature header rather than the platform signature described in Verification.

Warrants​

Warrant events fire when electronic warrants are created, updated, signed, or served.

Citations​

Citation events fire when citations are issued, updated, or resolved.

Electronic Signatures​

Electronic signature events fire when signature requests are sent, viewed, signed, or declined.

Next Steps​