Create recording entry

POST

/recordings/entries

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

OperationId:CreateRecordingentry

Turns call recording on for an address of record (AOR) on every recording server, or on one with recording-server-id, giving each its own copy of the entry. Sending an entry that already exists updates it. 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 entry is added on every targeted recording server shortly after. Read it back with GET /recordings/entries?device-aor=....

Bodyapplication/json

🟠400Bad Request

🟠401Authentication Required

🟠403Forbidden

🟠404Record not found

Request Example

Shell

JavaScript

Java

Swift

cURL

Record a user everywhereRecord a device on one serverRecord a whole domain

curl --location '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",
    "sentiment": "yes"
}'

Response Example

202 - Accepted

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

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

List recording entries

Update recording entry