> ## Documentation Index
> Fetch the complete documentation index at: https://docs.peakmetrics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete a custom enrichment

> Retires a custom enrichment for your team. It disappears from
`GET /customEnrichments`, from your workspaces, and from filters;
`PUT /mentions/customEnrichments` rejects its `enrichment_id`. This is
whole-enrichment retirement, distinct from removing individual options with
`PUT /customEnrichments/{enrichmentId}`, and applies to every type.

Values already written to mentions are not removed from the mention documents.




## OpenAPI

````yaml /api/api_docs.yaml delete /customEnrichments/{enrichmentId}
openapi: 3.1.0
info:
  title: PeakMetrics API
  description: >
    The PeakMetrics API provides programmatic access to narrative intelligence
    data.


    Access millions of mentions across news, social media, and online platforms,
    enriched with custom AI-powered

    smart categories and over 50 metadata properties. The API enables you to

    identify, analyze, and act on emerging narratives in real-time.
  version: 2.0.0
servers:
  - url: https://api.peakmetrics.com
    description: Main (production) server
security:
  - BearerAuth: []
tags:
  - name: Authorization
  - name: Workspaces
  - name: Folders
  - name: Channels
  - name: Custom Channels
  - name: Custom Enrichments
    description: >
      Custom enrichments let you push external context about mentions into
      PeakMetrics,

      attached to individual mentions and used alongside all other mention
      metadata across

      the platform. Once written, enrichment values feed into narrative
      analysis, workspace

      summaries, and notifications, and are available through the customer API
      and the MCP

      server.


      Your team manages its own custom enrichments through the API: create one
      with

      `POST /customEnrichments`, list them with `GET /customEnrichments`, rename
      one or

      replace its option list with `PUT /customEnrichments/{enrichmentId}`,
      retire one with

      `DELETE /customEnrichments/{enrichmentId}`, and push values for individual
      mentions

      with `PUT /mentions/customEnrichments`.
paths:
  /customEnrichments/{enrichmentId}:
    delete:
      tags:
        - Custom Enrichments
      summary: Delete a custom enrichment
      description: >
        Retires a custom enrichment for your team. It disappears from

        `GET /customEnrichments`, from your workspaces, and from filters;

        `PUT /mentions/customEnrichments` rejects its `enrichment_id`. This is

        whole-enrichment retirement, distinct from removing individual options
        with

        `PUT /customEnrichments/{enrichmentId}`, and applies to every type.


        Values already written to mentions are not removed from the mention
        documents.
      parameters:
        - in: path
          name: enrichmentId
          required: true
          schema:
            type: integer
          description: The `enrichment_id` from `GET /customEnrichments`.
          example: 1681
      responses:
        '204':
          description: The custom enrichment is retired. Empty body.
        '401':
          description: Missing or invalid access token.
        '404':
          description: |
            Your team has no custom enrichment with this `enrichment_id`.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CustomEnrichmentError'
              examples:
                not_found:
                  summary: No such custom enrichment
                  value:
                    error: Custom enrichment not found
      security:
        - BearerAuth: []
components:
  schemas:
    CustomEnrichmentError:
      type: object
      properties:
        error:
          type: string
          description: A human-readable description of what was rejected.
          example: '''constraints.enum'' contains a duplicate value: ''Mixed'''
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````