Docs · Connect your tools
Connect PagerDuty
StackWeaver reads, and never changes, one read-only endpoint on your PagerDuty account once a day, through an API key you create yourself. This guide says exactly what is read, which permission the key needs, how to create one, and how to remove it.
Last reviewed: 6 November 2026 · Describes what is live in production on that date. A result is evidence of what the provider returned at a time, nothing more.
1. What it collects
Once a day StackWeaver calls PagerDuty's REST API with the key you paste. The result is kept as an Evidence Object with a SHA-256 fingerprint (platform), including a result that fails.
| Check (as shown in the portal) | What it looks at |
|---|---|
| API key valid and reachable | Whether the stored key is accepted and PagerDuty's own abilities list responds, listing the plan feature names your account has. Evidence only: no threshold is applied. |
2. What it does not do
- It never reads an incident, schedule or person. The one check reads only the list of plan feature names your account has.
- It cannot change anything: the key is used for one read-only endpoint.
- It does not say your incident-response programme meets any requirement. A result is what PagerDuty returned at a certain time.
3. The access it needs
One credential: an API key, sent as `Authorization: Token token=<API_KEY>` on every request (PagerDuty).
Who can connect. In StackWeaver, a workspace owner or admin pastes the key. PagerDuty does not tell StackWeaver who created the key or what role they hold, so create it with no more access than this one read-only check needs.
4. Connect steps
- In PagerDuty, open Integrations → API Access Keys and create a new key (read-only if offered).
- In StackWeaver, open Evidence, the PagerDuty section, and paste the key.
- Press Test connection. StackWeaver records the result and fills in the account fingerprint automatically.
5. Reading the results
| Label | What it means |
|---|---|
| Pass | The provider returned data that meets the threshold at that time |
| Fail | The provider returned data that does not meet the threshold |
| Not enabled | There was nothing to check, or the feature needs a plan StackWeaver could not confirm |
| Could not check | StackWeaver could not read the data, or the check needs a higher plan than the account has |
6. Disconnect and revoke
- In StackWeaver, press Disconnect on the PagerDuty section. StackWeaver deletes the stored key.
- In PagerDuty, revoke or delete the key yourself — StackWeaver has no way to ask PagerDuty to revoke a key on your behalf.
What remains. Past evidence stays in your workspace as the audit trail. Disconnecting does not delete it.
7. Troubleshooting
| Message | What to do |
|---|---|
| PagerDuty refused the key: it may be wrong or revoked | Check the key was copied in full and has not been deleted in PagerDuty |
| This key belongs to a different PagerDuty account than the one already connected here | Disconnect first if you mean to switch to a different PagerDuty account |
Still stuck? Use the contact page.
Sources and method
Statements about GitHub and Okta link to their own documentation. Statements about StackWeaver link to the page that says them, or are recorded in a claims ledger with the file in StackWeaver's repository that they come from. See oureditorial policy. Spotted an error? Use the contact page.