Create or update system setting

POST

/settings

Last modified:2026-10-04 19:47:32

OperationId:CreateSystemSetting

Stores a platform-wide setting that every domain uses unless its reseller or the domain overrides it. Send the name in setting. If the system already stores the setting, its value is replaced. Requires Super User scope.

Two flags lock the setting for the tiers below:

reseller-editable: no stops Reseller tokens from overriding it for a territory

domain-editable: no stops Office Manager tokens from overriding it on a domain, unless a reseller setting sets the flag again

A 202 means the change is accepted and applied shortly after. PUT /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 ********************

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

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/settings' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "setting": "localization.date.format",
    "value": "MDY",
    "reseller-editable": "no",
    "domain-editable": "no"
}'

Response Example

202 - Accepted

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

Modified at 2026-10-04 19:47:32

List system settings

Read system setting