---
title: "Mark an Event Enrichment as the account default"
method: PUT
path: "/enrichment/event_enrichments/default"
tags: ["Event Enrichments"]
---

# Mark an Event Enrichment as the account default

`PUT /enrichment/event_enrichments/default`

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.

The default Event Enrichment gets applied to every Event Orchestration or Service that is not already associated to any other Event Enrichment

<!-- theme: warning -->

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

Mark a specific Event Enrichment as the account default. Set the request body to `default: null` to clear the current default.

## Headers

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

## Request body

- object
  - `default` EventEnrichmentReference — A reference to an Event Enrichment object.
    - `id` string — The ID of the Event Enrichment.
    - `type` 'event_enrichment_reference' — A string that determines the schema of the object.
    - `summary` string — A short-form, server-generated string that provides succinct, important information about an object suitable for primary labeling of an entity in a client. In many cases, this will be identical to `name`, though it is not intended to be an identifier.
    - `self` string, url — The API show URL at which the object is accessible.

## Response `200`

The updated account default Event Enrichment.

- EventEnrichmentDefault — The account default Event Enrichment, along with the previous default if one was replaced.
  - `default` EventEnrichmentReference — A reference to an Event Enrichment object.
    - `id` string — The ID of the Event Enrichment.
    - `type` 'event_enrichment_reference' — A string that determines the schema of the object.
    - `summary` string — A short-form, server-generated string that provides succinct, important information about an object suitable for primary labeling of an entity in a client. In many cases, this will be identical to `name`, though it is not intended to be an identifier.
    - `self` string, url — The API show URL at which the object is accessible.
  - `previous_default` EventEnrichmentReference — A reference to an Event Enrichment object.
    - `id` string — The ID of the Event Enrichment.
    - `type` 'event_enrichment_reference' — A string that determines the schema of the object.
    - `summary` string — A short-form, server-generated string that provides succinct, important information about an object suitable for primary labeling of an entity in a client. In many cases, this will be identical to `name`, though it is not intended to be an identifier.
    - `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.
- `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/versions/b679a8f3f02c/schema)