Update recording entry

PUT

/recordings/entries

Last modified:2026-10-30 21:05:10

OperationId:UpdateRecordingentry

Changes transcription or sentiment on an existing entry, matched by device-aor and case-id, on every recording server or on one with recording-server-id. Requires Super User scope.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Body Params application/jsonRequired

Examples

Responses

🟢202Accepted

application/json

Accepted. The change is applied on every targeted recording server shortly after. An entry that does not exist is accepted and changes nothing; create it with POST /recordings/entries.

Bodyapplication/json

🟠400Bad Request

🟠401Authentication Required

🟠403Forbidden

🟠404Record not found

Request Example

Shell

JavaScript

Java

Swift

cURL

Turn on transcriptionTurn off sentiment on one server

curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/recordings/entries' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "device-aor": "1001@example.com",
    "transcription": "yes"
}'

Response Example

202 - Accepted

{
    "code": 202,
    "message": "Accepted"
}

Modified at 2026-10-30 21:05:10

Create recording entry

Delete recording entry