Skip to main content

rate_limit_exceeded

HTTP Status: 429 Too Many Requests

Example response

The response will also include rate limit headers and a Retry-After header:
For paid tiers, X-RateLimit-Reset reflects your billing anniversary instead of the 1st of the month.

What happened?

You’ve used all the requests in your monthly quota. This happens when:
  • Your cumulative requests this month have reached your tier’s limit
  • Cached responses have counted toward your usage (cached results still consume quota)

How to fix

  1. Wait for the reset: Check the Retry-After header for the number of seconds to wait, or X-RateLimit-Reset for the exact reset timestamp (your billing period reset date)
  2. Upgrade your tier: Move to a higher tier for more monthly requests:
  3. Optimize your usage: Implement client-side caching to avoid duplicate lookups for the same VAT number

Common mistakes

  • Not tracking usage: Monitor the X-RateLimit-Remaining header on each response to see how many requests you have left
  • Assuming cached results are free: Cached responses still count toward your monthly quota
  • Ignoring the reset date: The X-RateLimit-Reset header tells you exactly when your quota refreshes

Catching this error with the SDKs