Disputes

Name: Disputes API
Brand: Disputes
Availability: InStock

✓ Official Vendor SpecPaymentsBilling Subscriptionsoauth215 EndpointsREST

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

Quickstart

Get started with Disputes in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list disputes"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Disputes API.

List disputes

Show dispute details

Partially update dispute

Provide evidence

Appeal dispute

GET STARTED

Start building with Disputes API

Explore with Jentic

View OpenAPI Document

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 though Jentic?

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

Credential isolation

Disputes oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'list disputes') and Jentic returns the matching Disputes operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Disputes integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe

Alternative payments API

Choose Stripe when you need a different approach to payments operations

Alternative

Adyen

Alternative payments API

Choose Adyen when you need a different approach to payments operations

Complementary

Square

Complementary payments API

Choose Square when you need a complementary approach to payments operations

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.