---
title: "Get a Ruleset"
method: GET
path: "/rulesets/{id}"
tags: ["Rulesets"]
---

# Get a Ruleset

`GET /rulesets/{id}`

Get a Ruleset.
<!-- 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.

Rulesets allow you to route events to an endpoint and create collections of Event Rules, which define sets of actions to take based on event content.

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

Scoped OAuth requires: `event_rules.read`

## Path parameters

- `id` string, required

## Headers

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

## Response `200`

The Ruleset object.

- object
  - `ruleset` Ruleset
    - `id` string — ID of the Ruleset.
    - `self` string, url — the API show URL at which the object is accessible
    - `type` 'global' | 'default_global'
    - `name` string — Name of the Ruleset.
    - `routing_keys` string[] — Routing keys routed to this Ruleset.
    - `created_at` string, date-time — The date the Ruleset was created at.
    - `creator` object — Reference to the user that has created the Ruleset.
      - `id` string
      - `type` string — A string that determines the schema of the object
      - `self` string, url — The API show URL at which the object is accessible
    - `updated_at` string, date-time — The date the Ruleset was last updated.
    - `updater` object — Reference to the user that has updated the Ruleset last.
      - `id` string
      - `type` string — A string that determines the schema of the object
      - `self` string, url — The API show URL at which the object is accessible
    - `team` object — Reference to the team that owns the Ruleset. If none is specified, only admins have access.
      - `id` string, required
      - `type` string, required — A string that determines the schema of the object
      - `self` string, url — The API show URL at which the object is accessible

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