> ## 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.

# PagerDuty

> Connect PagerDuty to Iru Compliance with a read-only REST API key to collect incidents, services, escalation policies, and on-call evidence.

### 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):

```http theme={null}
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

PagerDuty REST API keys are sent with PagerDuty’s custom header format **`Authorization: Token token=<API_KEY>`** (this is **not** a generic **`Bearer`** token).

| Detail             | Value                                         |
| ------------------ | --------------------------------------------- |
| **Category**       | Incident response / operations                |
| **Authentication** | REST 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](https://support.pagerduty.com/main/docs/api-access-keys), [REST API reference](https://developer.pagerduty.com/api-reference/), and [Rate limiting](https://developer.pagerduty.com/docs/rest-api-v2/rate-limiting/).

### Prerequisites

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

### Connect PagerDuty to Iru

<Tabs>
  <Tab title="PagerDuty">
    <Note>
      Complete this tab before you connect the source in Compliance.
    </Note>

    <Steps>
      <Step title="Sign in to PagerDuty">
        Open [PagerDuty](https://www.pagerduty.com) and sign in with an **Admin** or **Account Owner** (or equivalent) who can create **API Access Keys**.
      </Step>

      <Step title="Open Integrations">
        From the product navigation, open **Integrations** (sometimes under **Automation** or **Developer**, depending on your PagerDuty edition).
      </Step>

      <Step title="Open Developer Tools">
        Select **Developer Tools** (or **API Access**), then locate **API Access Keys**.
      </Step>

      <Step title="Create a new API key">
        Choose **Create new API key** (wording may read **New key**). Prefer a **General Access** key when org policy allows so Iru reads are not tied to a single human user’s visibility.
      </Step>

      <Step title="Name the key and set Read-only">
        Enter a name such as **Iru Compliance**. Set the key type to **Read-only** (or the least-privilege read option PagerDuty offers for REST evidence collection).
      </Step>

      <Step title="Create and copy the key">
        Finish creation and copy the key value **once** when PagerDuty shows it. It is not shown again after the dialog closes.
      </Step>
    </Steps>

    <Note>
      Continue on the [**Iru Compliance**](#iru-compliance) tab.
    </Note>
  </Tab>

  <Tab title="Iru Compliance">
    <Note>
      Finish the [**PagerDuty**](#pagerduty) tab first.
    </Note>

    <Steps>
      <Step title="Open Sources">
        In Iru Compliance, on the left navigation bar, expand **Compliance** and select **Sources**.

        <Frame>
          <img src="https://mintcdn.com/iru/7HsGH7lnQ8GpVmI0/assets/media/images/iru-navigation-compliance-sources.png?fit=max&auto=format&n=7HsGH7lnQ8GpVmI0&q=85&s=595982441fd777b333b3ecfea24adc24" alt="Left navigation: Compliance expanded, Sources selected" width="424" height="1056" data-path="assets/media/images/iru-navigation-compliance-sources.png" />
        </Frame>
      </Step>

      <Step title="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.
      </Step>

      <Step title="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.
      </Step>

      <Step title="Finish the connection">
        Click **Submit API Key**. When the connection succeeds, the wizard shows **Connection Configured**.
      </Step>

      <Step title="Confirm the source is Active">
        Close the **Iru is requesting access to external services** browser tab, then return to **Compliance** → **Sources** and confirm the **PagerDuty** card is **Active**.
      </Step>
    </Steps>
  </Tab>
</Tabs>

### Troubleshooting

<AccordionGroup>
  <Accordion title="Nothing opens when you turn the source on">
    Check **pop-up blocker** settings for the Iru site and try again.
  </Accordion>

  <Accordion title="401 Unauthorized">
    Full key, no spaces; key not disabled.
  </Accordion>

  <Accordion title="403 Forbidden">
    Switch from a **User** token to a **General Access** key with sufficient scope.
  </Accordion>

  <Accordion title="Missing services or schedules">
    User-scoped tokens only see that user’s teams. Use **General Access**.
  </Accordion>
</AccordionGroup>

### Considerations

<CardGroup cols={2}>
  <Card title="API keys do not auto-expire: rotate on a schedule." icon="circle-info">
    API keys do not auto-expire - rotate on a schedule.
  </Card>

  <Card title="Large backfills stay within PagerDuty rate limits;…" icon="shield">
    Large backfills stay within PagerDuty **rate limits**; sync may spread over time.
  </Card>
</CardGroup>

### Related Articles

<CardGroup cols={2}>
  <Card title="Sources Management" icon="plug" href="/en/compliance/sources-management">
    Browse and manage every Compliance source.
  </Card>

  <Card title="Getting Started With Compliance" icon="rocket" href="/en/compliance/getting-started-with-compliance">
    Frameworks, actions, and **Artifacts**.
  </Card>

  <Card title="Iru Overview" icon="layer-group" href="/en/iru/platform-overview/iru-overview">
    How Endpoint, Compliance, and Identity fit together.
  </Card>

  <Card title="Artifacts Management" icon="folder-open" href="/en/compliance/artifacts-management">
    Upload, review, and organize evidence from sources and actions.
  </Card>
</CardGroup>