Rate Limiting

Overview

The Rntor API implements rate limiting to ensure fair usage and maintain service quality for all users.

Every API response includes headers to help you track your usage:

Header	Description
`X-RateLimit-Limit`	Maximum requests allowed per minute
`X-RateLimit-Remaining`	Requests remaining in current window
`X-RateLimit-Reset`	Unix timestamp when the limit resets

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 45
X-RateLimit-Reset: 1704067200

When you exceed the rate limit, you’ll receive a 429 Too Many Requests response:

{
  "error": {
    "code": "rate_limit_exceeded",
    "message": "Rate limit exceeded. Please retry after 30 seconds.",
    "retry_after": 30
  }
}

Implement Exponential Backoff

When receiving a 429 response, wait for the specified retry_after duration before retrying. For subsequent failures, double the wait time.

Cache Responses

Cache API responses when possible to reduce the number of requests you need to make.

Use Webhooks

Instead of polling for changes, use webhooks to receive real-time notifications.

Batch Requests

Where possible, use bulk endpoints to reduce the total number of API calls.

Need higher limits? Contact our sales team to discuss Enterprise plans.