Revoke a member's token in a workspace

Take a member's token out of the workspace, with an optional reason its owner is shown.

POST/workspaces/{workspace}/personal-access-tokens/{id}

A token made for this workspace stops reaching it for good; a token made for all of its owner’s workspaces keeps working everywhere else but never reaches this one again. Recorded in the audit log as token.revoked. Owners only, as people.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: workspace with action revoke_member_token, and the same inputs
Scope: An access token needs access:admin.

Path parameters

Name	Type	Required	Description
`workspace`	string	Yes	The workspace’s name, e.g. “acme”.
`id`	string	Yes	The token’s id, tok_….

Body parameters

Send a JSON object. Names are snake_case, as in responses; the camelCase spelling is accepted too.

Name	Type	Required	Description
`reason`	string	No	Why, shown to the token’s owner.

Example request

curl -X POST https://api.g1t.sh/workspaces/flagon-io/personal-access-tokens/tok_01HZX3K2M9V7Q4N8B6D5C3A2E1 \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "reason": "Rotated after the laptop was lost"
  }'

Example response

A successful request answers 200 with:

{
  "revoked": true
}

Errors

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status	Code	When
401	`unauthenticated`	A token is required, or the one sent is not valid.
403	`forbidden`	The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404	`not_found`	It does not exist, or you cannot see it.
409	`conflict`	The request conflicts with the current state.
422	`invalid`	The input is not valid. `message` says which field and why.