Access our complete documentation library here
https://<IP_Domain_Name>:<port>/configuration/basicauth
accept : application/json
Authorization : Bearer eyJhbGciOiJSUzUxMiJ9.eyJpc3MiOiJh
Content-Type : application/json
The Temporary Authorization token can be obtained through a browser by logging in as the admin user of the specific CC
{
“username”: “customer_manager”,
“password”: “customer_manager@123”,
“context”: “ContactCenter”,
“contextId”: “1”,
“dateExpiry”: “2030-05-19T12:20:57.310Z”,
“userRole”: “Administrator”
}
| Parameter | Type | Description |
|---|---|---|
username |
String | Required. The unique identifier for the user account that is making the API request. This user must have the appropriate permissions to perform the requested actions. |
password |
String | Required. The authentication password associated with the provided username. For security, it is highly recommended to transmit this credential over HTTPS. |
context |
String | Required. Defines the specific application or service module the API call is intended for. For all contact center operations, this value should be set to "ContactCenter". |
contextId |
String | Required. The unique ID of the specific contact center instance or tenant you are targeting. This ensures the request is routed to the correct environment. |
dateExpiry |
String | Optional. The ISO 8601 timestamp that specifies the exact date and time when the session or token for this request will expire. If not provided, a default session timeout will apply. <ToBeChecked> Example: "2030-05-19T12:20:57.310Z" |
userRole |
String | Required. Defines the permission level of the user making the request. This determines which actions the user is authorized to perform. Example roles include "Administrator". |
We now have the following credentials registered on the server. To create a token, these credentials need to be encoded using Base64. You can use an online tool like Base64 Encode for this purpose. Here is the format: username:password i.e customer_manager:customer_manager@123$.
