---
title: "Send message about dispute to other party"
method: POST
path: "/v1/customer/disputes/{id}/send-message"
tags: ["disputes-actions"]
---

# Send message about dispute to other party

`POST /v1/customer/disputes/{id}/send-message`

## Request

- Base URL: `https://api-m.paypal.com`
- URL: `https://api-m.paypal.com/v1/customer/disputes/{id}/send-message`
- Auth: one of:
  - OAuth 2
    - Client credentials
    - Token URL: `/v1/oauth2/token` scopes: `https://uri.paypal.com/services/disputes/update-seller`
  - OAuth 2
    - Client credentials
    - Token URL: `/v1/oauth2/token` scopes: `https://uri.paypal.com/services/disputes/update-buyer`
- TypeScript: <https://skmtc.dev/paypal/apis/payments/docs/v1/customer/disputes/:id/send-message/post.ts> (a function with typed inputs; its response is checked against the schema)

Sends a message about a dispute, by ID, to the other party in the dispute. Merchants and customers can only send messages if the `dispute_life_cycle_stage` value is `INQUIRY`. For constraints and rules regarding documents that can be attached as part of the message, see <a href="/docs/integration/direct/customer-disputes/integration-guide/#documents">documents</a>. To send a message, use the <code>send-message</code> link in the <a href="/docs/api/reference/api-responses/#hateoas-links/">HATEOAS links</a> of the <a href="/docs/api/customer-disputes/v1/#disputes_get">show dispute details</a> response and specify the message in the JSON request body. In case the link is not present in the response you can't send a message on the dispute.

## Path parameters

- `id` string, required

## Request body `multipart/form-data`

- object
  - `message_document` string, binary: A file that contains any additional info about the message posted.

## 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.
- `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.dev/paypal/apis/payments.md) - [All operations](https://skmtc.dev/paypal/apis/payments/llms.txt) - [OpenAPI document](https://skmtc.dev/paypal/apis/payments/revisions/672aceee1190?raw)