Update custom scope

PUT

/scopes/{name}

Last modified:2026-10-07 23:37:20

OperationId:updateCustomScope

Changes a custom scope. Requires Super User scope. Super User Read Only can read scopes but cannot change them, and neither can a custom scope, even one derived from Super User.

Send only the fields to change. modifications replaces the whole map. Changes apply to tokens already issued within seconds, and enabled: no refuses them until you enable the scope again. The name cannot be changed.

For a built-in scope name, only hidden can be sent. hidden controls only whether a scope appears in GET /scopes. It does not change what the scope can do or who holds it. Any other field is a 400.

The response is 202: the change is accepted and applied shortly after.

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/jsonRequired

Examples

Responses

🟢202Accepted

application/json

The change is accepted and applied shortly after.

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Not Found

Request Example

Shell

JavaScript

Java

Swift

cURL

Change the limitsDisable the scopeHide a built-in scope

curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/scopes/Platform Manager' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "modifications": {
        "nsconfig": "none",
        "route": "ro",
        "phonenumber": "none"
    }
}'

Response Example

202 - Change the limits

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

Modified at 2026-10-07 23:37:20

Read custom scope

Delete custom scope