logo
Get StartedRate Limits

Rate Limits

Understand API rate limits, response headers, and best practices for staying within limits.

Rate limits

To ensure reliable service for all users, the Nashra API enforces rate limits on all endpoints.

Default limit: 60 requests per minute, per API token.

Response headers

Every API response includes headers that tell you your current rate limit status:

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 97
X-RateLimit-Reset: 1620345678
HeaderWhat it means
X-RateLimit-LimitMaximum requests allowed per minute
X-RateLimit-RemainingRequests remaining in the current window
X-RateLimit-ResetUnix timestamp when the current window resets

Exceeding the limit

If you exceed the rate limit, you will receive a 429 Too Many Requests response:

{
  "error": "Too Many Requests",
  "message": "API rate limit exceeded",
  "retry_after": 30
}

The retry_after value tells you how many seconds to wait before making another request.

Best practices

  • Cache responses — Store data locally when possible instead of making repeated API calls for the same information.
  • Use pagination — When listing subscribers, use the limit and page parameters to fetch data in manageable chunks.
  • Implement backoff — If you receive a 429 response, wait for the retry_after period before retrying. Use exponential backoff for repeated failures.
  • Batch your work — Group related operations together rather than making many small individual requests.

Need higher limits?

If your integration requires a higher rate limit, contact the Nashra support team at support@nashra.ai.