User Management API Implementation Guideline
This manual describes how to implement an interface for user management with Convercus. With this documentation, it should be more intuitive and straight-forward to map all relevant information and processes to calls of the Convercus Api.
For all loyalty-related processes it is important to identify the person the system is interacting with. The central object in Convercus api for this identification is the account you can collect points on. This account can be linked to user-data, transactions, bookings, etc. Every account has a unique identifier, the accountId (e.g. 7d123457-bfa1-4a83-8213-123456789763), which is the technical ID all those connections are made with.
Additionally, every account can have multiple identifiers (i.e. card-codes, external identification-codes, etc.), which allow to make a connection to an account without the need to extract the account-id.
This documentation will explain the creation and maintanance of accounts, users, identifiers and memberships step-by-step and demonstrate, how all can be linked together to create a fully-fledged customer profile.
Technical information about the Convercus Api can be found at the following sites
- https://staging.convercus.io/api-docs/swagger-ui.html (Staging Environment)
- https://api.convercus.io/api-docs/swagger-ui.html (Production Environment)
and on the Developer Page
Updated 2 months ago