Skip to main content
PUT
Update account recording 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
mediaType
enum<string>
required

Specifies whether the recording should be done on audio or both audio and video.

Available options:
AUDIO,
AUDIO_AND_VIDEO
inbound
boolean

Enables inbound call recording. At least one of the parameters 'inbound' or 'outbound' must be set to true.

outbound
boolean

Enables outbound call recording. At least one of the parameters 'inbound' or 'outbound' must be set to true.

autoCompose
boolean
default:false

Enables composition of call recordings. If set to true, the call recording will be merged into a single audio or video file.

enabled
boolean
default:false

Response

OK

mediaType
enum<string>
required

Specifies whether the recording should be done on audio or both audio and video.

Available options:
AUDIO,
AUDIO_AND_VIDEO
inbound
boolean

Enables inbound call recording. At least one of the parameters 'inbound' or 'outbound' must be set to true.

outbound
boolean

Enables outbound call recording. At least one of the parameters 'inbound' or 'outbound' must be set to true.

autoCompose
boolean
default:false

Enables composition of call recordings. If set to true, the call recording will be merged into a single audio or video file.

enabled
boolean
default:false
enabledChangedAt
integer<int64>
read-only