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

JPMorgan Chase Disputes Data Retrieval API

Operations for fetching dispute-related data, such as list of disputes, details, status, and issuer documents

JPMorgan Chase Disputes Data Retrieval API is one of 65 APIs that JPMorgan Chase publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 4 operations across 4 paths, and defines 78 schemas. It is described by OpenAPI 3.2.0, at version 1.1.3.

Requests are made against 2 base URLs: https://api.payments.jpmorgan.com/commerce/v1, https://api-sandbox.payments.jpmorgan.com/commerce/v1.

4 operations 4 paths 78 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.1.3
Base URL
https://api.payments.jpmorgan.com/onboarding/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

JPMorgan Chase Disputes Data Retrieval API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 4

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

Disputes Data Retrieval 4

Operations for fetching dispute-related data, such as list of disputes, details, status, and issuer documents

POST
/disputes
Retrieve a list of disputes
fetchDisputes 2 params body → 200400401403503
GET
/disputes/{disputeId}
Get dispute details
getDisputeDetails 4 params → 200400401403404406503
POST
/disputes/status-query
Retrieve disputes status
fetchDisputeStatuses 2 params body → 200400401403503
GET
/disputes/{disputeId}/documents
Get dispute documents
getDisputeDocuments 4 params → 200400401403404406503

Schemas 78

The contract defines 78 schemas that model the data the API accepts and returns. The most detailed are disputeDetails (31 properties), disputeData (19 properties), disputesRequest (11 properties), authorizationDataDetailed (10 properties). Each schema is shown below with its type and property counts.

