PagerDuty
Published on May 25th, 2026Introduction
The Context Store has several PagerDuty templated Data Sources to allow users to quickly pull relevant data into their Data Store. These templates are a starting point and often you'll want to apply filters or chained Data Sources to modify these templates to suit your needs.
Authentication
The built-in pagerduty integration uses token/header auth.
PagerDuty REST API tokens are commonly account/user tokens without granular endpoint scopes, so the "permissions" below are listed as required read access domains.
For least privilege:
- Use a read-only PagerDuty API token (or equivalent service account token).
- Ensure the token's user/account context can read incidents, services, users, teams, escalation policies, schedules, and on-calls.
- If your PagerDuty setup restricts object visibility by team/business service, verify that the token identity can see the target scope.
Pre-built Data Sources
This table lists the PagerDuty API permissions needed for the PagerDuty data source seeds currently defined in this repo.
| Data source seed | PagerDuty endpoint(s) used | Required token permission(s) |
|---|---|---|
PagerDuty incidents | GET /incidents | Read access to incidents |
PagerDuty services | GET /services | Read access to services |
PagerDuty users | GET /users | Read access to users |
PagerDuty teams | GET /teams | Read access to teams |
PagerDuty escalation policies | GET /escalation_policies | Read access to escalation policies |
PagerDuty schedules | GET /schedules | Read access to schedules |
PagerDuty on-calls | GET /oncalls | Read access to on-calls |
