Loyverse · Rate Limits

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.

3 Limits Throttle: 429
Point of SalePOSRetailRate LimitingQuotas

Limits

API Request Rate token
requests
~60 per minute (community-reported; verify)
Exceeding the rate returns HTTP 429. Loyverse does not prominently publish a single fixed number.
Personal Access Tokens account
tokens
20
Maximum of 20 personal access tokens per Loyverse account.
Page Size request
records
up to 250 per page
List endpoints are cursor-paginated; use the returned cursor to page through results.

Policies

Backoff Strategy
On HTTP 429, pause and retry with exponential backoff and jitter rather than retrying immediately.
Prefer Webhooks
Use webhooks for event-driven updates (for example receipts and inventory changes) instead of tight polling loops.
Cursor Pagination
Iterate large collections with the cursor returned by list endpoints to minimize request volume.

Sources