Creating an Access Token
Mint a token, copy it before it disappears, and revoke one you have lost.
An access token is how a program proves it is you. Claude Code and anything else you drive from a terminal send one with every request. Claude Desktop and claude.ai do not need one: they sign in to this application and you approve them once, with nothing pasted anywhere. If the client you are setting up is one of those, you can skip this page.
A Token Is Yours, Not a Connection's
Tokens belong to you rather than to a connection, so one token reaches every connection you have. You want one per client, not one per CRM. Two tokens named "Claude Code on my laptop" and "Claude Code at the office" are useful, because revoking one does not disturb the other.
Mint One
- Open Settings in the header, then Access Tokens.
- Under New Token, name it after the machine or the client that will hold it.
- Choose Create Token.
Copy It Immediately
The token is shown exactly once, in the panel that appears when it is created. What is stored here is a digest, not the token, and a digest cannot be turned back into a token. So a lost token is not recovered, it is replaced: revoke it and mint another.
Use the copy button rather than selecting the text by hand. Selecting by hand is where a once-only value gets truncated, and a token missing its last character fails in a way that looks exactly like a token that was never valid.
Revoking
Revoke is on the same page, beside each token, and it takes effect immediately. Any client still holding that token stops working on its next request. Revoke one you cannot account for, one you have lost, and one on a laptop you no longer have. You do not need a reason beyond doubt, because minting a replacement costs nothing.
The list shows each token's prefix and when it was last used, which is usually enough to work out which one a forgotten machine is holding.