Delete custom scope

DELETE

/scopes/{name}

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

OperationId:deleteCustomScope

Deletes 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.

Tokens issued under it are refused with 403 from their next request once the delete is applied. Users and API keys still assigned the scope cannot log in until you assign another one. To stop a scope without deleting it, set enabled to no.

For a built-in scope name, this clears its hidden setting back to the default and deletes nothing. It returns 404 when no setting is stored.

The response is 202: the delete 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

Responses

🟢202Accepted

application/json

The delete is accepted and applied shortly after.

Bodyapplication/json

🟠401Unauthorized

🟠403Forbidden

🟠404Not Found

Request Example

Shell

JavaScript

Java

Swift

curl --location --request DELETE 'https://awqacore01.crexendocloud.com/ns-api/v2/scopes/Platform Manager' \
--header 'Authorization: Bearer <token>'

Response Example

202 - Deleted

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

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

Update custom scope

List system settings