Keys / Doppler
DOPPLER_TOKEN
The Doppler service token your app reads secrets from one config with, through the Doppler CLI.
- Starts with
dp.st.- Expires
- never, unless you set an expiration
- API
- create, list and delete service tokens
Get it
Create one on dashboard.doppler.com. The steps aren't recorded yet.
Set it
DOPPLER_TOKEN=dp.st....
The Doppler CLI reads it in place of its stored login, so doppler run injects that config's secrets. Or keep it out of .env with keypin: keypin run -- npm run dev
Replace it
- In the config's Access tab, generate a new service token with the same access, or run
doppler configs tokens create. - Deploy it everywhere that reads
DOPPLER_TOKEN. - Check that nothing still uses the old token, then revoke it in the Access tab or with
doppler configs tokens revoke.
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.