Keys / Vercel

VERCEL_TOKEN

The Vercel access token the Vercel CLI deploys with in CI, and your scripts call the REST API with.

Starts with
vcp_
Expires
you choose when you create it
API
create, list and delete

Get it

Create one on vercel.com/account/tokens. The steps aren't recorded yet.

Set it

VERCEL_TOKEN=vcp_...

The Vercel CLI reads it when you don't pass --token; the Vercel SDK doesn't, so the app passes it in as bearerToken. Or keep it out of .env with keypin: keypin run -- npm run dev

Replace it

  1. Create a new token with the same scope: full account, one team or one project.
  2. Deploy it everywhere that reads VERCEL_TOKEN.
  3. Check that nothing still uses the old token, then delete it on the Account Tokens page or with vercel tokens revoke <id>.

Set rotate_every on the key in keypin.toml and a rotated date on its vault item, and keypin status shows when it's due.

Sources, checked 2026-11-16