Revoke token with reason

post

https://zyins.isaapi.com/v1/tokens/{id}/revoke

Marks a token as revoked with a recorded reason; the secret stops working immediately. To undo a mistaken revocation while the token is still in revoked state, see Reinstate a revoked token — banned tokens cannot be reinstated.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

string

required

Token identifier

Body Params

reason

string

required

Reason for revocation

Headers

Idempotency-Key

string

Client-supplied idempotency token for mutating versioned API requests
(POST, PUT, PATCH, DELETE under /v1/* and /v2/* where listed).

When the service has already completed a request for the same
account, route, key, and identical JSON body within the replay window,
it returns the stored HTTP status and body instead of executing again.

Reusing the same key with a different body returns 409 Conflict
(see 409 / Idempotency conflict responses on those operations). Keys
expire after 24 hours. Prefer a new UUID v4 per distinct logical operation.

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Responses

200Token revoked with reason recorded

400Invalid request parameters

401Authentication required or invalid

403Insufficient permissions

404Resource not found

409Idempotency key reused with a different request body than the completed replay entry for the same account, endpoint, and key.

429Rate limit exceeded

500Internal server error