---
title: "Provide supporting information for dispute"
method: POST
path: "/v1/customer/disputes/{id}/provide-supporting-info"
tags: ["disputes-actions"]
---

# Provide supporting information for dispute

`POST /v1/customer/disputes/{id}/provide-supporting-info`

Provides supporting information for a dispute, by ID. A merchant or buyer can make this request for disputes if they find the `provide-supporting-info` link in the HATEOAS links in the list disputes response. The party can provide the supporting information to PayPal to defend themselves only when the `dispute_life_cycle_stage` is `CHARGEBACK`, `PRE_ARBITRATION`, or `ARBITRATION`. They can provide a note that describes their part with details or upload any supporting documents to support their side. For constraints and rules regarding documents, see <a href="/docs/integration/direct/customer-disputes/integration-guide/#documents">documents</a>.<br/>To make this request, specify the dispute ID in the URI and specify the notes in the JSON request body. This method differs from the provide evidence method which supports only multipart request, where PayPal asks the concerned party for evidence.

## Path parameters

- `id` string, required

## Response `200`

A successful request returns the HTTP `200 OK` status code and a JSON response body that includes a link to the dispute.

- SubsequentAction — The subsequent action.
  - `links` LinkDescription[] — An array of request-related [HATEOAS links](/docs/api/reference/api-responses/#hateoas-links/).
    - `href` string, required — The complete target URL. To make the related call, combine the method with this [URI Template-formatted](https://tools.ietf.org/html/rfc6570) link. For pre-processing, include the `$`, `(`, and `)` characters. The `href` is the key HATEOAS component that links a completed call with a subsequent call.
    - `rel` string, required — The [link relation type](https://tools.ietf.org/html/rfc5988#section-4), which serves as an ID for a link that unambiguously describes the semantics of the link. See [Link Relations](https://www.iana.org/assignments/link-relations/link-relations.xhtml).
    - `method` 'GET' | 'POST' | 'PUT' | 'DELETE' | 'HEAD' | 'CONNECT' | 'OPTIONS' | 'PATCH' — The HTTP method required to make the related call.

## Other responses

- `400` — The request failed due to a validation error. The request returns the HTTP `400 Bad Request` status code.
- `404` — The request failed due to the dispute is not available. The request returns the HTTP `404 Not Found` status code.
- `422` — The requested action could not be completed. The request returns the HTTP `422 Unprocessable Entity` status code.
- `500` — An internal server error occurred. The request returns the HTTP `500 Internal Server Error` status code.
- `default` — The error response.

---

[API](https://skmtc.net/paypal/apis/payments.md) · [All operations](https://skmtc.net/paypal/apis/payments/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/paypal/payments/revisions/672aceee1190/schema)