List recording servers holding LiCf configuration

Developing

GET

/recordings/config/servers

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

OperationId:ListLicfConfigServers

One row per recording server: whether it answered, how many configuration rows it holds, and how many of those disagree with the other servers.

The server list comes from the recording-server inventory, not from what answered. A server that errors or times out is reported with reachable: no and null counts — deriving the list from the responses would report an unreachable server as one holding no configuration at all, which is the opposite of what an operator needs to see.

The inventory is the set of cluster servers carrying a recording-server package, and it is cached for 10 minutes. A newly built recording server can therefore take up to that long to appear here and in the fan-out; a decommissioned one takes the same to disappear, and shows as unreachable until it does.

Requires the Super User or Super User Read Only scope.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

Responses

🟢200OK

application/json

One row per recording server

Bodyapplication/json

🟠401Unauthorized

🟠403Forbidden

🟠405

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/recordings/config/servers' \
--header 'Authorization: Bearer <token>'

Response Example

200 - Example 1

[
    {
        "config-server": "string",
        "config-server-local": "yes",
        "config-server-reachable": "yes",
        "config-server-config-count": 0,
        "config-server-out-of-sync-count": 0
    }
]

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

Create a LiCf configuration entry

Read a LiCf configuration entry