Introduction

Rate limits

The IBEE Solutions API may apply rate limits to ensure fair usage and platform stability.

Current policy

Limits can vary by environment, endpoint, and account. Do not hard-code a request rate from this page. Use the response headers returned by the gateway and contact IBEE support when you need a confirmed quota for production.

Handling rate limits

When the gateway returns 429 Too Many Requests, wait before retrying. Honor a Retry-After header when it is present; otherwise use exponential backoff with jitter. Treat the error body as descriptive rather than parsing a fixed message.

Best practices:

  • Add exponential backoff with jitter to retry logic.
  • Cache responses when possible instead of re-fetching.
  • Batch operations where the API supports it rather than making individual calls.

Higher limits

If your integration needs higher rate limits, contact IBEE support.