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, in the API Commons Rate Limits shape.

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

Limit state is signalled in the retryAfter, crossTokenLimit, crossTokenConcurrentLimit, and tokenLimit response headers, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429 retryAftercrossTokenLimitcrossTokenConcurrentLimittokenLimit
Method: generated, dated 2026-06-02.
Written by API Evangelist on 2026-06-02 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/clover-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.