Skip to main content
GetRequest enforces request quotas at the edge — before any request reaches your endpoints or your backend. This gives you predictable cost control and protects your upstream services from runaway traffic consuming your entire monthly allowance without warning.

​
How quotas work

Every GetRequest account is tied to a usage plan through your API key. The plan defines your monthly request allowance: Quota is enforced by GetRequest’s edge infrastructure the moment a request arrives — before it reaches your endpoint logic or your backend. When your quota is exhausted, requests are rejected at the edge with no forwarding and no logging.

​
What happens at the limit

When your monthly quota is reached, every subsequent request receives:
The request is not forwarded to your backend. No log entry is created. The caller receives the 429 directly from GetRequest’s edge infrastructure.
Your quota resets on your billing anniversary date, not on the 1st of each month. If you subscribed on the 18th, your quota resets on the 18th of each billing period.

​
Monitor your usage

Check your current consumption in Settings → Usage:
  • Requests used — total requests consumed in the current billing period
  • Requests remaining — how much quota you have left
  • Daily breakdown — a chart of request volume by day so you can spot growth trends before they become a problem
Review this regularly if your traffic is growing or if you’ve recently added new endpoints. Catching a trend early gives you time to upgrade without hitting the wall.

​
Upgrade before you hit the limit

If you’re approaching your quota, go to Settings → Subscription to upgrade your plan. The new quota takes effect immediately — mid-period upgrades are prorated, so you only pay for what’s left in the billing cycle.
Watch for a spike in daily volume that’s 2–3× your normal baseline. This is usually a sign of a retry loop, a misconfigured client, or a load test hitting your endpoints unexpectedly. Identify the source before upgrading so you’re not paying for noise.

​
Per-endpoint traffic visibility

The Logs view shows every request organized by endpoint slug. When a spike occurs, filter by endpoint to pinpoint which service is driving the volume — and whether it’s legitimate traffic or automated noise. Use the Method and Status filters together to detect retry loops: a flood of identical POST requests all returning 4xx responses is the most common pattern. Once you’ve identified the offending endpoint or client, you can investigate the root cause before the traffic consumes your remaining quota.

​
Dashboard action rate limits

Beyond the monthly request quota, a few dashboard actions have their own per-user rate limits that reset automatically: These limits are independent of your monthly quota and apply regardless of your plan.