List recording entries

GET

/recordings/entries

Last modified:2026-08-12 22:05:57

OperationId:ListRecordingentries

Recording entries across every recording server, so an AOR recorded on three servers appears three times. Filter by recording-server-id to narrow to one.

Only entries whose recording server exists are listed. lidf_lic_config has no foreign key to the servers table, so it accumulates entries for servers that were never real (three are seeded by the platform install) or are gone (deleting a recording server leaves its entries behind). Those can never be written to — every write path resolves its targets from the servers table — so they are hidden rather than offered as servers that silently do nothing. Nothing is deleted; pass include-orphaned=yes to see them.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

Query Params

Responses

🟢200OK

application/json

Recording entries

Bodyapplication/json

🟠401Unauthorized

🟠403Forbidden

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/recordings/entries?recording-server-id=undefined&device-aor=undefined&case-id=undefined&transcription=undefined&sort=undefined&limit=undefined&start=undefined&include-orphaned=undefined' \
--header 'Authorization: Bearer <token>'

Response Example

200 - Example 1

[
    {
        "recording-server-id": "Recording-Server",
        "device-aor": "sip:1123wp@example.com",
        "case-id": "sip:1123wp@example.com",
        "valid-from": "0000-00-00 00:00:00",
        "valid-to": "0000-00-00 00:00:00",
        "ccc-intercept": "yes",
        "cdc-intercept": "yes",
        "transcription": "yes",
        "sentiment": "yes"
    }
]

Modified at 2026-08-12 22:05:57

Create a recording entry on one server

Create a recording entry