Skip to main content
Self-manage the current workspace’s personal access tokens over the API — the twin of the Developers settings page. Tokens are scoped to the acting token’s workspace, so you only ever see and manage tokens minted for that workspace. All endpoints require Authorization: Bearer {token}. See Authentication for how a token is bound to its workspace and how the optional site allowlist works.

List tokens

List the workspace’s active (non-revoked) tokens, newest first. Response — flat JSON array of: Status: 200 OK.

Create a token

Mint a personal access token bound to the current workspace. Body parameters Response — the created token. Only this response includes the one-time plaintext token field, which is never persisted and can never be shown again. Status: 201 Created.

Revoke a token

Revoke a token. Resolved through the workspace, so a foreign/unknown id returns 404. Path parameters Status: 204 No Content.