Revoke API key

DELETE

/apikeys/{key_id}

Last modified:2026-09-26 01:45:02

OperationId:RevokeApikey

Revokes an API key. The key stops working on each node once the revocation is applied there, and a 202 means the revocation was published. With an API key, the calling key must be the key that created this one. With an OAuth or JWT token, the key must be in your territory, and in your domain below Reseller scope. Nobody can revoke a key above their own scope. Super User scope skips the ownership, territory and domain checks. Keys that this key created stay active unless you send revoke_child_keys. An unknown key_id returns 404.

Request

Authorization

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

Path Params

Query Params

Responses

🟢202Accepted

application/json

Revocation published. The key stops working on each node once the event is processed there.

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Not Found

Request Example

Shell

JavaScript

Java

Swift

curl --location --request DELETE 'https://awqacore01.crexendocloud.com/ns-api/v2/apikeys/nsr_EXAMPLE1?revoke_child_keys=' \
--header 'Authorization: Bearer <token>'

Response Example

202 - Success

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

Modified at 2026-09-26 01:45:02

Update API key

Get API key