Connect & Integrate Pagerduty

Last updated: August 6, 2026

Connecting PagerDuty to YeshID lets you manage who has a PagerDuty user account as part of the same onboarding and offboarding you run everywhere else. YeshID talks to PagerDuty's REST API, so when someone joins or leaves, their PagerDuty account can be created or removed automatically instead of by hand in the PagerDuty admin console.

It's a good fit when on-call and incident response run through PagerDuty and you want account access to follow the same joiner-mover-leaver rules as the rest of your stack — provisioned on day one, cleaned up on the last day, and visible in your access reviews in between.

Scope note: This integration manages PagerDuty user accounts — the accounts people use to sign in to PagerDuty — and reads their PagerDuty role. It does not manage teams, schedules, escalation policies, or on-call rotations; those stay in PagerDuty. If you're governing who has a PagerDuty login, this is it.

How it connects — REST API, not SCIM: PagerDuty is connected through its REST API using a PagerDuty API token, not a SCIM URL. Setup is about generating an API key in PagerDuty and pasting it into YeshID.

What it gives you

  • PagerDuty access on the same lifecycle as everything else — a new hire's PagerDuty account is created through onboarding, and it's removed through offboarding, without a separate manual step.

  • One place to answer "who's in PagerDuty?" — imported PagerDuty accounts show up in YeshID alongside a person's other access, so audits and access reviews include your incident-response tooling.

  • Admins are visible — YeshID reads each PagerDuty user's role, so account owners and admins are distinguishable from regular users in your access picture.

  • No leftover accounts — offboarding removes the PagerDuty account, so someone who's left doesn't keep a login after their last day.

How YeshID connects to PagerDuty

YeshID uses PagerDuty's REST API authenticated with an API token:

  • You generate an API access key in PagerDuty and paste it into YeshID once.

  • YeshID sends that key on every request in the Authorization header, in PagerDuty's classic format (Token token=<your key>), against https://api.pagerduty.com.

  • Each action is a REST call — for example, GET /users to import, POST /users to create, DELETE /users/{id} to remove.

Key terms

Term

What it means

PagerDuty user

An account that can sign in to PagerDuty. This is what YeshID imports, creates, and removes.

API token

The PagerDuty REST API key you generate once and paste into YeshID. YeshID sends it on every call as Token token=<key>.

Role

A PagerDuty user's permission level (for example owner, admin, user). YeshID reads this on import and sets it when creating a user.

Provisioner action

A single operation YeshID runs against PagerDuty — Import Users, Create User, or Delete User — each mapped to a PagerDuty REST endpoint.

Before you begin (in PagerDuty)

You'll need a PagerDuty API token that YeshID can use to call the API:

  1. Confirm you're a PagerDuty admin or account owner with rights to manage users and API access.

  2. Generate an API access key in PagerDuty (Integrations ▸ API Access Keys ▸ Create New API Key). Use a full-access (read/write) key so create and delete can work — a read-only key supports Import Users only.

  3. Copy the key when it's shown — PagerDuty displays it once.

Setting up the integration (in YeshID)

This assumes PagerDuty is already on your Applications list. If it isn't, add it first — see Adding Applications to YeshID.

  1. On the Applications page, find PagerDuty and open its Manage menu.

  2. Choose Connect, then open the Authentication section.

  3. For authentication method, choose Custom API key.

  4. Paste your PagerDuty API key into the Token field — the field with the hide/show (eye) icon near the bottom. This is the only field you need to fill in.

  5. Leave the prefilled fields as they are — they're already set correctly for PagerDuty:

    • Base URL → https://api.pagerduty.com

    • Header Name → Authorization

    • Header Value → Token token={{ .Key }}

    The Header Value is a template, not a place for your key. The {{ .Key }} in it is a placeholder — YeshID automatically substitutes whatever you paste into Token, producing the header PagerDuty expects: Authorization: Token token=<your key>. The leading word "Token" is just part of PagerDuty's required format; leave it alone.

  6. Save to test the connection.

  7. Enable the actions you want YeshID to run against PagerDuty (see below), then wire them into your onboarding and offboarding workflows.

What each action does

Action

What it does

PagerDuty endpoint

Import Users

Reads existing PagerDuty users into YeshID so they can be matched to people and reviewed. Reads each user's name, email, and role.

GET /users

Create User

Creates a new PagerDuty user during onboarding, with the role admin if the YeshID account is marked admin, otherwise user.

POST /users

Delete User

Removes a PagerDuty user during offboarding.

DELETE /users/{id}

Import-only is a safe start. With a read-only key you can import PagerDuty users for visibility without turning on provisioning. Add a full-access key later when you're ready to create and delete.

How it connects to other features

  • Onboarding. When a new hire's onboarding runs, the Create User action can create their PagerDuty account so on-call access is ready on day one. Admins get the admin role; everyone else gets user.

  • Offboarding. When someone leaves, Delete User removes their PagerDuty account, closing off access without a manual cleanup step.

  • Access reviews. Because Import Users brings PagerDuty accounts into YeshID, PagerDuty appears in the same access picture as the rest of a person's apps — so "who has PagerDuty, and who's an admin?" is answerable in one place.

Good to know

  • Users only. YeshID imports and manages PagerDuty user accounts and their role. Teams, schedules, escalation policies, and on-call rotations aren't imported or changed — they stay in PagerDuty.

  • Admin is inferred from the PagerDuty role. On import, a PagerDuty user whose role is owner or admin is treated as an admin in YeshID.

  • Create makes the account directly. There's no separate "invite" step — Create User provisions the PagerDuty account outright.

  • No update or deactivate. PagerDuty supports Import, Create, and Delete in YeshID today — there's no separate update or suspend/deactivate action, so mid-life changes and offboarding are handled by delete rather than deactivation.