Openpay Rate Limits
Openpay does not publish explicit numeric request-per-second or request-per-minute rate limits in its public API reference. As a payments platform it applies account- and merchant-level throttling and anti-fraud controls, and may return HTTP 429 or service-unavailable responses under excessive load. List endpoints are paginated via offset and limit query parameters. Specific per-merchant limits are not reconciled in this artifact and should be confirmed with Openpay.
Openpay Rate Limits is the machine-readable rate-limit profile for Openpay on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests, records, and transactions.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Payments, Fintech, Cards, SPEI, and Subscriptions.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/openpay-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.