---
title: "Convert a Service's Event Rules into Event Orchestration Rules"
method: POST
path: "/services/{id}/rules/convert"
tags: ["Services"]
---

# Convert a Service's Event Rules into Event Orchestration Rules

`POST /services/{id}/rules/convert`

Convert this Service's Event Rules into functionally equivalent Event Orchestration Rules.

Sending a request to this API endpoint has several effects:

1. Automatically creates Event Orchestration Rules for this Service that will behave identically as this Service's currently configured Event Rules.
2. Makes all existing Event Rules for this Service read-only. All future updates need to be made via the newly created Event Orchestration rules.

Sending a request to this API endpoint will **not** change how future events will be processed. If past events for this Service have been evaluated via Event Rules then new events sent to this Service will also continue to be evaluated via the (now read-only) Event Rules. To change this Service so that new events start being evaluated via the newly created Event Orchestration Rules use the [Update the Service Orchestration active status for a Service API](https://developer.pagerduty.com/api-reference/855659be83d9e-update-the-service-orchestration-active-status-for-a-service).

> ### End-of-life
> Event Rules will end-of-life soon. We highly recommend that you use this API to [migrate to Event Orchestration](https://support.pagerduty.com/docs/migrate-to-event-orchestration) as soon as possible so you can take advantage of the new functionality, such as improved UI, rule creation, APIs and Terraform support, advanced conditions, and rule nesting.

Scoped OAuth requires: `services.write`

## Path parameters

- `id` string, required

## Headers

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

## Response `200`

The Event Orchestration Rules were successfully created

- object
  - `convert_status` string — Did PagerDuty successfully create equivalent Event Orchestration rules
  - `converted_to` string, url — the API URL at which the newly created Event Orchestration rules are accessible

## Other responses

- `400` — Could not create equivalent Event Orchestration Rules based on the Service's current Event Rules
- `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.
- `405` — The request was received and recognized by the server, but its HTTP method was rejected for the requested resource.
- `409` — The request conflicts with the current state of the server.

---

[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)