Skip to main content

Retry Behavior

eCourtDate retries a webhook delivery when the endpoint returns a 5xx status. For the outbound_texts and outbound_emails channels, eCourtDate also retries a delivery that times out, cannot connect, or returns 408 or 429.

eCourtDate does not retry a delivery that returns any other 4xx status. A 4xx status tells eCourtDate that the endpoint refuses the payload, so the same request gets the same answer.

To send failed deliveries again by hand, open Webhooks in the Console and use the delivery logs. Each failed delivery can be retried on its own or in bulk.

Endpoint Requirements​

To ensure reliable webhook delivery, the endpoint should follow these guidelines:

  • Return HTTP 200 quickly: respond within a few seconds to avoid timeouts
  • Return 4xx only for a payload that the endpoint must never accept: eCourtDate does not retry it
  • Process asynchronously: if handling the payload requires significant work, queue it for background processing and return 200 immediately
  • Be idempotent: the same event may be delivered more than once due to retries, so ensure the processing logic can safely handle duplicate deliveries
tip

Always return a 200 response immediately, then process the webhook payload in the background. This prevents timeouts and unnecessary retries.

Handling Duplicates​

Use the uuid field in the webhook payload to detect duplicate deliveries. Store processed event UUIDs and skip any that have already been handled.

Next Steps​