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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
JPMorgan Chase

JPMorgan Chase Disputes Actions API

Operations for executing actions on disputes, such as challenging, accepting, and fulfilling requests.

Documentation Provider Profile APIs.io OpenAPI GitHub

JPMorgan Chase Disputes Actions 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-Actions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 3 paths, and defines 22 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.

3 operations 3 paths 22 schemas 3 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
Contact
Disputes API Support
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 3

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

Disputes Actions 3

Operations for executing actions on disputes, such as challenging, accepting, and fulfilling requests.

POST
/disputes/{disputeId}/challenge
Challenge a dispute
challengeDispute 4 params body → 200400401403404406422503
POST
/disputes/{disputeId}/fulfill
Fulfill a retrieval request dispute
fulfillDispute 4 params body → 200400401403404406422503
POST
/disputes/{disputeId}/accept
Accept a dispute
acceptDispute 4 params body → 200400401403404406422503

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are acceptDisputeResponse (6 properties), fulfillDisputeResponse (6 properties), challengeDisputeResponse (6 properties), messages (5 properties). Each schema is shown below with its type and property counts.

fulfillRequest
object
Contains request attributes required to fulfill retrieval-request dispute.
2 properties 2 required
requestId
string
Unique request identifier provided by the requestor.
messages
object
A list of errors and warnings
5 properties
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…
actionProcessingStatus
string
Codifies dispute action processing status code, in response of the case action requested by merchant. Possible values are, INPROGRESS: The request is being pro…
location
string
Location of the field for which the error occurred in the request
httpStatus
integer
The response code that is returned to the client based on how a backend service handled the request
last4CardNumber
string
Identifies the last 4 digits of card number. The truncated value is used in place of the full number to protect against exposure of confidential information.
field
string
The field for which the error has occured.
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.
disputeStatus
string
The label for the current stage of a case in the dispute resolution process
fulfillDisputeResponse
object
Fulfill action response
6 properties
contextMessage
object
Object containing information in the file
4 properties
acceptDisputeResponse
object
Accept dispute response.
6 properties
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…
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…
title
string
Short human readable title of the error
challengeDisputeResponse
object
Challenge action response
6 properties
acceptRequest
object
Contains request attributes required to accept a dispute.
1 property 1 required
supportingDocument
object
Contains supporting document information for the dispute action.
2 properties 2 required
disputeId
integer
A unique identifier assigned by the acquirer to track each inquiry or case created for a transaction dispute on an account.
challengeRequest
object
Contains request attributes required to challenge a dispute.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jp-morgan-chase-disputes-actions-api-openapi.yml Raw ↑

Other APIs JPMorgan Chase publishes across the network.

Notifications API
AE Profile APIs.io
Accounts API
AE Profile APIs.io
Recipients API
AE Profile APIs.io
Webhooks API
AE Profile APIs.io
Transactions API
AE Profile APIs.io
Documents API
AE Profile APIs.io
JPMorgan Chase Account Information API
AE Profile APIs.io
JPMorgan Chase Account Restrictions API
AE Profile APIs.io
JPMorgan Chase Account Services API
AE Profile APIs.io
JPMorgan Chase Account Statements API
AE Profile APIs.io
JPMorgan Chase Account Transactions API
AE Profile APIs.io
JPMorgan Chase Account Updates API
AE Profile APIs.io
#Disputes-Actions
← Back to J APIs
API Details
ID
jp-morgan-chase:jp-morgan-chase-disputes-actions-api
Base URL
https://api.payments.jpmorgan.com/onboarding/v1
Docs
https://developer.payments.jpmorgan.com/api
Provider
JPMorgan Chase
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=jp-morgan-chase-disputes-actions-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/jp-morgan-chase-disputes-actions-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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