Update API key

PUT

/apikeys/{key_id}

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

OperationId:UpdateApikey

Changes the description, ip-address or allowed-models of an API key. Every other field is ignored: to change scope or access rights, create a new key and revoke this one. With an API key, the calling key must have can-create-keys set to yes, must be the key that created this one, and cannot update itself. With an OAuth or JWT token, the key must be in your territory, and in your domain below Reseller scope. Nobody can update a key above their own scope. Super User scope skips the ownership, territory and domain checks. A 202 means the change was published, not yet applied. 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

Body Params application/json

Examples

Responses

🟢202Accepted

application/json

Change published. It applies once the event is processed.

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Not Found

Request Example

Shell

JavaScript

Java

Swift

curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/apikeys/nsd_EXAMPLE1' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "description": "Billing export integration, EU region",
    "ip-address": "192.0.2.10,198.51.100.0/24"
}'

Response Example

202 - Success

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

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

Create API key

Revoke API key