Read recording server

GET

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

Last modified:2026-10-30 21:04:54

OperationId:ReadRecordingserver

Returns one recording server as the core server that takes the request sees it, with that core server's enabled and hostname. Other core servers are not asked. Requires Super User or Super User Read Only scope. To see it on every core server, use GET /recordings/coreservers.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

Path Params

Responses

🟢200OK

application/json

The recording server, as the core server that takes the request sees it.

Bodyapplication/json

🟠401Authentication Required

🟠403Forbidden

🟠404Record not found

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/recordings/servers/Recording-Server2' \
--header 'Authorization: Bearer <token>'

Response Example

200 - Recording server

{
    "recording-server-id": "Recording-Server2",
    "hostname": "core1.example.com",
    "name": "Secondary recording server",
    "address": "100 Main Street, Springfield",
    "contact": "Network Operations",
    "phone": "15555550100",
    "email": "admin@example.com",
    "ccc-ip": "192.0.2.10",
    "ccc-port": 9000,
    "cdc-url": "https://recording1.example.com/cdc",
    "cdc-type": "http",
    "enabled": "yes",
    "entry-count": 42
}

Modified at 2026-10-30 21:04:54

Create recording server

Update recording server