List recording servers by core server

GET

/recordings/coreservers

Last modified:2026-10-04 00:04:56

OperationId:ListRecordingCoreservers

Lists which recording servers are enabled on each core server: one row per core server and recording server, sorted by hostname and then recording-server-id.

Requires Super User or Super User Read Only scope.

The core server that takes the request asks every other core server. A core server that does not answer within 3 seconds has no rows. To change one core server, use PUT /recordings/coreservers/{hostname}.

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

One row per core server and recording server. No recording servers returns an empty array.

Bodyapplication/json

🟠401Authentication Required

🟠403Forbidden

🟠404Record not found

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/recordings/coreservers?hostname=core1.example.com&preventremote=1' \
--header 'Authorization: Bearer <token>'

Response Example

200 - Two core servers

[
    {
        "hostname": "core1.example.com",
        "recording-server-id": "Recording-Server2",
        "enabled": "yes"
    },
    {
        "hostname": "core1.example.com",
        "recording-server-id": "Recording-Server3",
        "enabled": "yes"
    },
    {
        "hostname": "core2.example.com",
        "recording-server-id": "Recording-Server2",
        "enabled": "no"
    },
    {
        "hostname": "core2.example.com",
        "recording-server-id": "Recording-Server3",
        "enabled": "yes"
    }
]

Modified at 2026-10-04 00:04:56

Delete recording entry

List recording servers on core server