API Rate Limits

To ensure fair usage and system stability, our API enforces rate limits. Each endpoint has a maximum number of requests allowed per second. When the limit is exceeded, requests are throttled and the API returns 429 Too Many Requests.

How Rate Limits Work

• Per‑endpoint limits: Each API method has its own requests‑per‑second (RPS) allowance.
• Window: Limits apply over a rolling 1‑second window.
• Retry: If you exceed the limit, wait 1 second before retrying (see Retry‑After header).
• Why different limits? Heavier endpoints allow fewer requests per second based on relative compute cost.

Example 429 response

HTTP/1.1 429 Too Many Requests
Retry-After: 1
Content-Type: application/json

{
  "error": "rate_limited",
  "message": "Too many requests. Please retry after 1 second."
}

API-Level Overview (Uniform Limits)

Some APIs have the same limit across all listed endpoints.

*SEO Research API covers both Organic SERP and Top Pages endpoints.

Endpoint-Specific Limits

Domain Stats API

Ad History API (uniform: 10 r/s)

PPC Research API

SEO Research API (uniform: 10 r/s)

Competitors API (uniform: 1000 r/s)

Kombat API

Keyword Research API

Ranking History API (uniform: 10 r/s)

Client Recommendations

• Backoff on 429: Retry after the number of seconds indicated by Retry‑After (typically 1).
• Batch or paginate where supported to reduce call volume.
• Cache results to avoid redundant calls.
• Parallelism: Cap concurrency so per‑endpoint RPS stays within limit.

Questions?

If you need a higher limit for specific workloads, contact support with:

• The API and endpoint,
• Expected sustained RPS and burst behavior,
• Use case and time window.