# Send signed webhooks to a product's own customers

> Send signed webhooks to a product's own customers: 1 companies fully do it, 6 with a limit, 21 carry the tag. Every listing in Event delivery & webhooks with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/webhooks.send-to-customers/
- Markdown: https://www.anchorterminal.com/niches/webhooks.send-to-customers/index.md (~1,250 tokens)
- Slim: https://www.anchorterminal.com/niches/webhooks.send-to-customers/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/webhooks.send-to-customers/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

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 6 | 21 | 16 | 7 |

## 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

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

- **Webhook Relay (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.

## 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.

- **Amazon EventBridge (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.
- **Convoy (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.
- **Hook0 (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.
- **Hookdeck (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.
- **Svix (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.
- **Upstash QStash (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.

- not this job: 402cron (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.
- not this job: Ably (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.
- not this job: Centrifugo (Centrifugal Labs LTD): No outbound webhook delivery to customer endpoints.
- not this job: PubNub (PubNub Inc.): Events & Actions forwards the keyset's own events to targets; there are no per-customer subscriptions, signed deliveries or attempt log.
- not this job: Pusher Channels (MessageBird UK Limited): Webhooks report the app's own channel and presence events to its backend; there are no customer subscriptions or attempt log.

## 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

As data: https://www.anchorterminal.com/api/v1/use-cases/webhooks.send-to-customers.json, or the MCP tool get_use_case with id webhooks.send-to-customers. 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
