Create an authentication token for a client application installation.
⚠️ Endpoint is available only in the Customer interface.
⚠️ When creating a new token, the request does not need to contain an Authentication header.
⚠️ We highly recommend filling all identifications in the tokens resource (device and application) to avoid problems if multiple applications use the CareCloud REST API on one device.
What happens when a token is created
A token record is created and its server-generated token_id is returned.
The token is bound to the supplied device identification and setup parameters (language, GPS permission, notifications permission).
The token is used as the credential on subsequent customer-interface requests, sent as Authorization: Bearer <token_id>. See Authentication for the full flow.
Recent Requests
Log in to see full request history
Time
Status
User Agent
Retrieving recent requests…
Loading…
Responses
403
The client does not exist or the client tried to access an unauthorized property or resource.
404
The resource was not found.
405
The resource does not support the specified HTTP method.
429
Too many requests - more than the resource limit.
500
Server is not working as expected.
503
Temporary state when the service is temporarily unavailable, overloaded or there is a maintenance window.