Niches · Event delivery & webhooks

Receive third-party webhooks without losing or repeating them

Two or three companies' docs show a full fit.

2companies, full fit
3companies, fit with a limit
7companies carry the tag
26share of the category's work
11first-hand accounts

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 2

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

ListingWhy
Convoy C
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. source
Hookdeck A
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. source

Does the job, with a limit 3

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.

ListingWhy
Svix BB
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. source
Upstash QStash BB
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. source
Webhook Relay C
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. source

Doesn't do this job 7

Listings in the category that do something else, with the reason.

ListingWhy
402cron B
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. source
Ably BB
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. source
Amazon EventBridge BB
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. source
Centrifugo C
Centrifugal Labs LTD
A realtime channel server; it does not receive or log third-party webhooks. source
Hook0 B
FGRibreau SARL
Hook0 sends the application's own events; it does not receive or verify third-party webhooks. source
PubNub BB
PubNub Inc.
PubNub does not receive or verify third-party webhooks. source
Pusher Channels D
MessageBird UK Limited
Pusher does not receive third-party webhooks. source

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

The same as data: /api/v1/use-cases/webhooks.receive-reliably.json, or the MCP tool get_use_case with id webhooks.receive-reliably. Other jobs in this category: /api/v1/niches?category=webhooks.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.