---
title: "Resolve PagerDuty service"
method: GET
path: "/v1/integrations/pagerduty/services/{pagerduty_service_id}/"
tags: ["Integrations"]
---

# Resolve PagerDuty service

`GET /v1/integrations/pagerduty/services/{pagerduty_service_id}/`

## Request

- Base URL: `https://logfire-api.pydantic.dev/api`
- URL: `https://logfire-api.pydantic.dev/api/v1/integrations/pagerduty/services/{pagerduty_service_id}/`
- Auth: OAuth 2
  - Authorization code: `api/oauth/authorize`
  - Token URL: `/api/oauth/token` scopes: `organization:read_channel`
- TypeScript: <https://skmtc.dev/pydantic/apis/pydantic-logfire-api/docs/v1/integrations/pagerduty/services/:pagerduty_service_id/get.ts> (a function with typed inputs; its response is checked against the schema)

Resolve the Logfire IDs for a service approved through a PagerDuty connection.

Use PagerDuty's account subdomain and service ID as stable inputs. The returned
`install_id` and `service_id` are the values required by a
`pagerduty-integration` notification channel.

## Path parameters

- `pagerduty_service_id` string, required

## Query parameters

- `account_subdomain` string, required
- `region` 'us' | 'eu'

## Response `200`

Successful Response

- PagerDutyServiceView
  - `install_id` string, uuid, required
  - `service_id` string, uuid, required
  - `pagerduty_service_id` string, required
  - `service_name` string, required

## Other responses

- `404`: PagerDuty service not found
- `422`: Validation Error
- `429`: Rate limit exceeded

---

[API](https://skmtc.dev/pydantic/apis/pydantic-logfire-api.md) - [All operations](https://skmtc.dev/pydantic/apis/pydantic-logfire-api/llms.txt) - [OpenAPI document](https://skmtc.dev/pydantic/apis/pydantic-logfire-api/revisions/7996e45256f4?raw)