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.
Limits
Policies
Sources
- https://docs.clover.com/dev/docs/api-usage-rate-limits
- https://docs.clover.com/dev/reference/api-reference-overview
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/clover-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.