---
title: "Get an Integration for an Event Orchestration"
method: GET
path: "/event_orchestrations/{id}/integrations/{integration_id}"
tags: ["Event Orchestrations"]
---

# Get an Integration for an Event Orchestration

`GET /event_orchestrations/{id}/integrations/{integration_id}`

Get an Integration associated with this Event Orchestrations.

You can use the Routing Key from this Integration to send events to PagerDuty!

For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations)

Scoped OAuth requires: `event_orchestrations.read`

## Path parameters

- `id` string, required
- `integration_id` string, required

## Headers

- `Accept` string, required
- `Content-Type` 'application/json', required

## Response `200`

An Integration for this Event Orchestration.

- object
  - `integration` OrchestrationIntegration
    - `id` string — ID of the Integration.
    - `label` string — Name of the Integration.
    - `parameters` object
      - `routing_key` string — Routing Key used to send Events to this Orchestration
      - `type` string

## Other responses

- `400` — Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work.
- `401` — Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed.
- `403` — Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.
- `405` — The request was received and recognized by the server, but its HTTP method was rejected for the requested resource.

---

[API](https://skmtc.net/pagerduty/apis/rest-api.md) · [All operations](https://skmtc.net/pagerduty/apis/rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pagerduty/rest-api/versions/b679a8f3f02c/schema)