How DSALTA integrates with PagerDuty — data collected, setup guide, and automated compliance checks.
Overview
How to connect
Automated checks
Useful links
DSALTA connects to PagerDuty using read-only API access to collect compliance evidence automatically. Data feeds into your Data Library modules. DSALTA reads your account users (email and role) and services to power access reviews.
Read-only access. DSALTA never modifies, creates, or deletes resources in your PagerDuty account.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.
DSALTA reads the PagerDuty user roster — names, emails and roles, which appears on your Access page; and your PagerDuty resources, which appear on your Inventory page. PagerDuty’s user list carries no active or suspended status, so every member is listed as Active.It calls these PagerDuty endpoints:
/users?limit=1
/users?limit=…&offset=…
/services?limit=…&offset=…
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your PagerDuty environment.
There is no Reconnect button. Open Integrations → Connected, click Manage on the PagerDuty card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from PagerDuty. This usually happens when the REST API key was deleted or rotated in PagerDuty. Create a new key and reconnect.
Data is not syncing
Confirm the REST API key is still valid and has read access to users. If the key was removed, generate a new one under Integrations → Developer Tools → API Access Keys and reconnect, then click Sync from integrations on the Integrations page (Connected tab) — it refreshes every connected integration at once.
PagerDuty REST API key with read access to users and services. Read-only.Before you begin
A PagerDuty account (free tier works)
Account admin or owner access to create a REST API key (Integrations → Developer Tools → API Access Keys)
A General Access (account-level) REST API key, created by an Admin or the Account Owner — not a personal “User Token” key. On accounts with Advanced Permissions enabled, a personal key is restricted to its creator’s own permissions, which can make DSALTA sync an incomplete user list.
Open Integrations in the DSALTA sidebar, find PagerDuty, and click Connect to open the connect panel. Leave it open — it lists every value you need, and you create those in the steps below.
2
Create a REST API key
In PagerDuty, open Integrations → Developer Tools → API Access Keys. Click Create New API Key, add a description (for example, DSALTA), and — optionally — check Read-only API Key. Click Create Key and copy the key now; it is shown only once. The free tier supports REST API keys; no paid or enterprise plan is required.Tick Read-only API Key. PagerDuty restricts a read-only key to GET calls, and DSALTA only ever issues GETs (/users, /services), so a read-only key is sufficient — and it makes the read-only claim verifiable inside PagerDuty.PagerDuty makes the REST API available to all accounts on its current pricing plans, including Free — but not to some accounts still on legacy pricing plans. If the API Access Keys page is missing, check which plan your account is on.
3
Connect PagerDuty
Paste the REST API key, then click Connect.
DSALTA validates the credential when you click Connect. On success the integration moves to the Connected tab, and Manage → Status reads Connected and working properly. Checks begin reporting after the first sync.
If the connection is rejected. Invalid API key, or it lacks read access to users.The on-screen message is generic — see Connection error messages.
Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)