Feature · Platform

API tokens

Manage access tokens for your tools and agents.

Last changed

Generated from commit be57775 ·

How it works

Create a token

  1. On API tokens, give the token a name, for example "CI pipeline".
  2. Choose a role: Member, Viewer, Approver or Admin. A token cannot be an owner, and it cannot have a higher role than yours.
  3. Choose when it expires: 7, 30, 90, 180 or 365 days. The default is 90 days.
  4. Copy the token now. Agent shows it only one time.

What a token cannot do

A token never manages people or other tokens. Some calls, such as data export and member roles, accept only a person signed in to the browser.

Statuses

Active, Expired and Revoked. Revoking a token cannot be undone.

Who can manage tokens

Only owners and admins, signed in to the browser.

From the help article API tokens, checked against the product on .

What you can do

The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.

  • listApiTokens

    AdminNo API tokens

    Lists API tokens.

    Types: EmptyRequest returns ListApiTokensResponse

  • revokeApiToken

    AdminNo API tokens

    Revokes the API token.

    Types: RevokeApiTokenRequest returns OkResponse

  • createApiToken

    AdminNo API tokens

    Creates a API token.

    Types: CreateApiTokenRequest returns CreateApiTokenResponse

  • listMembers

    Viewer

    Lists members.

    Types: EmptyRequest returns ListMembersResponse

  • listWorkers

    Viewer

    Lists workers.

    Types: ListWorkersRequest returns ListResponse<WorkerSummary>

Screens

What it records

The feature writes these events to the audit log, the permanent record of what happened.

  • API token created
  • API token revoked
  • Member added
  • Member role changed
  • Org created
  • User signed in

Generated from code at commit be57775 ·

Turn the numbers into shipped work.

Agent runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.