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

Cash App Disputes API

The disputes API from Cash App — 8 operation(s) for disputes.

Cash App Disputes API is one of 19 APIs that Cash App 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 an OpenAPI specification, API documentation, and an API reference.

This API exposes 9 operations across 8 paths, and defines 30 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.cash.app/network/v1, https://sandbox.api.cash.app/network/v1.

9 operations 8 paths 30 schemas 1 DELETE4 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.cash.app/network/v1
Resource Areas
1

Paths & Operations 9

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

disputes 9
GET
/disputes
List disputes
list-disputes 7 params → 200400
GET
/disputes/{dispute_id}
Retrieve dispute
retrieve-dispute 5 params → 200404
POST
/disputes/{dispute_id}/accept
Accept dispute
accept-dispute 5 params → 200400404
POST
/disputes/{dispute_id}/challenge
Challenge dispute
challenge-dispute 5 params → 200400404
GET
/disputes/{dispute_id}/evidence
List dispute evidence
list-dispute-evidence 7 params → 200400
POST
/disputes/{dispute_id}/evidence-text
Create dispute evidence text
create-dispute-evidence-text 5 params body → 201400404
POST
/disputes/{dispute_id}/evidence-file
Create dispute evidence file
create-dispute-evidence-file 5 params body → 201400404
DELETE
/disputes/{dispute_id}/evidence/{evidence_id}
Delete dispute evidence
delete-dispute-evidence 6 params → 200404
GET
/disputes/{dispute_id}/evidence/{evidence_id}
Retrieve dispute evidence
retrieve-dispute-evidence 6 params → 200404

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are Dispute (11 properties), DisputeEvidence (8 properties), Error (4 properties), DisputesDisputeIdEvidenceTextPostRequestBodyContentApplicationJsonSchemaEvidence (3 properties). Each schema is shown below with its type and property counts.

DisputeEvidenceFileContentType
string
The MIME type of the uploaded file. Current values: - application/pdf - image/heic - image/heif - image/jpeg - image/png - image/tiff
DisputesDisputeIdEvidenceTextPostRequestBodyContentApplicationJsonSchemaEvidence
object
Details about the evidence to create.
3 properties 2 required
DisputeSettlementWithholding
string
Indicates if the disputed amount has already been withheld from a settlement or not. Current values: - NOTWITHHELD: The disputed amount has not yet been withhe…
Disputes_retrieve-dispute_Response_200
object
1 property 1 required
Disputes_create-dispute-evidence-text_Response_201
object
1 property
DisputeEvidenceType
string
Indicates if the evidence is a file or plain text. Current values: - TEXT: The evidence is a blob of text under 500 characters. - FILE: The evidence is an uplo…
DisputesDisputeIdEvidenceFilePostRequestBodyContentMultipartFormDataSchemaRequest
object
JSON-encoded payload describing the contents of the file uploaded
2 properties
DisputesDisputeIdEvidenceTextPostRequestBodyContentApplicationJsonSchemaEvidenceCategory
string
Describes what type of information is contained in this piece of evidence. Current values: - GENERICEVIDENCE: Default evidence type used if no other category a…
Error
object
Represents an error encountered during a request to the API.
4 properties 2 required
DisputeEvidenceCategory
string
Describes what type of information is contained in this piece of evidence. Current values: - GENERICEVIDENCE: Default evidence type used if no other category a…
Disputes_challenge-dispute_Response_200
object
1 property 1 required
ErrorCategory
string
The high-level reason the error occurred.
IdempotencyKey
string
A unique identifier which can be used by Cash App to de-duplicate retries of this request, making it idempotent. For more information, see [Idempotency](/cash-…
Disputes_list-dispute-evidence_Response_200
object
2 properties 1 required
ErrorResponse
object
1 property 1 required
DisputesDisputeIdEvidenceFilePostRequestBodyContentMultipartFormDataSchemaRequestEvidenceCategory
string
Describes what type of information is contained in this piece of evidence. Current values: - GENERICEVIDENCE: Default evidence type used if no other category a…
Dispute
object
Represents a dispute initiated by a customer within Cash App or the customer's linked bank
11 properties 9 required
Metadata
object
Freeform key-value pairs of arbitrary data associated with this resource. Keys and values must be passed as strings and not contain any personally identifiable…
DisputeEvidence
object
8 properties 5 required
DisputesDisputeIdEvidenceFilePostRequestBodyContentMultipartFormDataSchemaRequestEvidence
object
Details about the evidence to create.
3 properties 2 required
DisputesDisputeIdEvidenceFilePostRequestBodyContentMultipartFormDataSchemaRequestEvidenceFile
object
Metadata about the uploaded file.
2 properties 2 required
Disputes_create-dispute-evidence-file_Response_201
object
1 property 1 required
DisputesDisputeIdEvidenceFilePostRequestBodyContentMultipartFormDataSchemaRequestEvidenceFileContentType
string
The MIME type of the uploaded file. Current values: - application/pdf - image/heic - image/heif - image/jpeg - image/png - image/tiff
Disputes_list-disputes_Response_200
object
2 properties 1 required
DisputeState
string
The step in the dispute lifecycle that this dispute is currently at: - RESPONSEREQUIRED - NORESPONSEREQUIRED - PROCESSING - ACCEPTED - WON - PARTIALLYWON - LOST
Disputes_delete-dispute-evidence_Response_200
object
Empty response body
DisputeEvidenceFile
object
If the evidence is of type FILE, contains metadata about the binary file uploaded as evidence.
2 properties 2 required
Disputes_accept-dispute_Response_200
object
1 property
DisputeReason
string
4-digit code consisting of 2 letters followed by 2 numbers that indicates why the dispute was created, at a high level. Current values: - FR10: Customer has no…
Disputes_retrieve-dispute-evidence_Response_200
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cash-app-disputes-api-openapi.yml Raw ↑

Other APIs Cash App publishes across the network.

Cash App Add Cash App Pay To Your Site API
Cash App API Keys API
Cash App Balances API
Cash App Billing Agreements (Deprecated) API
Cash App Brands API
Cash App Customer Request API
Cash App Customers API
Cash App App Default API
Cash App Fee Plans API
Cash App Grants Afterpay API
Cash App Merchants API
Cash App Network API
Where this information came from

This is an independent, third-party profile of Cash App 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.