Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.iru.com/llms.txt

Use this file to discover all available pages before exploring further.

​
About PagerDuty

Iru reads incidents, services, escalation policies, schedules, teams, and audit data through the PagerDuty REST API. Authentication uses PagerDuty’s header format (not plain Bearer): 
Authorization: Token token=YOUR_API_KEY
Prefer a General Access REST API key with read-only scope so Iru cannot change incidents or services.

​
How it works

DetailValue
CategoryIncident response / operations
AuthenticationREST API key (Authorization: Token token=…)
General Access keys are created by admins and can cover the whole account. User tokens inherit that user’s visibility. Avoid them unless you intentionally restrict scope. Official references: API access keys, REST API reference, and Rate limiting.

​
Prerequisites

  • Admin or Account Owner (or equivalent) to create General Access API keys.

​
Connect PagerDuty to Iru

​
PagerDuty

1

Create a read-only REST API key

In PagerDuty, open Integrations → Developer Tools → API Access Keys. Create a new key, name it (for example Iru Compliance), choose Read-only, and copy the key once the dialog closes. It is shown once.

​
Iru Compliance

1

Open Sources

In Iru Compliance, on the left navigation bar, expand Compliance and select Sources.
Left navigation: Compliance expanded, Sources selected
2

Turn on PagerDuty

Find PagerDuty (use Category or Search by name or description). On that card, turn on the toggle. A browser tab or window may open for the connector wizard.
3

Paste the API key

Paste the raw API key into the field the wizard provides. The product formats Authorization: Token token=YOUR_API_KEY for you. Do not prefix Token token= yourself.
4

Confirm the source is Active

Submit until the PagerDuty card is Active.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
Full key, no spaces; key not disabled.
Switch from a User token to a General Access key with sufficient scope.
User-scoped tokens only see that user’s teams. Use General Access.

​
Considerations

API keys do not auto-expire: rotate on a schedule.

API keys do not auto-expire - rotate on a schedule.

Large backfills stay within PagerDuty rate limits;…

Large backfills stay within PagerDuty rate limits; sync may spread over time.

​
See also