Troubleshooting
If your webhook endpoint is failing it could be due to some of the common causes listed below.
Not using the raw payload body
We generate signatures based on the raw payload body in the message request.
When verifying signatures it’s important to use the payload exactly as it was sent rather than modifying the payload.
Not using the correct signing secret
Check that you are using the correct signing secret when verifying signatures.
Keep in mind that signing secrets are different for each API endpoint.
Responding with incorrect status codes
Responding with a 2XX status code indicates successful processing even if you indicate a failure elsewhere in the response.
Make sure to respond with status codes that appropriately indicate success or failure.
Responses timing out
If your endpoint takes a long time to respond, it might timeout and be considered failed.
In such cases, we recommend your endpoint queue the webhook request for asynchronous processing so that it can respond promptly without timing out.
Updated 7 months ago