---
title: "List enrichment schemas"
method: GET
path: "/enrichment/schemas"
tags: ["Enrichment Schemas"]
---

# List enrichment schemas

`GET /enrichment/schemas`

Lists all enrichment schemas for the account.

<!-- theme: warning -->

> ### Early Access
> This API is in Early Access and may change at any time. Contact your PagerDuty account team to request access.

Scoped OAuth requires: `contextual_data.read`

## Headers

- `Accept` string, required

## Response `200`

The list of enrichment schemas for the account.

- object
  - `schemas` EnrichmentSchema[] — The list of enrichment schemas.
    - `id` string, uuid — Unique identifier for the enrichment schema.
    - `type` string — The type of the resource.
    - `integration_type` 'CSV' | 'SERVICENOW' — The source of the enrichment schema. `CSV` schemas are created and populated through the schema and CSV-upload endpoints; `SERVICENOW` schemas are managed by the ServiceNow CMDB integration. Schemas created through the API are always `CSV`, and only `CSV` schemas can be deleted.
    - `name` string — Display name of the enrichment schema.
    - `description` string, nullable — Description of this set of enrichment data.
    - `fields` EnrichmentField[] — The fields that make up the schema, including both query and enriched fields. A schema must contain 1-3 `query` fields and at least one `enriched` field, up to a maximum of 25 fields. Field names are unique within the schema (case-insensitive).
      - `name` string, required — The name of the field. Unique within the schema (case-insensitive).
      - `type` 'query' | 'enriched' | 'discriminator', required — How the field is used during enrichment. `query` fields are used to match incoming events to enrichment records (matching is case-insensitive), and `enriched` fields carry the contextual data added to a matched event. A schema has 1-3 query fields and at least one enriched field. `discriminator` is reserved for internal use (for example, by the ServiceNow CMDB integration).
    - `created_at` string, date-time — Timestamp when the schema was created.
    - `updated_at` string, date-time — Timestamp when the schema was last updated.
    - `deleted_at` string, date-time, nullable — Timestamp when the schema was deleted, or `null` if it has not been deleted.

## Other responses

- `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.
- `429` — Too many requests have been made, the rate limit has been reached.
- `500` — Internal Server Error the PagerDuty server experienced an error.

---

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