Overview
Nova API uses rate limiting to ensure fair usage and maintain service stability. Limits are applied per IP address and reset every minute.Rate Limit Tiers
| Endpoint Type | Requests per Minute | Description |
|---|---|---|
| Normal | 1,000 | Standard endpoints (default) |
| Strict | 10 | Sensitive or resource-intensive endpoints |
Most endpoints use the normal rate limit. Strict limits apply to specific endpoints documented in the API Reference.
Response Headers
Every API response includes rate limit information in the headers:| Header | Description |
|---|---|
X-Rate-Limit-Limit | Maximum requests allowed per minute |
X-Rate-Limit-Remaining | Requests remaining in the current window |
X-Rate-Limit-Reset | Unix timestamp (UTC) when the limit resets |
Example Headers
Rate Limit Exceeded
When you exceed the rate limit, the API returns a429 Too Many Requests response:
Handling Rate Limits
1
Monitor Headers
Check
X-Rate-Limit-Remaining in responses to track your usage.2
Implement Backoff
When you receive a
429 response, wait until the X-Rate-Limit-Reset timestamp before retrying.3
Queue Requests
For bulk operations, implement a request queue to stay within limits.
Code Examples
Handling 429 Responses
Monitoring Rate Limit Usage
Best Practices
Cache Responses
Cache frequently accessed data to reduce API calls.
Batch Requests
Use bulk endpoints when available instead of multiple single requests.
Implement Retry Logic
Always handle
429 responses gracefully with exponential backoff.Monitor Usage
Track your rate limit consumption to prevent unexpected throttling.
Need higher rate limits? Contact us to discuss enterprise options.

