Obtaining and managing access tokens
Learn about the TokenAuth endpoint collection, which enables you to authenticate connections with your solution from your external front end as well as authenticate solution users.
Solutions powered by Affective Computing can have two kinds of users depending on their functional role:
Internal users
Administrative or managerial users who might be responsible for feeding actions and managing logic blueprints.
Typically, they wouldn't interact with the solution directly as end-users, and can therefore be considered as internal users.
External users
Users who interact directly with the solution as end-users and participate in interactions. These users can be considered as external users. The data of external users is completely anonymized.
Note: External users could be the same or a different set of users from internal users.
External users must have user IDs to access the platform.
EDAA™, the technology that powers Affective Computing, can identify recurring end-users within the infrastructure and deliver personalized content that takes into account all of their previous interactions with the solution.
Your Affective Computing-powered solutions might require data from various sources, such as the front ends of apps or external devices. In order to allow the external data to flow into your solution, you must set up a connection with our APIs, which begins with authenticating the external data sources. This process involves obtaining an access token.
You can use the endpoints in the TokenAuth collection to manage external user authentication and authenticate external data sources to access our APIs. You can do the following:
Last updated
Was this helpful?