---
title: "Add an attachment to a dispute"
method: POST
path: "/disputes/{disputeId}/attachments"
tags: ["Dispute Attachments"]
---

# Add an attachment to a dispute

`POST /disputes/{disputeId}/attachments`

Add supporting information as an attachment for the raised dispute. Upload receipts, communication, or any other documentation to support the dispute.

## Path parameters

- `disputeId` string, required

## Request body

- DisputeAttachment
  - `attachmentType` 'receipt' | 'correspondence' | 'other', required
  - `content` string, required — The content of the image. An attachment must be base64-encoded data. Make sure that all base64-encoded data strings are generated without line breaks or "wrapping". For example, do not use `Base64.NO_WRAP` in Java, or its equivalent in other languages. Newline characters at the end of the base64-encoded data string will also result in a malformed input error.
  - `fileName` string, required — The name of the attachment, including its filename extension. Supported filename extensions: **jpeg**, **pdf**, **tiff**.
  - `id` string — The unique identifier of the attachment.

## Response `200`

OK - the request has succeeded.

- AttachDocumentResponse
  - `attachmentId` string — The unique identifier of the attachment.

## Other responses

- `401` — Authentication required.
- `403` — Insufficient permissions to process the request.
- `422` — A request validation error.

---

[API](https://skmtc.net/adyen/apis/transactionservice.md) · [All operations](https://skmtc.net/adyen/apis/transactionservice/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/adyen/transactionservice/versions/7b225d65ac3a/schema)