Using the API
Rate limits
How many requests you can make and how to handle limits.
Each API key can make 120 requests per minute. The limit applies to the REST API and the MCP server together, and each key has its own limit.
Response headers
Successful responses include your current limit:
| Header | Description |
|---|---|
X-RateLimit-Limit | Requests allowed per minute for this key. |
X-RateLimit-Remaining | Requests left in the current minute. |
When you reach the limit
The API responds with 429 Too Many Requests, a Retry-After header with the number of seconds to wait, and this body:
{
"error": {
"code": "rate_limited",
"message": "Rate limit reached. Try again in 42 seconds.",
"requestId": "9cea0cfd-19a0-4d8c-afdf-55a8d238ecde"
}
}Wait for the number of seconds in Retry-After, then retry the request.
Tips
- Gensiv collects new AI responses on a schedule, not in real time. For dashboards, fetch data once an hour or once a day rather than on every page view.
- Use
GET /brands/{brandId}/metrics/dailyto get a whole date range in one request instead of one request per day. - If you need a higher limit, contact support@gensiv.com.