Rate limits

To keep the platform stable and fair for all users, OneProvider may apply rate limits to API requests. Rate limits restrict how many requests can be made within a given time period.

How rate limits work

Rate limits may be applied based on factors such as:

• API endpoint (some endpoints may be stricter)
• Account or project
• Token/credential
• Source IP address

Exact thresholds may vary and can change over time.

What happens when you exceed a rate limit

If you send too many requests in a short time, you may receive responses such as:

• 429 Too Many Requests
• Temporary request failures or throttling

Depending on the API, the response may include headers or messages indicating when you can retry.

Best practices to avoid rate limiting

• Implement retry with backoff (exponential backoff is recommended).
• Cache responses when appropriate.
• Avoid frequent polling; prefer event-driven approaches if available.
• Batch operations where possible.

Example strategy (conceptual):

• Retry after 1s → 2s → 4s → 8s (up to a maximum), and stop after a reasonable number of attempts.

Need higher limits?

If your workload legitimately requires higher request rates, contact Sales/Support with:

• Your account email
• Which endpoints you call and approximate request rate
• Business use case and whether requests are bursty or steady
• Desired region/project (if relevant)