Skip to content
Open App

Why has my API token stopped working?

Short Answer

API tokens can become invalid for several reasons: Someone revoked the token, the person who created it is no longer in the Workspace, or a personal access token expired after 90 days.

Details

Why does a token become invalid?

A Workspace can have up to ten access tokens at the same time; a new token does not replace any of the existing ones. A token becomes invalid when someone revoked it under Workspace settings → AI connections or when the person who created it was removed from the Workspace.

Personal access tokens under Personal settings → Connections expire after 90 days. The date is shown in the list under Expires.

Create a new token:

Open Workspace settings → AI connections, enter a name under Access token name, choose the Permission level, and click Create access token. Copy the token immediately—it will only be displayed once. After that, the list shows only the name, level, and last use, not the token itself.

Update the token in all configuration files:

If you use Claude Code, enter the new token in .mcp.json or in ~/.claude.json under PICASI_API_TOKEN. For other applications: update all locations where the old token was stored.

Tip: If multiple people on your team use the MCP server, you should store the token in a central, secure location—for example, in a password manager or as a shared secret in your development environment.