POST over an existing key would silently rewrite it. Pass overwrite=yes to allow it. The check is best-effort rather than a lock: the row lives on every server and another one could be writing at the same time.PUT /nmsconfig/{config-name} for how config-server and verify work; they behave identically here.Super User scope.Authorization: Bearer ********************curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/nmsconfig?overwrite=undefined&verify=undefined&verify-timeout=undefined' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"config-name": "SMTP_HOST",
"config-value": "smtp.example.com",
"config-geo": "yes",
"config-server": "core1.example.com"
}'{
"code": 0,
"message": "string"
}