Webhook Guides
Webhook Rate Limiting
Webhook rate limiting protects destinations from traffic they cannot safely process. Provider bursts, retry storms, and bulk replay can all overload a receiver that works fine during normal traffic.
FastHook separates inbound capture from destination delivery, so you can accept provider traffic quickly and control how much pressure reaches each downstream branch.
Where pressure comes from
- Provider bursts after a product launch, billing run, or incident window.
- Automatic retries after destination timeouts or 5xx responses.
- Manual replay after a receiver outage.
- Noisy event families being delivered to every downstream service.
- Several providers sharing one slow destination.
Rate limiting strategy
| Control | Best use | Why it helps |
|---|---|---|
| Destination rate limit | Known receiver capacity. | Prevents delivery from exceeding service limits. |
| Filters | Noisy providers or event families. | Stops irrelevant events before delivery. |
| Pause | Incident isolation. | Protects one branch without stopping all ingress. |
| Replay window | Recovery after outage. | Controls how much traffic returns at once. |