Revoke user tokens

DELETE 
/v1/users/:user_id/tokens

Revokes every token issued so far to one of the project's end users, e.g. when one may have leaked: each is refused from then on as an invalid token (invalid_token). Tokens issued afterwards work.

Request

Responses

204

Successful Response

401

Authentication failed: the credential is missing, malformed, expired, or revoked.

• invalid_token — The access token is invalid.
• project_disabled — This project is not active.
• token_expired — The access token has expired.
• user_disabled — This user is not active.
• invalid_secret — The API secret is invalid.

403

The caller is authenticated but not permitted to perform this action.

• permission_denied — You do not have permission to perform this action.
• project_disabled — This project is not active.

404

The requested resource does not exist, or is not visible to the caller.

• project_not_found — The requested project was not found.
• user_not_found — The requested user was not found.

422

A request value failed validation; the details array names each offending field.

• validation_failed — The request payload failed validation.

429

Either too many requests (a Retry-After header says when to retry) or the billing account is out of credits (no Retry-After — top up to continue); the code field tells the two apart.

• rate_limited — Too many requests. Please slow down.

500

An unexpected server-side error occurred.

• internal — An unexpected error occurred.