Update recording entry on server

PUT

/recordings/servers/{recording-server-id}/entries

Last modified:2026-10-04 00:09:01

OperationId:UpdateRecordingentryForServer

Changes transcription or sentiment on an existing entry on this recording server only. To change it on every recording server, use PUT /recordings/entries.

Requires Super User scope.

The entry is matched by device-aor and case-id, which defaults to device-aor. Fields you do not send keep their values. An entry that does not exist is accepted and changes nothing. A recording server that does not exist returns 404.

A 202 means the change is accepted and applied shortly after.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

Path Params

Body Params application/jsonRequired

Examples

Responses

🟢202Accepted

application/json

Accepted. The change is applied shortly after.

Bodyapplication/json

🟠400Bad Request

🟠401Authentication Required

🟠403Forbidden

🟠404Record not found

Request Example

Shell

JavaScript

Java

Swift

curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/recordings/servers/Recording-Server2/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-04 00:09:01

Count recording entries on server

Delete recording entry on server