IPRout
LoginSign up

Rate Limits and HTTP 429

IPRout returns HTTP 429 when a request cannot proceed because the shared monthly allowance or an individual key cap has been reached. Check GET /usage to distinguish remaining account capacity from key-level capacity, and avoid aggressive retries until the relevant limit resets or changes.

Last updated August 10, 2026

Why did I receive HTTP 429?

A 429 can indicate an exhausted monthly plan allowance or a key-specific cap that is lower than the shared allowance.

How do I diagnose the limit?

Call /usage with the affected key and compare total, remaining, and per-key request counts.

curl -H "Authorization: Bearer YOUR_API_KEY" https://api.iprout.com/usage

How should clients react?

Stop automatic retries, preserve the error for monitoring, and adjust traffic or plan capacity deliberately.

  • Use per-key caps to contain one integration
  • Alert before remaining capacity reaches zero
  • Do not treat 429 as a transient 500