Skip to main content
If you receive a 429 error, it means your project has reached the request limit available under your current Uniblock plan. This limit is applied at the Uniblock plan level.

​
What should I do if I hit a rate limit?

If you hit a rate limit, you can:
  1. Retry after a short delay
    Use exponential backoff or a short retry delay before sending the request again.
  2. Reduce request frequency
    Lower polling frequency, batch requests where possible, or cache responses when appropriate.
  3. Review your current usage
    Check whether your application traffic has increased beyond the expected level for your plan.
  4. Upgrade your plan if needed
    If your use case requires higher sustained throughput, upgrading your plan may be the best option.

​
FAQ

​
Are rate limits based on my Uniblock plan?

Yes. Rate limits are based on the limits included with your Uniblock plan.

​
Does a 429 mean the API is down?

No. A 429 means your project has exceeded its allowed request rate. It does not mean the platform is unavailable.

​
Will requests start working again?

Yes. Once traffic falls back within your allowed limit window, requests will succeed again.

​
Can I increase my rate limits?

Yes. If you need more throughput, please upgrade your plan or contact us to discuss a plan that matches your usage.

​
Should I retry 429 responses?

Yes, but retries should include a short delay or exponential backoff to avoid sending another burst immediately.

​
Example response

{
  "error": {
    "code": 429,
    "message": "Too Many Requests"
  }
}