KinexaSupport

API Rate Limits

API Rate Limits

To keep the platform fast and fair, the Kinexa API enforces rate limits per API key.

Default Limits

  • 60 requests per minute on most endpoints
  • 600 requests per minute for read-only endpoints on higher plans
  • Bulk endpoints (import/export) have separate, lower limits

Reading the Headers

Every response includes:

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 42
X-RateLimit-Reset: 1717689600

Reset is a Unix timestamp for when the window refreshes.

Handling 429 Too Many Requests

When you exceed the limit you get HTTP 429. The response includes a Retry-After header (seconds).

Best Practices

  1. Back off exponentially — wait, then retry with increasing delays
  2. Cache responses that don't change often
  3. Batch operations instead of looping single requests
  4. Spread scheduled jobs out instead of firing them all at once

Need Higher Limits?

Upgrade your plan or contact support to discuss a custom limit for high-volume integrations.

Was this article helpful?

Need more help? Contact our support team