Skip to main content

Webhook Troubleshooting

This page covers testing methods and solutions for common webhook integration issues.

Testing The Webhook​

Console Test Request​

Use the "Test Request" button in the Console Webhooks section to send a test webhook payload to the endpoint. This is the quickest way to verify the server is reachable and responding correctly.

Send and Receive Messages​

Send or receive messages to the Agency phone number or email address. This triggers real webhook events and validates the full end-to-end flow.

Staging Limitations​

Staging environments only support inbound channels. Use production webhooks or the Console test feature to validate outbound event handling.

Common Issues​

Signature Mismatch​

  • Compute the HMAC-SHA256 on the raw request body, not a parsed and re-serialized version. Parsing and re-serializing JSON can change whitespace or key order, producing a different hash.
  • Verify the shared secret in the application matches the value configured in the Console.
  • Confirm the secret is 24 characters or fewer.

Timeout​

  • Return HTTP 200 immediately upon receiving the request.
  • Move any time-consuming processing (database writes, API calls, etc.) to a background job or queue.

IP Blocked​

  • Verify that the webhook IP addresses listed in the Console are added to the firewall or application-level allowlist.
  • Behind a CDN or load balancer, ensure the original client IP is forwarded correctly (check the X-Forwarded-For header).

No Events Received​

  • Confirm the webhook is enabled in the Console.
  • Verify the webhook URL is correct and publicly accessible from the internet.
  • Check that an Agency is assigned to the webhook if the configuration requires one.
  • Review the server logs for incoming requests that may be rejected before reaching the application logic.

Getting Help​

To request help, create a support ticket in the Console: sign in, click the Help button in the bottom-right corner, and complete the Create a Ticket form (Region, Agency, Feature, and a Description). The current page is attached automatically, and updates appear under My Tickets in the same panel.

In the description, include the webhook name and URL, the response code the endpoint returned, whether the webhook is enabled and has an agency assigned, and the approximate time of the issue.

Check status.ecourtdate.com for platform incidents.

danger

Never share the webhook shared secret in a support ticket or logs.

See Also​