---
title: "Delete an Event Rule from a Service"
method: DELETE
path: "/services/{id}/rules/{rule_id}"
tags: ["Services"]
---

# Delete an Event Rule from a Service

`DELETE /services/{id}/rules/{rule_id}`

Delete an Event Rule from a Service.
<!-- theme: warning -->
> ### End-of-life
> Rulesets and Event Rules will end-of-life soon. We highly recommend that you [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
- `rule_id` string, required

## Headers

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

## Response `204`

The Event Rule was deleted successfully.

## 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.
- `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)