Errors and limits
Understand Public API error responses, method restrictions, and rate limits.
Public API errors use the same simple shape as other Klu API errors:
{
"code": 401,
"message": "Invalid API key"
}Common errors
| Status | Meaning | What to do |
|---|---|---|
400 | Invalid query parameter, date range, UUID, or limit. | Fix the request parameters. |
401 | Missing, invalid, revoked, or disabled API key. | Check the key or ask the owner to rotate it. |
403 | Requested store or data is outside the key organization. | Use only IDs returned by this API key. |
404 | Product or sale was not found in the key organization. | Confirm the ID came from the same organization. |
405 | Method is not allowed. | Use GET only. |
429 | Rate limit exceeded. | Wait until Retry-After or RateLimit-Reset. |
Rate limits
Default limits:
60 requests per minute
3000 requests per dayLimits are per organization key.
When a quota is exceeded, the API returns 429 and rate-limit headers such as:
Retry-After: 30
RateLimit-Limit: 60
RateLimit-Remaining: 0
RateLimit-Reset: 30Agent behavior
AI agents should:
- Cache stable reference data such as stores, categories, and product IDs.
- Use date ranges for analytics and sales.
- Stop retrying immediately on
401and ask a human for a valid key. - Retry
429only after the indicated wait time. - Avoid brute-force ID guessing; use IDs returned by list endpoints.