Rate Limiting and Quotas
To ensure optimal performance and fair resource distribution, APIRE.IO enforces specific rate limits and quotas on API usage. Understanding these constraints and managing your usage accordingly will help maintain seamless integration with our services.
Limits Explanation
APIRE.IO imposes the following rate limits:
- Per-Minute Limit: A maximum of 100 requests per minute.
These limits are applied per API key to ensure equitable access for all users.
Monitoring Usage
To help you monitor your API usage and avoid exceeding the limits, APIRE.IO provides usage information in the response headers of each API call:
- X-RateLimit-Limit: Indicates the maximum number of requests allowed in the current time window.
- X-RateLimit-Remaining: Shows the number of requests remaining in the current time window.
- X-RateLimit-Reset: Specifies the time at which the current rate limit window resets, in UTC epoch seconds.
By examining these headers, you can track your usage in real-time and adjust your request patterns to stay within the allowed limits.
Handling Limit Exceedance
If you exceed the rate limits, the API will respond with a 429 Too Many Requests status code. The response will include the Retry-After header, indicating the number of seconds to wait before making a new request.
Recommended Actions:
- Implement Exponential Backoff: When receiving a 429 response, wait for the duration specified in the Retry-After header before retrying. If the limit is exceeded again, increase the wait time exponentially.
- Optimize Request Patterns: Review your application's request logic to ensure it operates efficiently within the established limits.
- Contact Support for Higher Limits: If your application requires higher rate limits, please contact APIRE.IO support to discuss your needs and potential adjustments.
By adhering to these guidelines, you can effectively manage your API usage, prevent disruptions, and maintain a smooth integration with APIRE.IO's services.