Keys / Expo

EXPO_TOKEN

The Expo access token EAS CLI builds, submits and updates with in CI, without eas login.

Expires
the docs don't say
API
none documented; dashboard only

Get it

Create one on expo.dev/settings/access-tokens. The steps aren't recorded yet.

Set it

EXPO_TOKEN=...

EAS CLI and Expo CLI read it on their own. The expo-github-action takes it as token. Or keep it out of .env with keypin: keypin run -- npm run dev

Replace it

  1. Create a new token: a personal access token with the same Limit access setting, or a new token for the same robot user. A robot user's role sets what its tokens can do.
  2. Put it in every CI secret named EXPO_TOKEN.
  3. Check that builds still run, then delete the old token on the Access tokens page.

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