# Receive third-party webhooks without losing or repeating them

> Receive third-party webhooks without losing or repeating them: 2 companies fully do it, 3 with a limit, 7 carry the tag. Every listing in Event delivery & webhooks with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/webhooks.receive-reliably/
- Markdown: https://www.anchorterminal.com/niches/webhooks.receive-reliably/index.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/niches/webhooks.receive-reliably/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/webhooks.receive-reliably/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 3 | 7 | 26 | 11 |

## What counts as done

Each event is verified against its signature on the raw body, acknowledged within the provider's timeout, stored, processed once by event id, and a failed one can be listed and replayed from a delivery log.

How agents ask for it: set up a Stripe webhook endpoint; we are missing webhook events; verify this webhook signature; replay the events that failed last night

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Convoy (Frain Technologies Inc.)**: Sources verify incoming webhooks (HMAC, basic, API key), take an idempotency key from parts of the request, store each event, and event deliveries can be listed, retried and force-retried by API.
- **Hookdeck (Hookdeck Technologies Inc.)**: Sources verify HMAC, provider and Standard Webhooks signatures, events are queued and delivered with a configurable timeout, deduplication rules drop repeats within 1 second to 1 hour, and failed events are listed and retried or bulk-retried.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Svix (Svix Inc.)**: The API reference lists Ingest Source and Ingest Endpoint for receiving webhooks, with resend and recover APIs and delivery logs, but the ingest verification and dedup behaviour was not documented in the pages read.
- **Upstash QStash (Upstash, Inc.)**: A sender can post to a QStash publish URL, which stores, retries and logs the message with DLQ retry, but QStash does not verify the original sender's signature, and the token then rides in the URL.
- **Webhook Relay (AppScension Ltd)**: Inputs persist each webhook before delivery and retry durably for up to 30 days, with per-delivery logs, retry and recover; but dedup on the provider's event id and inbound signature checks were not documented in the pages read.

- not this job: 402cron (Georgi Kalchev (operator, a named person; no company named)): A scheduler that sends to the agent's own endpoint; it does not receive or store third-party webhooks.
- not this job: Ably (Ably Realtime Ltd): Ably's inbound webhooks publish a request onto a channel; there is no verification of the sender's signature scheme, dedup by provider event id or delivery log to replay from.
- not this job: Amazon EventBridge (Amazon Web Services, Inc.): No public webhook endpoint that verifies a sender's signature; third-party webhooks need a Lambda URL or API Gateway in front, so EventBridge only stores and replays what that code publishes.
- not this job: Centrifugo (Centrifugal Labs LTD): A realtime channel server; it does not receive or log third-party webhooks.
- not this job: Hook0 (FGRibreau SARL): Hook0 sends the application's own events; it does not receive or verify third-party webhooks.
- not this job: PubNub (PubNub Inc.): PubNub does not receive or verify third-party webhooks.
- not this job: Pusher Channels (MessageBird UK Limited): Pusher does not receive third-party webhooks.

## What stops agents finishing

- body parser changes the raw bytes and signature checks fail
- handler does work inline and the provider times out and retries
- no record of which events were missed and no way to read state from the sender

## Around it

Before: payment-platforms.create-webhook-endpoint, code.write-handler. After: database.write-record, webhooks.trigger-agent.

## Where this comes from

Weight 26 of 100 in Event delivery & webhooks: 11 of 40 accounts; the two Ask HN threads on lost and failed webhooks. Most accounts build this themselves; only Svix and Hookdeck are named as products

As data: https://www.anchorterminal.com/api/v1/use-cases/webhooks.receive-reliably.json, or the MCP tool get_use_case with id webhooks.receive-reliably. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
