Create a LiCf configuration entry

Developing

POST

/recordings/config

Last modified:2026-09-17 01:26:30

OperationId:CreateLicfConfig

Create a key in LiCfDomain.config_config.

The write is published on the service bus and applied by every recording server on receive, so the response is 202 — published, not applied. Pass synchronous=yes to poll until the servers converge and have config-applied reported back.

Naming one server with config-server writes there only, with no publish at all. A hostname that is not a known recording server is a 404.

A 409 is returned if the key already exists, unless overwrite=yes is passed. The underlying save is an upsert, so without this guard a POST over an existing key would silently rewrite it and answer 201.

Requires the Super User scope.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

Body Params application/jsonRequired

Examples

Responses

🟢202Accepted

application/json

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Record Not Found

🟠409

🔴502Bad Gateway

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/recordings/config' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "config-name": "string",
    "config-value": "string",
    "config-geo": "yes",
    "config-server": "string",
    "overwrite": "no",
    "synchronous": "no"
}'

Response Example

202 - Example 1

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

Modified at 2026-09-17 01:26:30

List LiCf configuration entries

List recording servers holding LiCf configuration