Paypal Disputes

Name: Disputes API
Brand: Disputes
Availability: InStock

✓ Official Vendor SpecPaymentsBilling Subscriptionsoauth215 EndpointsREST

Install Jentic One Beta

Connect the Disputes to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Disputes, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Disputes API.

List disputes

Show dispute details

Partially update dispute

Provide evidence

GET STARTED

Start building with Disputes API

Explore with Jentic

View OpenAPI Document

For Agents

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

Use for: I need to disputes, I want to show dispute details, Search for partially update dispute, Find all provide evidence

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

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.

Use Cases

Patterns agents use Disputes API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

15 endpoints — occasionally, something goes wrong with a customer's order.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Disputes API through Jentic.

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.

Paypal Disputes

Connect the Disputes to your agent

Capabilities

Start building with Disputes API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs