A user in the context of our APIs represents one of your customers, the end user. In our application, every action is taken on behalf of a user which gives the user a central role in our business and features. Regardless of how you choose to implement, you will need to create a user in our system before the user can access any of our features.
The user signs in to our features through single sign-on (SSO), where we rely on the fact that the user is securely authenticated through your channels. You would then authenticate against our APIs which opens up all of our functionality to the user.
To identify users throughout their lifecycle, we require a unique, stable identifier in order to create a connection between a user in your channel to a user in our channel. A stable identifier, in this context, means an identifier that will never change. The identifier we require from your side, called
externalId in our API, could for example be a database identifier, either as is or in some way obfuscated.
Updated 7 months ago