Update recording servers on core server

PUT

/recordings/coreservers/{hostname}

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

OperationId:UpdateRecordingCoreserver

Enables or disables recording servers on one core server without changing the others. Requires Super User scope. The hostname and every recording server you name must be known to the cluster. PATCH works the same way.

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 core server applies the change shortly after. Read it back with GET /recordings/coreservers/{hostname}.

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/coreservers/core1.example.com' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "recording-servers": {
        "Recording-Server2": "yes",
        "Recording-Server3": "no"
    }
}'

Response Example

202 - Accepted

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

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

List recording servers on core server

Copy recording entries from server