Webhooks or inbound replies are not arriving

Missing inbound traffic is nearly always registration or endpoint health.

1. Confirm the inbound URL registered on the channel.
2. Confirm your endpoint returns 2xx quickly — a slow response counts as a failure and is retried.
3. Confirm TLS is valid and the host is publicly reachable.
4. Inspect the retry log for response codes.
5. If you verify signatures, hash the raw request body; re-serialising the JSON changes the bytes and breaks the comparison.

Design for retries

Webhook deliveries can repeat. Make your handler idempotent on the provider message ID so a retry does not create a duplicate record.

Steps at a glance

1. Confirm the webhook is registeredCheck the inbound URL registered on the channel in Settings → Channels.
2. Check endpoint healthYour endpoint must return 2xx quickly; slow responses are treated as failures and retried.
3. Check TLS and reachabilityA valid certificate and a publicly reachable host are required — self-signed certificates are rejected.
4. Inspect the retry logReview recent delivery attempts and response codes in the channel log.
5. Verify signature handlingIf you verify signatures, confirm you hash the raw body, not a re-serialised copy.