Prompt
How do I troubleshoot signature completion webhooks not firing?
Latest observation
Nov 3, 2026
OpenAI APIWeb search: off
If “signature completion” webhooks aren’t firing, troubleshoot in this order:
1) Confirm the event actually occurred
- Make sure the signature was fully completed, not just viewed or started.
- Check the envelope/document status in the app/provider dashboard.
- Verify you’re listening for the correct event name (e.g.,
completed,signature_completed,document.completed, etc.).
2) Verify webhook configuration
- Confirm the webhook URL is correct and publicly reachable.
- Check that the webhook is enabled for the right account, environment, or workspace.
- Ensure the specific event type is subscribed.
- If there are separate test and production environments, make sure you’re checking the right one.
3) Check delivery logs
- Look for webhook attempt logs in the provider dashboard.
- Note:
- timestamp of attempts
- HTTP status codes
- response body
- timeout errors
- If there are no attempts at all, the trigger/configuration is likely the issue.
- If attempts exist but fail, your endpoint or network is likely the issue.
4) Validate your endpoint
- Ensure the endpoint returns a
2xxresponse quickly. - Avoid long processing during the request; acknowledge first, process asynchronously.
- Confirm it accepts the expected method, usually
POST. - Check that your server isn’t rejecting payloads because of:
- invalid JSON parsing
- request size limits
- missing headers
- CSRF/auth middleware blocking requests
5) Test reachability
- Verify the endpoint is accessible from the public internet.
- If using localhost, private IPs, VPN-only hosts, or firewalled environments, the provider can’t reach it.
- Use a tunnel like ngrok or a temporary public endpoint for testing.
- Check DNS, SSL cert validity, and firewall rules.
6) Inspect signature verification
- If you validate webhook signatures, make sure:
- the correct secret is configured
- you’re using the raw request body, not a reserialized JSON string
- timestamp tolerance is not too strict
- A failed verification may cause your app to reject the request even if it was delivered.
7) Look for retries or suppression
- Some providers retry failed deliveries; others stop after repeated failures.
- Some suppress events if the same webhook URL has recently failed.
- Check whether the webhook is being rate-limited or deactivated.
8) Reproduce with a test event
- Use the provider’s “send test webhook” or replay feature if available.
- Compare a known-good event with the failing signature-completion event.
- Confirm the payload shape and headers match what your code expects.
9) Check downstream logic
- Sometimes the webhook arrives, but your application discards it because:
- you filter on the wrong document/status ID
- idempotency logic ignores it
- processing errors occur after receipt
- Add logging at request entry and after parsing.
10) Contact support with specifics
Provide:
- webhook URL (or masked domain)
- event type
- timestamp of the signature completion
- any delivery IDs / request IDs
- response codes from your server
- sample payload and headers
If you want, I can help you debug this for a specific platform (DocuSign, Adobe Sign, Dropbox Sign, PandaDoc, etc.) or help you create a quick webhook test checklist/script.