Request Limits

Rate Limits

All services enforce rate limits to control the number of incoming requests, typically allowing an average of five requests per second. When this limit is exceeded, APIs respond with an HTTP 429 status code.

Integrators should implement backoff logic to handle variable rate limits effectively. This includes detecting HTTP 429 responses, respecting the Retry-After response header, and waiting for the specified duration before retrying.

❗️

Rate limits may change

API rate limits may change, so integrators should plan accordingly during development.

Size Limits

Cortex imposes size limits on certain request query parameters. If a request exceeds any of these limits, it will return an error_validation error code with an HTTP 400 status, providing additional details in the message field.

Beyond query parameter limits, services may impose request payload limits. These can be found in the API reference documentation.

📘

Request size limits

Due to variations in data types and retrieval methods, request limits are applied per service.