Skip to main content
PUT
Update account wrap up configuration

Authorizations

Authorization
string
header
default:App
required

This is the most secure authorization type and the one with the most flexibility.

API keys can be generated by calling the dedicated API method. Furthermore, API keys can have a limited scope and cover only some API methods. Lastly, they can be revoked at any time. This range of possibilities makes API keys well suited for separating the API access rights across multiple applications or use cases. Finally, the loss of an API key is easily manageable.

You can manage your API keys from GUI, or programmatically with dedicated API.

API key Authorization header example:

Body

application/json
wrapUpSeconds
integer<int32>
required

Wrap up duration.

canExtendWrapUp
boolean
required

Determines if agents can extend wrap up time.

enabled
boolean
required

Determines if wrap up is enabled for the account.

Response

OK

wrapUpSeconds
integer<int32>
required

Wrap up duration.

canExtendWrapUp
boolean
required

Determines if agents can extend wrap up time.

enabled
boolean
required

Determines if wrap up is enabled for the account.