canonical: https://jentic.com/apis/paypal.com/disputes

# Paypal Disputes

Occasionally, something goes wrong with a customer's order. To dispute a charge, a customer can create a dispute with PayPal. PayPal merchants, partners, and external developers can use the PayPal Disputes API to manage customer disputes.<blockquote><strong>Note:</strong> In the live environment, merchants cannot create disputes but can only respond to customer-created disputes. However, merchants. The API exposes 15 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically list disputes, show dispute details. Covers 15 operations with oauth2 authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- List disputes
- Show dispute details
- Partially update dispute
- Provide evidence
- Appeal dispute
- Accept claim
- Settle dispute

## Use cases

### Payments Operations

Use the Disputes to perform payments operations programmatically. The API provides 15 endpoints covering core functionality including list disputes, show dispute details, partially update dispute.

Example prompt: Call GET /v1/customer/disputes to list disputes

### Automated disputes Management

Automate disputes operations by combining multiple Disputes endpoints. Agents can show dispute details and then partially update dispute in a single workflow.

Example prompt: Call GET /v1/customer/disputes/{id} to show dispute details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Disputes endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'list disputes', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/customer/disputes | List disputes |
| GET | /v1/customer/disputes/{id} | Show dispute details |
| PATCH | /v1/customer/disputes/{id} | Partially update dispute |
| POST | /v1/customer/disputes/{id}/provide-evidence | Provide evidence |
| POST | /v1/customer/disputes/{id}/appeal | Appeal dispute |
| POST | /v1/customer/disputes/{id}/accept-claim | Accept claim |
| POST | /v1/customer/disputes/{id}/adjudicate | Settle dispute |
| POST | /v1/customer/disputes/{id}/require-evidence | Update dispute status |

## Key resources

- **disputes** — Use the `/disputes` resource to list disputes, create disputes, show dispute details, and partially
- **disputes-actions** — Use the `/disputes` resource with a dispute ID and an action to:<ul><li>Accept a claim.</li><li>Acce
- **referred-disputes** — Use the `/customer/referred-disputes` resource to create a dispute for a referred case that was crea
- **validate-eligibility** — Use the `/validate-eligibility/` resource to determine whether you can create a case for a transacti
- **compute-metrics** — Use the `/compute-metrics` resource to provide metrics for all disputes.

## Why Jentic

- **Setup:** Wiring PayPal Disputes by hand means running its OAuth 2.0 flow, refreshing Bearer tokens, and choosing the right sandbox or live host before you can list disputes or provide evidence. Through Jentic you install once, import Disputes from the API Directory, store the client credentials once, and your agent calls it.
- **Permission scoping:** Disputes puts the dispute id in the URL path (/v1/customer/disputes/{id}), so a rule can pin your agent to reading one dispute. You choose the operations it may call, so accepting a claim, adjudicating, or appealing is not included unless you add them.
- **Credential handling:** Your PayPal OAuth client id and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time, with token refresh handled for you. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list disputes' or 'provide evidence for a dispute', and Jentic returns the matching Disputes operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API

## FAQ

### What authentication does the Disputes use?

The Disputes uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list disputes with the Disputes?

Yes. Use the GET /v1/customer/disputes endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Disputes?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list disputes through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list disputes'. Jentic returns the matching Disputes operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Disputes have?

The Disputes exposes 15 endpoints covering disputes, disputes-actions, referred-disputes operations.

### Can I limit what my agent is allowed to do with the PayPal Disputes API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Disputes operations and credentials the agent may use. Because the dispute id sits in the URL path (/v1/customer/disputes/{id}), you can pin the agent to reading a single dispute, or allow only read operations like listing disputes and showing dispute details. Higher-impact actions such as accepting a claim, adjudicating, or appealing are not included unless you explicitly add them.