One of the main setup steps is choosing the registration method. See the sample example how this can be configured. Links to more detailed instructions can be found at the end of the article.
Last updated
Was this helpful?
OpenLoyalty supports multitenancy, allowing each tenant (store) to operate as a distinct database, complete with its own member list and campaigns. This guide outlines the initial step of the setup process: selecting the appropriate registration method for a member. A single unique identifier is required, which can be an email, phone number, or loyalty card number (that can serve as your own unique identifier).
Input the previous saved token in the request header
Retrieve a list of
Endpoint: GET /api/store
Choose the required tenant and its code
Retrieve member registration for the specified tenant
Endpoint: GET /api/{storeCode}/settings
Update identificationMethod
Endpoint: PATCH /api/{storeCode}/settings
Moving forward, the chosen method will be a required field for member registration.
Please ensure the proper configuration of the tenant. You can find out more in this article.
For a detailed overview and description of the member registration configuration, please refer to these articles:
This method returns a list of all created Stores in the system.
If sorting is not chosen, the rows will be returned in an unspecified order.
To sort a result, use an _orderBy parameter in query.
Maximum supported value is 50.
This method returns all system settings.
If sorting is not chosen, the rows will be returned in an unspecified order.
To sort a result, use an _orderBy parameter in query.
Store code