---
title: "Get the Service Orchestration for a Service"
method: GET
path: "/event_orchestrations/services/{service_id}"
tags: ["Event Orchestrations"]
---

# Get the Service Orchestration for a Service

`GET /event_orchestrations/services/{service_id}`

Get a Service Orchestration.

A Service Orchestration allows you to create a set of Event Rules. The Service Orchestration evaluates Events sent to this Service against each of its rules, beginning with the rules in the "start" set. When a matching rule is found, it can modify and enhance the event and can route the event to another set of rules within this Service Orchestration for further processing.

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

Scoped OAuth requires: `services.read`

## Path parameters

- `service_id` string, required

## Query parameters

- `include[]` 'migrated_metadata'

## Headers

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

## Response `200`

The Service Orchestration object.

- ServiceOrchestration — unresolved $ref

## 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.
- `404` — The requested resource was not found.

---

[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/revisions/b679a8f3f02c/schema)