Webhooks
What is a Webhook?
A webhook is an automatic notification 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 a court 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 information to you the moment it happens.
Overview
Webhooks deliver real-time event notifications 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.
Use Cases
- Receive inbound messages -- get notified instantly when a text, email, or voice message arrives
- Track delivery status -- monitor outbound message delivery in real time
- Payment notifications -- receive alerts when payments are processed
- Event updates -- stay informed about scheduling and case event changes
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 notifications across text, email, and voice channels |
| Events | Case and scheduling event updates |
| Payments | Payment processing notifications |
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