Revoke Login Token

Immediately invalidate a login token, ahead of its natural 10-day expiry.

Use this when a token has leaked, an integration is being rotated, or a session should be terminated. From the moment this call returns, the revoked token is rejected by every endpoint.

Rules:

  • The bearer token you authenticate with must be minted for the organisationId in the URL and carry the CRM_ADMIN, ACCOUNT_OWNER, or CRM_BOT role.
  • The token being revoked must also belong to that organisation — you cannot revoke another organisation's tokens.
  • Revoking the token you are authenticating with (self-logout) is allowed.
  • Revocation is permanent and idempotent; mint a replacement via POST /token.
  • Tokens issued before revocation support cannot be revoked individually — they expire on their own within 10 days of issue.
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Your organisation UUID (returned as org from the /token endpoint)

Body Params

The token to revoke

string
required

The login token (JWT) to revoke. Must have been minted for the organisation in the URL. Revocation is immediate and permanent — the token is rejected by all endpoints from that point on.

Responses

400

Token is invalid, already expired, or predates revocation support

401

Unauthorized — bearer token invalid/expired or organisation ID does not match it

403

Forbidden — caller lacks the required role, or the token being revoked belongs to a different organisation

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json