Full stack of operations with users and users' profiles
VERY IMPORTANT and read it carefully:
Almost all responses contain DeviceToken, AccessToken, and Refresh Token. The existing platform operates with DeviceToken, However, We are currently in the transition period of moving to a new platform. Therefore, we strongly recommend keeping all three tokens to smoothly switch between platforms in the near future.
We will Maintenance the old platform till September 01, 2021, and keep inform all our clients about progress and required steps.
This step plays a significant role in SDK installation. DeviceToken (Virtual device) is a unique ID that is used as an identifier to link depersonalized telematics data with app user.
To obtaine a DeviceToken you have to register users in User Service, then store the device token against a user account in your database.
User service is a full-end service for user management. The main role of the service is to keep a unique user ID (Device Token) which used as a unique key to start collecting and transferring telematics data by telematics SDK. The service contains fields sufficient to build a full user profile if it is needed.
The rules of the service depend on a product selected in SandBox
Telematics SDK. no mandatory parameters. you can create a device token by a simple request without providing any parameters. However, we recommend to add some identifiers that you will use in DataHub to search users. if no paratemers provided, you will have in datahub a device token only.
Platform. Email or phone number are required. Given that the platform product is mainly used as a back-end service for mobile app, the parameters (email or phone number) will play a role of Login. However, we recommend adding more identifiers that you will use in DataHub to search users. if no parameters provided, you will have in datahub a device token and email or phone only.