orgs

Revoke Org Personal Access Token

Changed on

Revoke a personal access token, so it stops working but its record remains.

The token is marked revoked rather than deleted, and stops authenticating as soon as its cached auth entry refreshes. Its expiry is left untouched, so the revocation can be lifted by deleting it. Callers may always revoke their own tokens; organization admins may revoke any member's.

post/api/v1/orgs/current/personal-access-tokens/{pat_id}/revocation

Request

  • Base URL
    https://api.smith.langchain.com
  • URL
    https://api.smith.langchain.com/api/v1/orgs/current/personal-access-tokens/{pat_id}/revocation
  • Auth
    • API key in header X-API-Key
    • or API key in header X-Organization-Id
    • or HTTP bearer

Path parameters

pat_idstring uuid required

Response

Successful Response

created_atstring date-time nullable
idstring uuid required
short_keystring required
descriptionstring required
read_onlyboolean
last_used_atstring date-time nullable
expires_atstring date-time nullable
revoked_atstring date-time nullable
workspace_namesstring[] nullable
default_workspace_namestring nullable
role_idstring uuid nullable
org_role_idstring uuid nullable
access_scope'organization' | 'workspace'
created_bystring nullable
is_tracing_keyboolean
workspace_idsstring[]
can_deleteboolean

Whether tracing-key deletion authority has been confirmed. Legacy key responses do not evaluate this capability.

Changes