API & Integrations
Rate Limits Explained
Understand Karsilo's API rate limits and how to handle them in your integrations.
Default rate limits
Karsilo's API allows 100 requests per minute per API key on the standard plan and 500 requests per minute on the professional and enterprise plans. Rate limits are applied per key, so multiple keys from the same account each get their own limit.
Rate limit headers
Every API response includes rate limit headers: X-RateLimit-Limit (your limit), X-RateLimit-Remaining (requests left in the current window), and X-RateLimit-Reset (Unix timestamp when the window resets). Use these headers to proactively manage your request rate.
Handling 429 responses
When you exceed the rate limit, the API returns a 429 Too Many Requests response with a Retry-After header indicating how many seconds to wait. Implement exponential backoff in your client: wait the specified time, then retry. Avoid tight retry loops that could extend your rate limit window.
Optimizing API usage
To stay within rate limits, batch requests where possible, cache responses that don't change frequently, and use webhooks for real-time data instead of polling. If you consistently hit limits, consider upgrading your plan for a higher allocation or contact support for custom limits.