How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Stripe Disputes API

A dispute occurs when a customer questions your charge with their card issuer. When this happens, you have the opportunity to respond to the dispute with evidence that shows that the charge is legitimate.

Stripe Disputes API is one of 159 APIs that Stripe publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Disputes. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 8 operations across 5 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 2023-10-16.

Requests are made against a single base URL, https://api.stripe.com/.

8 operations 5 paths 18 schemas 4 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2023-10-16
Server
https://api.stripe.com/
Authentication
HTTP Basic, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

Stripe Disputes API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (auth-scheme) (bearerAuth). By default, every request must be authenticated.

  • basicAuth — Basic HTTP authentication. Allowed headers-- Authorization: Basic | Authorization: Basic
  • bearerAuth — Bearer HTTP authentication. Allowed headers-- Authorization: Bearer

Paths & Operations 8

Across 5 paths, the API surfaces 8 operations — 4 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Disputes 8
GET
/v1/disputes
Returns a list of your disputes.
GetDisputes 7 params body → 200default
GET
/v1/disputes/{dispute}
Retrieves the dispute with the given ID.
GetDisputesDispute 2 params body → 200default
POST
/v1/disputes/{dispute}
When you get a dispute, contacting your customer is always the best first step. If that doesn’t work, you can submit evidence to help us resolve the dispute in your favor. You can do this in your das…
PostDisputesDispute 1 param body → 200default
POST
/v1/disputes/{dispute}/close
Closing the dispute for a charge indicates that you do not have any evidence to submit and are essentially dismissing the dispute, acknowledging it as lost. The status of the dispute will change from…
PostDisputesDisputeClose 1 param body → 200default
GET
/v1/issuing/disputes
Stripe Get Issuing Disputes
getIssuingDisputes 7 params body → 200default
POST
/v1/issuing/disputes
Stripe Post Issuing Disputes
postIssuingDisputes body → 200default
GET
/v1/issuing/disputes/{dispute}
Stripe Get Issuing Disputes
getIssuingDisputesDispute 2 params body → 200default
POST
/v1/issuing/disputes/{dispute}
Stripe Post Issuing Disputes
postIssuingDisputesDispute 1 param body → 200default

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are issuing.authorization (25 properties), issuing.card (23 properties), issuing.transaction (22 properties), issuing.cardholder (16 properties). Each schema is shown below with its type and property counts.

issuing.token
object
An issuing token object is created when an issued card is added to a digital wallet. As a [card issuer](https://stripe.com/docs/issuing), you can [view and man…
12 properties 8 required
GetIssuingDisputesDisputeRequest
object
GetIssuingDisputesRequest
object
DisputeList
object
4 properties 4 required
PostIssuingDisputesDisputeRequest
object
4 properties
IssuingDisputeList
object
4 properties 4 required
issuing.transaction
object
Any use of an [issued card](https://stripe.com/docs/issuing) that results in funds entering or leaving your Stripe account, such as a completed purchase or ref…
22 properties 12 required
issuing.cardholder
object
An Issuing Cardholder object represents an individual or business entity who is [issued](https://stripe.com/docs/issuing) cards. Related guide: [How to create…
16 properties 10 required
error
object
An error response from the Stripe API
1 property 1 required
issuing.dispute
object
As a [card issuer](https://stripe.com/docs/issuing), you can dispute transactions that the cardholder does not recognize, suspects to be fraudulent, or has oth…
12 properties 10 required
dispute
object
A dispute occurs when a customer questions your charge with their card issuer. When this happens, you have the opportunity to respond to the dispute with evide…
16 properties 14 required
PostDisputesDisputeRequest
object
4 properties
issuing.authorization
object
When an [issued card](https://stripe.com/docs/issuing) is used to make a purchase, an Issuing Authorization object is created. [Authorizations](https://stripe.…
25 properties 18 required
issuing.card
object
You can [create physical or virtual cards](https://stripe.com/docs/issuing/cards) that are issued to cardholders.
23 properties 14 required
GetDisputesDisputeRequest
object
PostDisputesDisputeCloseRequest
object
1 property
GetDisputesRequest
object
PostIssuingDisputesRequest
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stripe-disputes-api-openapi.yml Raw ↑

Other APIs Stripe publishes across the network.

Stripe Accounts API
Stripe Balance API
Stripe Billing API
Stripe Charges API
Stripe Checkout API
Stripe Climate API
Stripe Country API
Stripe Coupons API
Stripe Credit Notes API
Stripe Customers API
Stripe Ephemeral Keys API
Stripe Events API
Where this information came from

This is an independent, third-party profile of Stripe Disputes API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.