---
title: "Add Event Enrichment associations"
method: POST
path: "/enrichment/event_enrichments/{id}/associations"
tags: ["Event Enrichments"]
---

# Add Event Enrichment associations

`POST /enrichment/event_enrichments/{id}/associations`

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.

Associating an Event Orchestration or Service with an Event Enrichment allows for the enrichment to be evaluated when events are ingested for that Event Orchestration or Service

<!-- theme: warning -->

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

Add new associations between an Event Enrichment and Services or Event Orchestrations.

## Path parameters

- `id` string, required

## Headers

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

## Request body

- object
  - `associations` EventEnrichmentAssociation[], required
    - `type` 'service_reference' | 'event_orchestration_reference' — The type of the associated resource.
    - `id` string — The ID of the associated Service or Event Orchestration.
    - `summary` string — The name of the associated Service or Event Orchestration.
    - `self` string, url — The API show URL at which the associated resource is accessible.

## Response `201`

Associations created successfully, or a multi-status response if some failed.

- object
  - `status` 'created'

## Other responses

- `207` — Multi-status response indicating partial success when adding or deleting associations.
- `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)