Keys / PagerDuty

PAGERDUTY_API_KEY

A REST API key your app calls the PagerDuty API with: a general access key for the account, or a user token with one user's permissions.

Expires
the docs don't say
API
none; web app only

Get it

Create one on app.pagerduty.com. The steps aren't recorded yet.

Set it

PAGERDUTY_API_KEY=...

No official PagerDuty library reads this variable. The Terraform provider reads PAGERDUTY_TOKEN, and the MCP server reads PAGERDUTY_USER_API_KEY; elsewhere, the app passes it in. Or keep it out of .env with keypin: keypin run -- npm run dev

Replace it

  1. For a general access key, an Admin creates one under Integrations, Developer Tools, API Access Keys, with the same read-only setting. For a user token, use My Profile, User Settings, API Access.
  2. Deploy it everywhere that reads PAGERDUTY_API_KEY. Both keys work in the meantime.
  3. Check that nothing still uses the old key. Disable a general access key first if you want a way back, then remove it.

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