Loyverse Rate Limits
The Loyverse API enforces rate limiting to protect the platform, returning HTTP 429 (Too Many Requests) when a client exceeds the allowed request rate. Community and reference sources cite an approximate ceiling of around 60 requests per minute per token, though Loyverse does not prominently publish a single fixed numeric figure and may adjust limits per endpoint. Clients should read the response headers, back off on 429 responses, and use cursor-based pagination rather than tight polling. Personal access tokens are also capped at 20 per account.
Loyverse Rate Limits is the machine-readable rate-limit profile for Loyverse on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests, tokens, and records.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Point of Sale, POS, Retail, Rate Limiting, and Quotas.
Limits
Policies
Sources
- https://developer.loyverse.com/docs/
- https://help.loyverse.com/help/loyverse-api
- https://support.loyverse.com/en/articles/8061203-faqs-about-loyverse-api
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.