An API quota is the usage allowance a data or content provider grants your account for a given time window — the ceiling on how many calls you can make before the provider starts refusing them.
| Term | API Quota |
|---|---|
| Category | APIs, Reliability and Publishing |
| Also known as | Quota |
| Where it appears | Provider errors and diagnostics |
What it means in RankGear
RankGear pulls data from outside providers — search results, ranking data, content services — and every one of those providers caps how much an account may request per hour, per day, or per billing period. That cap is the API quota. You do not set it inside RankGear; the provider defines it and RankGear works within it. When a run bumps against the ceiling, the provider stops returning data and RankGear surfaces the refusal in its provider errors and diagnostics rather than silently failing, so you can see that the wall you hit is a quota limit and not a broken key or a bad configuration.
How to interpret it
Treat a quota error as a temporary, self-clearing condition rather than a fault to debug. It means the account was working correctly right up to the limit, so the fix is usually to wait for the window to reset, spread work across a longer period, or raise the plan with the provider — not to change credentials or settings. Read it against the diagnostics RankGear shows: a quota message is distinct from an authorization failure or a timeout, and the visible status and retry behavior are what let you tell them apart. A quota that is hit early and often is a signal to size your batches to the allowance you actually have.
| Signal | What it tells you |
|---|---|
| Quota exceeded | The account is valid; you have used the allowance for this window and it will reset in time. |
| Authorization failure | A credential or permission problem — not a quota; retrying the same call will not help. |
| Timeout | A transient network or provider delay; may earn one bounded longer retry. |
Example
You queue a large factor analysis across two hundred pages, and part way through the provider begins returning “quota exceeded.” RankGear stops calling that provider, marks the affected rows in diagnostics, and leaves your key untouched because nothing is wrong with it. You wait for the daily window to reset, or split the job into two smaller runs, and the remaining pages complete on the next pass without any change to your settings.
Important considerations
- The quota is owned by the provider, not by RankGear — the amount and the reset window are set by your plan with that provider.
- A quota error is not a configuration or credential problem; treat it separately from authorization failures so you do not chase the wrong fix.
- Hitting a quota does not affect the quality or meaning of the data you already collected — it only limits how much more you can pull in the window.
- Where RankGear tests providers or publishing targets, tests are kept read-only where possible and credentials stay redacted, so diagnosing a quota never exposes secrets.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.