Open Loyalty · Rate Limits

Open Loyalty Rate Limits

Open Loyalty does not publish fixed numeric per-endpoint rate limits for its REST API. Because the platform is delivered as a per-tenant cloud SaaS, request throughput is governed by the capacity provisioned for your instance and your commercial plan rather than a documented public request cap. The primary commercial constraint is Monthly Active Members - the billing metric - rather than API calls per second. Self-hosted Open Source Edition deployments are bounded by your own infrastructure and the ~200 member testing cap.

Open Loyalty Rate Limits is the machine-readable rate-limit profile for Open Loyalty on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests and members.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Loyalty, Gamification, Rate Limiting, and Quotas.

3 Limits Throttle: 429
LoyaltyGamificationRate LimitingQuotas

Limits

REST API Requests instance
requests
not published
No fixed numeric request-rate limit is documented; capacity is per provisioned tenant instance.
Monthly Active Members account
members
per plan
Commercial billing/quota metric - a member performing at least one loyalty event in a month.
Open Source Edition Members deployment
members
200
The self-hosted Open Source Edition is capped at roughly 200 members and is for testing only.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Bulk Imports
Use the XML import endpoints (customers, transactions, points transfers) for large batch loads rather than tight per-record request loops.

Sources