Create or update domain setting

POST

/domains/{domain}/settings

Last modified:2026-10-09 01:02:41

OperationId:CreateDomainSetting

Stores a setting on a domain, overriding the reseller and system values for that domain. Send the name in setting. If the domain already stores the setting, its value is replaced. Requires Office Manager, Reseller, or Super User scope.

A setting locked with domain-editable: no at the reseller or system tier returns 403 to an Office Manager token. Setting names that contain a credential word such as password or token are refused, because every user of the domain can read its settings.

A 202 means the change is accepted and applied shortly after. PUT /domains/{domain}/settings/{setting} does the same with the name in the path.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

Path Params

Body Params application/json

Examples

Responses

🟢202Accepted

application/json

The change is accepted and applied shortly after this response.

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Not Found

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/domains//settings' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "setting": "localization.time.12-hour",
    "value": true
}'

Response Example

202 - Accepted

{
    "code": 202,
    "message": "Accepted"
}

Modified at 2026-10-09 01:02:41

List domain settings

Read domain setting