1
Is the provider pointed at the right URL?
Check that the provider is sending to your endpoint’s exact ingest URL (
https://wbhk.my/…). A
trailing slash or an extra query parameter can matter for providers that sign the URL. Find the
URL on the endpoint’s page.2
Is the endpoint paused?
A paused endpoint answers new requests with a
429 so the provider holds and retries rather
than dropping the event. If you see a “Capture is paused” banner, you’ve either paused the
endpoint or hit your usage cap — resume or raise your limit so
new requests are captured again. (webhook.co doesn’t buffer requests while paused; the retryable
429 is what makes a well-behaved provider redeliver.)3
Did the provider actually send it?
Check the provider’s own webhook/delivery logs. If the provider shows a delivery to your URL,
the event should appear in webhook.co almost immediately — capture happens before anything else.
If the provider shows nothing, the issue is on their side or in their configuration.
4
Are events arriving but looking wrong?
If events are arriving but show
unattempted or failed
verification, they were still captured — capture
never depends on a valid signature. That’s a verification issue, not a delivery one.Remember capture is durable-first: a request that reaches your ingest URL is stored before
it’s verified or processed, so a bad signature or unknown provider labels an event rather than
losing it. If a request truly reached
wbhk.my, it’s captured.Related
A delivery failed
If it’s the outbound side that’s failing.
Usage alerts & caps
If capture is paused.