transactionAmount
number
Specifies the monetary value of the transaction performed.
merchantId
string
Identifies a unique entity for transaction processing at the lowest level of the account hierarchy of the backend proprietary merchant acquiring processing pla…
merchantIds
object
A list of unique processing entities or transaction division identifiers.
1 property
responseDueDate
string
Due date before which the merchant can challenge the dispute in YYYY-MM-DD format.
disputeStatuses
array
A list of dispute status filters to apply when querying disputes. Use the value 'ALL' to return disputes matching other filters, regardless of their status.
merchantData
object
Contains basic data of a merchant.
4 properties
transactionDataDetailed
object
Contains detailed information about sale or refund transaction.
2 properties
disputeCategoryCode
string
The category of the dispute based on the reason code.
disputeDetails
object
Includes details of a specific dispute.
31 properties
location
string
Location of the field for which the error occurred in the request
issuerDocumentReceived
boolean
Codifies a document is received by the payment network from the issuer for a disputed transaction. If this is set to true, an issuer document is received from…
caseTimelineEvent
object
Depicts a specific event within the chronological timeline of all events in a particular dispute case.
3 properties
disputeCurrencyCode
string
The currency code for the dispute amount, always in the merchant's settlement currency.
disputeStatus
string
The label for the current stage of a case in the dispute resolution process
disputeType
string
Codifies the category of an inquiry or disagreement related to a payment transaction on a consumer payment account.
disputesRequest
object
Specifies attributes used to query and retrieve a list of dispute cases
11 properties 1 required
authorizationReferenceNumber
string
Identifies a reference number generated at debit card transaction time.
outcome
string
The label given to the financial outcome of a chargeback dispute where money was taken back from the merchant for a sale and indicates if the case has been Won…
message
string
Provides textual description of a problem that has occurred and is preventing the system from completing a task. Messages can be a confirmation, warning or not…
disputesStatusResponse
object
Dispute Response
4 properties
disputeDocumentsResponse
object
Dispute document response
4 properties
disputeInitiatedDate
string
Designates the date the dispute case record was substantiated or established.
merchantName
string
The label given to a unique entity for transaction processing at the lowest level of the account hierarchy of the backend proprietary merchant acquiring proces…
pagination
object
This is used for specifying pagination related information.
1 property
issuerDocumentCode
integer
Codifies a document is required by the payment network from the issuer for a disputed transaction. If this is set to 1, expect an issuer document arrival in ne…
transactionCurrency
string
Codifies the monetary unit that was associated with the financial transaction (such as sale, refund)
disputeId
integer
A unique identifier assigned by the acquirer to track each inquiry or case created for a transaction dispute on an account.
disputeIds
object
List of unique case identifiers.
1 property
disputeTypes
array
A list of labels representing the categories or cycles of disputes. By default it returns all types of disputes.
documentData
object
Document data attached to a case.
3 properties
paymentMethod
object
Contains payment method code and description.
3 properties
statusUpdateEndDate
object
Dispute case status update date. This is to set end date-time of the range, in format YYYY-MM-DDTHH:MM:SSZ.
1 property
issuerDocumentExpected
boolean
Codifies a document is required by the payment network from the issuer for a disputed transaction. If this is set to true, expect an issuer document arrival in…
disputesStatusData
object
Dispute current status related information.
7 properties
requestId
string
Unique request identifier provided by the requestor.
relatedItemsData
object
Contains information about other related disputes items.
5 properties
disputesResponse
object
Disputes response object.
4 properties 3 required
authorizationData
object
Contains detailed information about transaction authorization.
2 properties
disputeReason
object
Contains reason code and description of a dispute.
2 properties
httpStatus
integer
The response code that is returned to the client based on how a backend service handled the request
authorizationTimestamp
string
Designates the year, month and day along with timestamp when an authorization for a transaction was received by transaction processing system. This may be diff…
disputeAmount
number
Specifies the monetary value of the total amount of a charge the customer is disputing on their account with the merchant.
code
string
Codifies a raised exception encountered by an internal or external system, sub-system, interface, job, module, system component with which the web service appl…
companyId
string
Identifies a unique entity which represents a relationship at the highest of the three levels of the account hierarchy of the backend proprietary merchant acqu…
disputeReasonCode
string
Codifies the reason for the disputed case.
title
string
Short human readable title of the error
merchantOrderNumber
string
A unique identifier assigned by the merchant or on behalf of the merchant for the intention to purchase goods and/or services. The merchant order provides the…
submitterPlatformId
string
Identifies the platform used to facilitate the request of the transaction that is being disputed.
companyName
string
The label given to a unique entity which represents a relationship at the highest of the three levels of the account hierarchy of the back-end proprietary merc…
disputesStatusFilter
string
Represents the possible status values used to filter disputes in a query. Includes all valid dispute statuses, as well as the special value 'ALL' to indicate t…
statusInquiryParameters
object
Status enquiry parameters
messages
object
A list of errors and warnings
5 properties
transactionTypeCode
string
Codifies whether a transaction type will be grouped as a debit, credit or non monetary. C value indicates Credit and D indicates Debit.
disputeData
object
Dispute information
19 properties 11 required
relatedItems
array
Includes details about items related to disputes.
disputeValue
object
Contains dispute amount and currency.
2 properties
paymentMethodList
array
A list of payment method codes to filter disputes by card brand or payment type.
merchantDataDetailed
object
Contains detailed information about merchant.
4 properties
authorizationCurrency
string
Codifies the monetary unit that was associated with the financial transaction (such as sale, refund)
companyIds
object
A list of unique company identifiers. Reserved for future use. Currently not active.
1 property
field
string
The field for which the error has occured.
contextMessage
object
Object containing information in the file
4 properties
entityIds
object
Entity identifiers for a Merchant Organization, determined by the hierarchical structure within the system.
acquirerReferenceNumber
string
Identifies a unique number assigned by the payment brand to a credit card transaction for use when it goes from the Firm acting as the acquiring bank through t…
traceId
string
A number assigned by a transaction originator to assist in identifying a transaction uniquely. The systems trace audit number remains unchanged for all message…
paymentMethodCode
string
Codifies the method used to pay for the exchange of money, goods or services between a merchant and their customer. Examples: VI for Visa, MC for MasterCard et…
statusUpdateStartDate
object
Dispute case status update date. This is to set start date-time of the range, in format YYYY-MM-DDTHH:MM:SSZ.
1 property
relatedFinancialItemsData
object
Dispute related financial items.
2 properties
statusUpdateTimestamp
string
Represents the date and time when the status of a dispute case was last updated in UTC timezone. The format is YYYY-MM-DDTHH:MM:SSZ.
transactionData
object
Contains basic data of an original sale or refund transaction.
6 properties
disputesStatusRequest
object
Retrieve dispute status request.
2 properties 1 required
transactionId
string
The transaction identifier of the original transaction.
authorizationDataDetailed
object
Contains detailed information about transaction authorization.
10 properties
paymentMethodName
string
English label for the method used to pay for the exchange of money, goods or services between a merchant and their customer. Examples: Visa, MasterCard, PayPal…
maskedAccountNumber
string
The Card Number is a number recognized by various payment systems to route debit card, ATM and credit Card transactions to an issuer and to identify the underl…
disputeReasonDescription
string
Textual reason description of the disputed case.
transactionTimestamp
string
Designates the date and time in UTC timezone, on which the original sale or refund transaction was performed. The format is YYYY-MM-DDTHH:MM:SSZ.
disputeDetailsResponse
object
Dispute details response
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jp-morgan-chase-disputes-data-retrieval-api-openapi.yml Raw ↑

Other APIs JPMorgan Chase publishes across the network.

Notifications API
Accounts API
Recipients API
Webhooks API
Transactions API
Documents API
JPMorgan Chase Account Information API
JPMorgan Chase Account Restrictions API
JPMorgan Chase Account Services API
JPMorgan Chase Account Statements API
JPMorgan Chase Account Transactions API
JPMorgan Chase Account Updates API
Where this information came from

This is an independent, third-party profile of JPMorgan Chase Disputes Data Retrieval 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.