Delete NMS configuration entry

DELETE

/nmsconfig/{config-name}

Last modified:2026-10-09 00:45:29

OperationId:DeleteNmsConfig

Deletes a key and replicates the delete to every core server.

Requires Super User.

The delete matches the key alone. It is published over the service bus (SBUS), so 202 means accepted, not yet applied; deleting a key no server holds also answers 202. With synchronous=yes, a server reports config-applied: yes once it no longer holds the key.

Send config-server to delete the key on one server only, with the same effects as on PUT /nmsconfig/{config-name}.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

Path Params

Query Params

Responses

🟢200OK

application/json

With synchronous=yes: one row per core server; config-applied: yes means the server no longer holds the key.

Bodyapplication/json

🟢202Accepted

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Not Found

🔴502Bad Gateway

Request Example

Shell

JavaScript

Java

Swift

curl --location --request DELETE 'https://awqacore01.crexendocloud.com/ns-api/v2/nmsconfig/SMTP_HOST?synchronous=undefined&synchronous-timeout=undefined&verify=yes&verify-timeout=3000&config-server=core2.example.com' \
--header 'Authorization: Bearer <token>'

Response Example

200 - synchronous=yes

[
    {
        "config-name": "SMTP_HOST",
        "config-server": "core1.example.com",
        "config-applied": "yes"
    },
    {
        "config-name": "SMTP_HOST",
        "config-server": "core2.example.com",
        "config-applied": "yes"
    }
]

Modified at 2026-10-09 00:45:29

Update NMS configuration entry

List recording configuration entries