API Usage Limits
To ensure the stability and availability of the NeoSpace API for all users, we have implemented request limits (rate limits). It's important to understand and respect these limits when developing your integrations.
Default limits
| Plan | Requests per minute | Requests per day |
|---|---|---|
| Free | 60 | 10,000 |
| Professional | 300 | 100,000 |
| Enterprise | 1,000 | 1,000,000 |
Response headers
Each NeoSpace API response includes headers that provide information about your current usage and limits:
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 58
X-RateLimit-Reset: 1625140003
Where:
X-RateLimit-Limit: Maximum number of requests allowed in the current periodX-RateLimit-Remaining: Number of requests remaining in the current periodX-RateLimit-Reset: Unix timestamp of when the limit will reset
When the limit is reached
If you exceed the request limit, you will receive a response with HTTP status code 429 Too Many Requests and a body like this:
{
"error": {
"code": "rate_limit_exceeded",
"message": "Request limit exceeded. Please try again after 45 seconds.",
"retryAfter": 45
}
}
Best practices
To avoid problems with request limits, we recommend:
- Implementing exponential backoff when encountering 429 errors
- Grouping requests when possible
- Implementing cache for data that doesn't change frequently
- Monitoring your usage regularly
Increasing your limits
If the default limits are not sufficient for your use case, you can:
- Upgrade to a plan with higher limits
- Contact our sales team to discuss a custom plan
For more information about plans and pricing, visit neospace.ai/pricing.