Update an NMS configuration entry

Update a configuration key.

By default the write replicates to every core server over the service bus, and the response means "published", not "applied everywhere". Delivery is batched, so there is normally a short window in which the servers disagree. Pass verify=yes to poll and get a per-server report instead of the bare acknowledgement.

config-server targets one server and skips replication entirely. Name a hostname and the value is written on that server only — nothing is published, and no other server ever sees it. Two things follow, and neither is a bug:

A later cluster-wide write to the same key (or any replication event from another publisher) overwrites the per-server value.

Nothing records that the divergence was deliberate, so a config-server override reads as config-in-sync: no, exactly like accidental drift.

Naming a hostname that is not in the cluster is a 404.

Echoing a masked value back is safe. If the value you send is exactly the mask this API emitted for the currently stored value, the stored value is kept rather than being replaced with asterisks — which matters here because a replicating write would otherwise destroy a live credential on every server at once. Sending a masked value for a key that does not exist yet is a 400; there is nothing to preserve.

Requires the Super User scope.

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

application/json

Accepted. Without verify=yes this is the bare {code, message} acknowledgement; with it, a per-server report of what has actually landed.

Bodyapplication/json

curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/nmsconfig/SMTP_HOST?verify=undefined&verify-timeout=undefined' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "config-value": "string", "config-geo": "yes", "config-server": "core1.example.com" }'

Update an NMS configuration entry

Request

Responses