Clover · Rate Limits

Clover Rate Limits

Clover enforces both request-rate and concurrency limits on the REST API, scoped per OAuth app and per access token. Documented limits are 50 requests/second per app and 16 requests/second per token, with 10 concurrent requests per app and 5 concurrent requests per token. Exceeding any limit returns HTTP 429 with an X-RateLimit-* header identifying which limit was hit; concurrent-limit responses include a retry-after header.

Clover Rate Limits is the machine-readable rate-limit profile for Clover on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests_per_second and concurrent_requests.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled and concurrencyExceeded.

Tagged areas include POS, Payments, Retail, SMB, and Hardware.

4 Limits Throttle: 429
POSPaymentsRetailSMBHardwareRate LimitingQuotasThrottling

Limits

Per-app request rate app
requests_per_second · second
50
Across all tokens issued to the app.
Per-token request rate key
requests_per_second · second
16
Per merchant access token.
Per-app concurrency app
concurrent_requests
10
Simultaneous in-flight requests across the app.
Per-token concurrency key
concurrent_requests
5
Simultaneous in-flight requests per access token; 429 responses carry a retry-after header.

Policies

Backoff Strategy
Pause one second on the first 429, then double the wait on each subsequent 429 until a successful response; honor the retry-after header on concurrency-limit responses.
Scope Awareness
Inspect the X-RateLimit-* response header to determine whether the app-level or token-level limit was exceeded, and throttle the appropriate dimension.

Sources