# Receive third-party webhooks without losing or repeating them (slim)

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

- Full: https://www.anchorterminal.com/niches/webhooks.receive-reliably/index.md (~1,200 tokens) · this version ~280 tokens · JSON https://www.anchorterminal.com/niches/webhooks.receive-reliably/index.json · canonical https://www.anchorterminal.com/niches/webhooks.receive-reliably/
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-15
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Two or three companies' docs show a full fit. Full fit: 2 companies, with a limit: 3, tagged: 7. Weight 26, 11 accounts.

Done when: 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.
yes: convoy (Frain Technologies Inc.)
yes: hookdeck (Hookdeck Technologies Inc.)
caveat: svix (Svix Inc.)
caveat: upstash-qstash (Upstash, Inc.)
caveat: webhook-relay (AppScension Ltd)

Data: https://www.anchorterminal.com/api/v1/use-cases/webhooks.receive-reliably.json
