Skip to main content
The Customer API allows 120 requests per minute for each customer API key.

When you exceed the limit

Requests over the limit fail with a rate_limited error:
Wait before retrying, and back off further if you’re limited again:
For sustained workloads, spacing out requests — no more than about 2 per second — works better than reacting to errors.

Tips for staying under the limit

  • Generate proxies in batches. One call to generate proxies with quantity: 100 returns 100 proxy lines. You don’t need 100 calls.
  • Cache reference data. Package tiers change rarely. Fetch them once and refresh occasionally.
  • Don’t poll usage in a tight loop. Check package usage on a schedule, for example once a minute, not before every proxy request.
This limit applies to the Customer API only. Proxy traffic through proxy.flameproxies.com has no limits on requests per second or minute, threads, or concurrent connections.

Next steps

Error handling

Every error code and how to handle it.

Generate proxies

Generate many proxy lines in one call.