Rate Limiting

Beta

The Nexoya API is currently in beta. Rate limits are not strictly enforced during this period. We ask that all customers observe fair-use principles to ensure a reliable experience for everyone.

Fair use

While hard limits are not yet in place, the following guidelines apply:

• Avoid high-frequency polling. Cache responses where possible and use date-range queries to fetch only the data you need.
• Do not attempt to bulk-export the entire dataset in a single session. Use pagination where available.
• Automated scripts should include backoff logic to handle transient failures gracefully.

When rate limits are enforced

When rate limiting is active, the API responds with HTTP 429 Too Many Requests. The response will include a Retry-After header indicating how many seconds to wait before retrying.

HTTP/1.1 429 Too Many Requests
Retry-After: 30

Implement exponential backoff in your client: wait the Retry-After duration, then retry. If no header is present, wait at least 5 seconds before the first retry and double the delay on each subsequent attempt.

IP blocking

In cases of sustained abusive request patterns, Nexoya may block access at the IP level. If this occurs, you will receive a descriptive error message explaining the reason. Contact developers@nexoya.com to resolve a block.