Rate Limits
Rate limiting exists, but older examples in this docs section were too specific and no longer trustworthy.
What is safe to rely on
- partner API key integrations can receive
429 Too Many Requests - responses may include rate-limit headers
- error responses may include
retryAfter
Current error format example
{
"success": false,
"message": "Too many requests",
"error": "Too Many Requests",
"statusCode": 429,
"timestamp": "2026-03-10T18:00:00.000Z",
"path": "/api/partner/cenotes",
"retryAfter": 60,
"requestId": "req_123"
}
Recommendation
- implement exponential backoff
- log
requestId - honor
retryAfterwhen present