Webhooks
What is a Webhook?
A webhook is an automated HTTP POST that eCourtDate sends to your system when something happens. For example, when a message is delivered, a payment is received, or a reply comes in. Think of it like a doorbell: instead of repeatedly checking whether someone is at the door (which is what polling the API would be), the doorbell rings and tells you right away.
When would an agency need webhooks? If you want your case management system or internal tools to react in real time to eCourtDate events (such as logging delivery confirmations, flagging failed messages, or triggering follow-up actions), webhooks deliver that data to you the moment it happens.
Overview
Webhooks deliver real-time event payloads from eCourtDate to your application via HTTP POST requests. Instead of polling the API for updates, webhooks push data to your endpoint as events occur.
Data Flow
Use Cases
- Receive inbound messages: get payloads instantly when a text, email, or voice message arrives
- Track delivery status: monitor outbound message delivery in real time
- Payment processing: receive payloads when payments are processed
- Event updates: stay informed about scheduling and case event changes
- Checkins: track when individuals check in to appointments or court dates
- Form submissions: receive completed form data from portals
- Chatbot chats: get payloads for AI chatbot conversations
- Warrants & Citations: track warrant and citation lifecycle events
- Electronic signatures: receive payloads when documents are signed or declined
Getting Started
Webhooks are configured in the eCourtDate Console under the Webhooks section. From there you can create webhooks, assign them to agencies, configure endpoint URLs, and manage shared secrets for signature verification.
Supported Event Categories
| Category | Description |
|---|---|
| Messages | Inbound and outbound payloads across text, email, and voice channels |
| Events | Case and scheduling event updates |
| Payments | Payment processing payloads |
| Checkins | Appointment and court date check-in events |
| Form Submissions | Completed form data from portals and links |
| Chatbot Chats | AI chatbot conversations, messages, and session completions |
| Warrants | Electronic warrant creation, signing, and service events |
| Citations | Citation issuance, updates, and resolution events |
| Electronic Signatures | Signature requests sent, viewed, signed, or declined |
Next Steps
- Configuration: set up your first webhook
- Security: secure your webhook endpoint
- Event Types: explore the payload structure
- Signature Verification: verify webhook authenticity
- Implementation Examples: build a complete webhook server