config_config, the NMS key/value configuration table.config_config exists on every core server and is kept in step by the service bus, so the interesting question is usually whether the servers agree — and a read that only ever answers for the box it landed on cannot tell you. Every row therefore carries config-server, and one row is returned per (config-name, server). Pass local-only=yes for this server alone.limit applies per server, so an N-server cluster can answer up to N × limit rows.config-in-sync is no when the reporting servers disagree on that key. That covers both accidental drift and a deliberate per-server value written with config-server — nothing records intent, so the two are indistinguishable here.SMTP_PWD, SMTP_UID, licence and third-party keys are all config-name values. Any key matching password, secret, key, token, auth, smtp, license, cert (and similar) comes back masked, with config-value-redacted: yes. Per-instance exceptions are configured with NsNmsconfigMaskExempt, which ships covering SMTP_HOST and SMTP_PORT.Super User or Super User Read Only scope.Authorization: Bearer ********************curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/nmsconfig?config-name=SMTP_HOST&config-geo=undefined&local-only=undefined&include-secrets=undefined&limit=undefined&start=undefined&sort=config_name%20ASC' \
--header 'Authorization: Bearer <token>'[
{
"config-name": "SMTP_HOST",
"config-value": "smtp.example.com",
"config-geo": "no",
"config-timestamp-datetime": "string",
"config-server": "core1.example.com",
"config-value-redacted": "yes",
"config-in-sync": "yes"
}
]