What is a webhook gateway?
A webhook gateway is an intermediary service that sits between webhook senders and receivers and handles the cross-cutting work of processing webhooks in one place: verifying requests, validating and routing payloads, retrying failures, and logging everything. Instead of every receiving service reimplementing that logic, deliveries pass through the gateway, which applies it consistently.
What a webhook gateway does
A webhook gateway terminates the incoming HTTP request, verifies its signature, validates the payload against a schema, and forwards it to the right internal service, retrying and logging every attempt. It does this once, at the edge, for every receiver behind it, instead of each service implementing the same steps:
- Verification. It verifies incoming requests so only authentic deliveries pass through, checking the webhook signature or, in some setups, mTLS.
- Payload validation. It checks payloads against expected schemas before forwarding, so malformed data is rejected at the edge rather than deep inside a service.
- Transformation. It can reshape or enrich a payload so an incoming format matches what the receiver expects.
- Routing and load balancing. It routes deliveries to different receivers by rule and spreads load across instances.
- Retries. It applies retry policies to failed deliveries instead of leaving each receiver to build its own.
- Monitoring. It logs deliveries and gives one place to inspect and troubleshoot the pipeline.
Consolidating these means a change to signature verification or retry behavior happens once, at the gateway, rather than in every service behind it.
How a gateway handles one delivery
A delivery arrives as a POST carrying webhook-id, webhook-timestamp, and webhook-signature headers. The gateway recomputes the HMAC-SHA256 over the raw body and rejects the request if the result does not match the header, or if the timestamp is more than 300 seconds from its own clock, which is what stops a captured request from being replayed. It returns a 2xx to the sender straight away, queues the event, forwards it to the receiver, and retries with exponential backoff when the receiver fails. Every attempt is recorded with its response status, so a failed delivery can be inspected and replayed rather than lost.
Gateway vs. building it yourself vs. a full webhook service
A gateway is one point on a spectrum. At one end you build webhook handling into each service; at the other you use a managed platform that owns sending and receiving end to end. The tradeoff is how much infrastructure you operate versus how much control you keep.
| Build in each service | Webhook gateway | Managed webhook service | |
|---|---|---|---|
| Verification, retries, logging | Reimplemented per service | Centralized at the gateway | Built in |
| Who operates it | You, everywhere | You, in one place | The provider |
| Best when | One or two simple endpoints | Many receivers, existing infra to front | You want to send or receive at scale without running it |
A gateway mainly manages traffic in front of infrastructure you already run. A managed service like Svix instead provides the whole platform, including sending, with enterprise features such as custom rate limits, SAML SSO, and uptime SLAs. If the goal is to add reliable webhooks to your product without operating the delivery pipeline yourself, a full service usually fits better than assembling a gateway plus the pieces around it.
Frequently asked questions
What is the difference between a webhook gateway and an API gateway?
An API gateway fronts outbound requests clients make to your API, handling auth, rate limiting, and routing for request/response traffic. A webhook gateway fronts inbound event notifications pushed to you, adding signature verification, payload validation, retries, and delivery logging specific to webhooks.
Do I need a webhook gateway?
A gateway earns its place when you have many receivers and want verification, retries, and monitoring handled in one spot rather than reimplemented in each. For one or two simple endpoints it is overhead; for sending webhooks at scale, a managed webhook service is usually a better fit than building a gateway yourself.
Does a webhook gateway handle retries?
Yes. Centralizing retries is one of its main jobs: it applies a retry policy to failed deliveries, typically with exponential backoff, so each receiver behind it does not have to build its own. See our webhook retry best practices for how a good policy works.