Error: Invalid token (Vercel CLI)

Error: Invalid token (Vercel CLI)

TL;DR: your Vercel token expired or was revoked. Make a new one at vercel.com/account/tokens, then either run vercel login or set the new value as VERCEL_TOKEN. Verify with vercel whoami.

Error: Invalid token

Steps

1. Confirm the symptom:

vercel whoami

Expected on success: your username. Error: Invalid token means the stored credential is dead.

1. Generate a fresh token from the Vercel dashboard under Settings → Tokens → Create. Give it full access if the CLI needs to deploy.

1. Use it. Interactive:

vercel login

Expected: follow the prompts until it reports you are logged in. Headless or CI: set VERCEL_TOKEN in the environment to the new value. If you are unsure the token is right, test one call with it inline first: vercel list --token [your token].

1. Verify:

vercel whoami

Expected: prints your account name.

When this applies

• the exact Error: Invalid token on commands that used to work
• CI failures right after someone rotated or revoked tokens in the dashboard
• a token copied from an old machine that has since been regenerated

When it doesnt

• Error: No token found — run vercel login; there is no token at all
• Error: Team not found — wrong VERCELORGID, that is org config not auth
• fetch or network failures — that is connectivity, not credentials

Compatibility

Vercel CLI 28 and up.

Why it happens

The CLI stores one long-lived token, in the global config or in VERCEL_TOKEN. Vercel invalidates it on expiry, manual revocation, or regeneration — and the CLI has no refresh flow, so every call fails until you replace the token.

Edge cases

• tokens for CI should be short-lived (90 days) and rotated on a schedule
• never commit the token — it is a full-access credential; store it as a CI secret
• if the team enforces SSO, the interactive login must go through the SSO flow or the new token wont be accepted

Find this skill again

curl -s 'https://vectle.com/api/v1/search?q=vercel+cli+error+invalid+token'