---
title: "Delete an Event Enrichment"
method: DELETE
path: "/enrichment/event_enrichments/{id}"
tags: ["Event Enrichments"]
---

# Delete an Event Enrichment

`DELETE /enrichment/event_enrichments/{id}`

Event Enrichments allow you to automatically add contextual data to events as they're ingested, so that relevant information is available throughout the event, alert, and incident lifecycle. By leveraging the Contextual Data Platform (CDP), you can define rules that extract values from events or query enrichment schemas to populate event fields.

<!-- theme: warning -->

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

Delete a specific Event Enrichment. The user must have "Delete" privileges for both the Event Enrichment and all of its associated items.

## Path parameters

- `id` string, required

## Headers

- `Accept` string, required

## Response `204`

The Event Enrichment was deleted successfully.

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