Skip to main content
The design is simple: warn you, then pause — never surprise you with a bill. As your usage climbs, you get a heads-up; at the limit, capture pauses rather than silently charging overage.

​
Usage alerts

You’re emailed as you cross 80% and 100% of your included events, so a limit never arrives unannounced. Alerts go to the organization.

​
What happens at your cap

When an organization reaches its limit, capture pauses:
  • New requests to your ingest URL get a 429 response with Retry-After, so a well-behaved provider holds the event and redelivers it later instead of dropping it.
  • webhook.co does not queue paused requests itself — it relies on the provider’s own retry — so resume promptly to avoid a provider eventually giving up.
  • The dashboard shows a “Capture is paused” banner. Reading, inspecting, and replaying your existing data all keep working.

​
How to resume

Free plan

The 5,000-event allowance is one-time and doesn’t reset. Upgrade to a paid plan to keep capturing.

Paid plans

Raise your limit by changing plan, or turn on overage so capture continues and extra events are billed per million instead of pausing.
Overage is a choice, not a default. On paid plans you decide whether going past your included volume pauses capture (the default) or continues and bills the extra. Set it on the Billing page.

What counts as an event

So you know what moves the number.

Manage your subscription

Raise your limit or turn on overage to resume.
A cap pause is org-wide and is cleared by raising your limit or enabling overage — not by a per-endpoint control. That’s different from manually pausing a single endpoint, which you resume from the endpoint itself.