Rate limits

A fixed window per minute. On a plan, the plan's requests per minute apply to each client and to the organisation. Without a plan, the numbers below apply. A test key has 10 a minute of its own. Exceeding any limit is a 429, with no partner exceptions.

Per service client, without a plan

60/min

Per tenant, without a plan

600/min

Every request counts before authorization, including refused ones.

On a plan with a monthly quota, every request by a live key or a service client counts toward the organisation's month. Each counted response carries Currixa-Quota-Limit, -Remaining and -Reset. Once the month is spent, requests get a 429 with QUOTA_EXCEEDED until it resets or the plan is upgraded; there are no overage fees. The organisation's owners get an email at 80% and at 100%.

• RateLimit-LimitThe applied limit.
• RateLimit-RemainingRemaining in the window.
• RateLimit-ResetWindow end.
• Retry-AfterSeconds to wait after a 429.
• Currixa-Quota-LimitThe month's request quota.
• Currixa-Quota-RemainingRequests left this month.
• Currixa-Quota-ResetSeconds until the month resets.

Wait out the full Retry-After, then retry once. Immediate repeated retries extend the block.

The public site pages read through one shared service client; collective excess can briefly show the busy state to everyone.