Rate Limiting

To ensure platform stability and fair usage across our partners, SpotOn’s API enforces rate limits on incoming requests. Requests that exceed the allowed threshold will be rejected with a 429 - Too Many Requests response.

SpotOn recommends that you implement retry and backoff logic.

Additional Details:

• The x-ratelimit-limit header in the response will detail what the current limits are set to.
• The x-ratelimit-remaining header in the response will detail how many requests are left before the rate limit resets.
• The x-ratelimit-reset header in the response will detail when the current rate limit counter will reset (in seconds).

So for example, if you were to receive these header values in your CAPI response:

• x-ratelimit-limit: 50;w=1, 1500;w=60
• x-ratelimit-remaining: 49
• x-ratelimit-reset: 1

You'd interpret them as:

• Short-term burst: 50 RPS
• Long-term quota: 1500 RPM
• Current Status: you can send 49 more requests right now.
• Next Refresh: wait 1 second for the counter to reset.

Partner Application Rate Limits

50 requests per second or 1,500 requests per minute ^

Rate limits are enforced per SpotOn API; requests to one API do not affect the limits of another. View SpotOn’s APIs

Example:

• If a partner sends 50 requests per second to the Menu API, those requests count only toward the Menu API’s rate limit.
• The same partner may still send up to 50 requests per second to the Order API during the same time period without being rate limited.

^ Rate limits are subject to change.