Skip to main content
Every plan has a monthly request quota — see the FAQ for current limits. This protects you from runaway traffic consuming your monthly allowance unexpectedly.

​
How quotas work

Free is a hard cap: once you hit it, further requests are blocked until the cycle resets or you upgrade. Paid plans allow metered overage past the included quota, up to a ceiling, before anything is blocked — see the FAQ for exactly how overage works. Quota is enforced before your destination is ever called — a request that’s over the limit never reaches your backend.

​
What happens at the limit

When a request would put you over your plan’s limit, getrequest returns:
The request never reaches your backend — but it is still logged, tagged so you can tell a quota block apart from any other failure and identify exactly what was blocked once you upgrade or the quota resets.
Quota resets on your billing anniversary date, not on the 1st of each month.

​
Monitor your usage

Check your current consumption in Settings → Usage:
  • Requests used — total for the current billing period
  • Requests remaining — how much quota is left
  • Daily breakdown — a chart of request volume by day so you can spot growth trends early
Use this to predict when you’ll hit your limit before it happens.

​
Upgrade before you hit the wall

If you’re approaching your quota, upgrade your plan from Settings → Subscription. The new quota takes effect immediately — mid-period upgrades are prorated.
Watch for a spike in daily volume that’s 2–3× your normal baseline. That’s usually a sign of a retry loop, a misconfigured client, or a load test hitting your endpoints.

​
Per-endpoint traffic visibility

The Logs view shows every request by endpoint. If a spike is happening, you can filter by endpoint to identify which one is driving the volume — and whether it’s legitimate traffic or noise. Use the method and status filters together to find automated retries: a flood of identical POST requests with 4xx responses is a common pattern.

​
Rate limits on dashboard actions

In addition to request quotas, a few dashboard actions have their own rate limits: These are per-user limits and reset automatically. See Bulk retry & recovering many requests for what each of these actions does. Between the quota, the usage dashboard, and per-endpoint filtering, you should never be surprised by a spike after the fact — you’ll see it building in Settings → Usage before it ever turns into a 429.