Set which recording servers are enabled on one core server

PUT

/recordings/coreservers/{hostname}

Last modified:2026-08-09 21:36:15

OperationId:UpdateRecordingCoreserver

Enables or disables recording servers for a single core server without disturbing the others. Because the hostname map is never stored, the API first reads the current state from every core server (each server's own enabled value is its entry in the map), merges the requested changes for {hostname}, and republishes one update per named recording server.

Only the recording servers named in the body are touched. The target hostname does not have to be reachable — it picks the change up from the bus.

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

🟢200OK

application/json

Updated successfully

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠405

Request Example

Shell

JavaScript

Java

Swift

curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/recordings/coreservers/' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "recording-servers": {
        "Recording-Server": "yes",
        "Recording-Server2": "no"
    }
}'

Response Example

200 - Example 1

{
    "code": 0,
    "message": "string"
}

Modified at 2026-08-09 21:36:15

Get one core server's recording-server enablement

Inbox