Updated 2026-07-01
On plans with API access, Status exposes a public v1 API so you can manage monitoring from your own scripts, infrastructure-as-code, or internal tools instead of only the dashboard.
Creating a key
From account settings, create an API key and choose which scopes it can use. A key must have at least one scope — there's no such thing as a scope-less key. The full secret is shown once at creation time; after that, only a masked version is shown, so store it somewhere safe when you create it.
Available scopes
| Scope | Grants |
|---|---|
checks:read |
Read checks and their configuration |
checks:write |
Create, update, and delete checks |
results:read |
Read check results and uptime data |
incidents:read |
Read incidents |
incidents:write |
Acknowledge and update incidents |
channels:read |
Read alert channels |
channels:write |
Create, update, and delete alert channels |
maintenance:write |
Create and manage maintenance windows |
Give a key only the scopes it actually needs — a read-only integration
should use checks:read/results:read, not a key with write access to
everything.
Using a key
Send the key as a bearer token:
Authorization: Bearer status_<prefix>_<secret>
Requests are rate-limited per key, so design integrations to react to events rather than polling aggressively.
Plan limits
Your plan controls whether API access is available at all, and how many API keys you can have at once. See Choosing a plan for specifics.