Create media converter configuration entry

POST

/recordings/nmc-config

Last modified:2026-10-30 21:12:58

OperationId:CreateNmcConfig

Creates a key in the media converter (NMC) configuration table and replicates it to every recording server, or writes it on one recording server with config-server. Requires Super User scope. An existing key returns 409 unless you send overwrite=yes; to change a key, use PUT /recordings/nmc-config/{config-name}.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

Query Params

Body Params application/jsonRequired

Examples

Responses

🟢200OK

application/json

With synchronous=yes: one row per recording server, reporting whether it holds the written value. With config-server, only that server is reported.

Bodyapplication/json

🟢202Accepted

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Not Found

🟠409Conflict

🔴502Bad Gateway

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/recordings/nmc-config?synchronous=undefined&synchronous-timeout=undefined&overwrite=yes' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "config-name": "RemoteArchiveLogRetryCount",
    "config-value": "5"
}'

Response Example

200 - synchronous=yes

recording2.example.com did not answer.

[
    {
        "config-name": "RemoteArchiveLogRetryCount",
        "config-server": "recording1.example.com",
        "config-applied": "yes"
    },
    {
        "config-name": "RemoteArchiveLogRetryCount",
        "config-server": "recording2.example.com",
        "config-applied": "unknown"
    }
]

Modified at 2026-10-30 21:12:58

List media converter configuration entries

List media converter configuration servers