# Enrich dispute representment

This method allows you to enrich dispute representment with additional content.

Endpoint: POST /dispute-representments/enrich
Version: 1.0.0
Security: merchant, signature

## Header parameters:

  - `merchant` (string, required)

  - `signature` (string, required)

## Request fields (application/json):

  - `dispute_type` (string, required)
    Type of represented dispute.
    Enum: "card"

  - `dispute_id` (string, required)
    Identifier of the represented dispute that corresponds to the orders chargebacks id in chargebacks.

  - `enrichment` (object, required)
    Additional enrichment content for dispute representment.

  - `enrichment.proof_of_communication` (array)
    Emails, chat logs, or support tickets showing cardholder interaction.

  - `enrichment.proof_of_communication.file_id` (string, required)
    Unique identifier of the enrichment content file.
Should be provided for the uploaded file one of extensions jpg, jpeg, png, pdf, csv, txt, docx. File size does not exceed 0.5 MB (524288 bytes).

  - `enrichment.proof_of_communication.annotation` (string)
    Annotation for the enrichment file.

  - `enrichment.application_logs` (array)
    System logs providing technical evidence of the transaction or user activity.

  - `enrichment.proof_of_delivery` (array)
    Shipping confirmations, tracking info, or signed delivery receipts.

  - `enrichment.invoice` (array)
    Invoice documents with itemized charges and billing details.

  - `enrichment.receipts` (array)
    Transaction receipts or payment confirmations.

  - `enrichment.other` (array)
    Additional supporting documents not covered by other categories.

  - `submit` (boolean)
    Submit the dispute representment after including provided enrichment content.
If set to false, the representment file with enrichment content will be created,
but not submitted immediately.

  - `dispute_id` (string, required)
    Identifier of the represented dispute that corresponds to the dispute_id parameter in PayPal disputes.

## Response 200 fields (application/json):

  - `error` (object, required)
    Error object.

  - `error.code` (string, required)
    Unauthorized access due to invalid credentials.
    Example: 1.01

  - `error.messages` (array, required)
    Array of error messages applied to the decline payment.

## Response 400 fields (application/json):

  - `error` (object, required)
    Error object.

  - `error.code` (string, required)
    Error code.
    Example: 2.01

  - `error.message` (string, required)
    Error message.
    Example: Validation error

## Response 404 fields (application/json):

  - `error` (object, required)
    Error object.

  - `error.code` (string)

## Response 422 fields (application/json):

  - `error` (object, required)
    Error object.

  - `error.code` (string)