Niches · Event delivery & webhooks
Send signed webhooks to a product's own customers
One company's docs show a full fit.
What counts as done
An event posted once is delivered signed to every subscribed endpoint, retried on a published schedule, filterable per subscription, and each attempt with its status code is readable by API.
How agents ask for it: add webhooks to our API
, send order events to customer endpoints
, let customers see failed deliveries
, sign our outgoing webhooks
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Webhook Relay C AppScension Ltd | The Outbound Gateway publishes once per Idempotency-Key to each consumer's subscribed endpoints, signs with Standard Webhooks, retries at 5 s to 10 h for up to 8 attempts in 48 hours, and lists deliveries per endpoint by API with 35 days of history. source |
Does the job, with a limit 6
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.
| Listing | Why |
|---|---|
| Amazon EventBridge BB Amazon Web Services, Inc. | API destinations deliver with retries for up to 24 hours and event patterns filter on payload fields, but requests carry only Basic, OAuth or API-key auth with no signature, and no API lists each attempt's status. source |
| Convoy C Frain Technologies Inc. | One event fans out to every subscribed endpoint, signed, with per-subscription retry and payload filters, and attempts are listed by API; but Convoy Cloud needs a person to create the first key, and acc-33 saw retries stop after an upgrade. source |
| Hook0 B FGRibreau SARL | One event reaches every matching subscription, signed with HMAC-SHA256 over timestamp and raw body, retried on a published backoff, and attempts are readable; but subscriptions filter on labels only (#51, open), so customers billed per execution get unwanted events. source |
| Hookdeck A Hookdeck Technologies Inc. | Destinations get signed deliveries with linear or exponential retry rules and payload filters, and attempts are readable, but there is no per-customer application, tenant limit or consumer portal. source |
| Svix BB Svix Inc. | Signed delivery to every subscribed endpoint on a published schedule, with attempt, resend and recover APIs; but a person must create the first API key, the hosted retry schedule is fixed (#481 added a switch to the self-hosted server's config only), and filters are by event type and channel. source |
| Upstash QStash BB Upstash, Inc. | URL groups fan one publish out to several endpoints with retries and a logs API carrying responseStatus, but every request is signed with the account's QStash key and there is no per-subscription filter or tenant model. source |
Doesn't do this job 5
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| 402cron B Georgi Kalchev (operator, a named person; no company named) | One task calls one verified destination; there are no subscriptions, fan-out or per-customer endpoints. source |
| Ably BB Ably Realtime Ltd | Outbound webhooks notify the app's own backend of channel events; there are no per-customer endpoints, payload filters or attempt log readable by API. source |
| Centrifugo C Centrifugal Labs LTD | No outbound webhook delivery to customer endpoints. source |
| PubNub BB PubNub Inc. | Events & Actions forwards the keyset's own events to targets; there are no per-customer subscriptions, signed deliveries or attempt log. source |
| Pusher Channels D MessageBird UK Limited | Webhooks report the app's own channel and presence events to its backend; there are no customer subscriptions or attempt log. source |
What stops agents finishing
- a person must create the first API key in a dashboard (Svix, Convoy Cloud, Hook0 Cloud)
- retries cannot be turned off for stateful events
- no per-subscription filter, so customers pay for unwanted executions
Around it
Before: code.write-handler. After: webhooks.receive-reliably.
Where this comes from
Weight 16 of 100 in Event delivery & webhooks: 7 of 40 accounts, six of them GitHub issues (Svix, Convoy, Hook0), so this rests on builder problems more than reports of use
The same as data: /api/v1/use-cases/webhooks.send-to-customers.json, or the MCP tool get_use_case with id webhooks.send-to-customers. Other jobs in this category: /api/v1/niches?category=webhooks.
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.