The token has expired
HTTP status 401
This token has expired. An admin can create a new one under Settings, Developer, API tokens.
From Pro up
The token reached the expiry date it was given when it was created, and the detail field names that date. Nothing else in the request needs to change: replace the token and send it again.
Why you get it
An admin chooses how long a token lasts when creating it, and the default is 365 days. From the expiry date on, the API refuses the token with this code. The token list under Settings, Developer, API tokens marks a token when it has at most 14 days left, so you can replace it before it stops.
What to do
- An admin creates a new token under Settings, Developer, API tokens.
- Put the new token in your script or tool in place of the old one.
- If the script is meant to run for a long time, choose a longer expiry for the new token, or none at all.
An app you connected by signing in
An app you approved in a sign-in window, which reads through MCP without a token, gets the same code when its connection ends. A connection lasts 90 days from the day you approved it. The app then asks you to sign in again, and approving it starts a new connection.
Published 27 October 2026 · Checked 27 October 2026