Limits

This article outlines the technical limits of the Open Loyalty system. Understanding these limits will help you optimize your implementation and use of the platform to ensure smooth operation.

Technical Limits

API Timeout

• Timeout Duration: The API will timeout after 30 seconds.

Authentication Rate Limit

This limit takes effect on 15 September 2026. Currently, the limit is set to 20 RPM.

Requests exceeding the limit will be rejected after enforcement begins.

• Authentication Endpoints: /login and /login_check

• Rate Limit: Maximum 40 requests per minute (RPM) per client.

Most integrations operate well below this threshold and require no changes. If your integration re-authenticates on every request rather than reusing tokens, you should adjust your auth flow before the enforcement date.

Pagination Depth Limit

This limit takes effect on 15 September 2026. Current limit is set to 50.

Requests with _page higher than 500 will return an error after enforcement begins.

To prevent inefficient deep-pagination queries, a maximum value is enforced for the _page parameter on the following list endpoints:

• Maximum _page value: 500

Affected endpoints:

• Custom Events

• Members

• Member History

• Audit Log

• Transactions

• Unit Transfers

• Issue Rewards (Redemptions)

• Collections

Retrieving data beyond page 500: For large datasets, use the Scroll Mechanism (recommended) or the platform's Data Export functionality. Scroll is a separate mechanism from _page pagination and cannot be combined with it — for shallow queries (_page ≤ 500) existing pagination continues to work unchanged.

Imports / Exports

• Maximum Concurrent Requests: You can import or export up to 5 files simultaneously.

• Maximum File Size: The maximum file size for importing XML or CSV files is 100MB.

Forms

Number Field Type

• Minimum Value: -2,147,483,648

• Maximum Value: 2,147,483,647

Float Field Type

• Maximum Decimal Places: 6 decimal places

String Field Type

• Maximum Length: 255 characters

Expressions

• Maximum Length: 500 characters

loyaltyCardNumber Field

• Uniqueness: The loyalty card number must be unique per tenant.

• Case Sensitivity: The field is case-sensitive (e.g., XYZ is not equal to xyz).

Email and Phone Matching

• Case Insensitivity: The system does not consider case when matching email and phone fields during member matching with transactions or custom events.

---

Business Limits

Some loyalty components have limitations that may be encountered when configuring your setup. Should you reach a cap while building out your loyalty program, please don't hesitate to reach out to the Open Loyalty team for assistance — whether through the Customer Helpdesk Portal, via email at [e-mail], or directly through your dedicated Customer Success Manager.