Limits

To assure good performance for every project, the API imposes limits on certain parameters and objects.

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

Technical Limits

Import XML/CSV

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

API Timeout

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

Forms

Number Field Type

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

  • Maximum Value: 2,147,483,647

String Field Type

  • Maximum Length: 255 characters

Business Limits

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.

Active Achievements

  • Maximum Active Achievements: A maximum of 1,000 active achievements is allowed.

Custom Attributes

Max no of custom attributesMax Key LengthMax Value Length

Member

25

255

255

Transaction

25

255

255

Transaction Item

10

255

255

Campaign Simulation

25

255

255

Transaction Limits

  • Maximum Number of Items in a Transaction: 100

Custom Event

  • Maximum Number of Fields in a Custom Event Schema: 50

These limits are designed to ensure optimal performance and reliability of the Open Loyalty platform. Adhering to these constraints will help maintain system stability and efficiency. If you have any questions or need further clarification, please refer to the OpenLoyalty API Documentation or contact us.

Last updated