Open Status
Scoped API keys

Scoped API keys

Create scoped credentials for scripts and integrations.

API keys provide non-browser access to Status. Manage them from Settings → Security & sessions → API keys, or from the Operations toolkit.

A key is bound at creation to the organization the creator was acting in, and it can only ever read and write that organization's data—switching organizations in the console does not change what an existing key reaches. A key stops working if its owner leaves that organization.

Create a key

Give the key a name and choose:

  • an expiration (30 days, 90 days, 1 year, or Never);
  • one or more scopes. Write permissions also allow reads for the same resource:
    • Read monitors (monitors:read)
    • Manage monitors (monitors:write)
    • Read deployment events (events:read)
    • Ingest deployment events (events:write)
    • Read incidents (incidents:read)
    • Manage incidents and external alerts (incidents:write)

Status reveals the bearer token only when the key is created or rotated—copy it then, because it is not shown again. Only a fingerprint of the token is stored.

Rotate and revoke

  • Rotate issues a new secret immediately; the old one stops working and the new one is revealed once.
  • Revoke disables the current token without deleting its audit history.

Each key row shows its prefix, expiration, last-used time, scopes, and state (Active, Expired, or Revoked). Creating keys requires Admin; creating, rotating, and revoking are recorded in the organization's audit log.

Pass the credential in the standard authorization header:

Shell
curl \
  -H 'Authorization: Bearer status_…' \
  https://status.example.com/api/monitors

See Automation API for the endpoints each scope opens.

Related documentation