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

Finix Disputes API

{'$ref': 'api-descriptions/tags/disputes.md'}

Finix Disputes API is one of 19 APIs that Finix 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, an API reference, a getting-started guide, and authentication docs.

This API exposes 11 operations across 8 paths, and defines 35 schemas. It is described by OpenAPI 3.0.2, at version 2022-02-01.

Requests are made against a single base URL, https://finix.sandbox-payments-api.com.

11 operations 8 paths 35 schemas 6 GET3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.2
API Version
2022-02-01
Base URL
https://finix.live-payments-api.com
Authentication
HTTP Basic
Contact
Resource Areas
1

Authentication & Security 1

Finix Disputes API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

Paths & Operations 11

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

Disputes 11

{'$ref': 'api-descriptions/tags/disputes.md'}

GET
/disputes
List Disputes
listDisputes 29 params → 200401403406
GET
/disputes/{dispute_id}
Fetch a Dispute
getDispute 1 param → 200401403404406
PUT
/disputes/{dispute_id}
Update a Dispute
updateDispute 2 params body → 200401403404406
POST
/disputes/{dispute_id}/evidence
Upload Files as Dispute Evidence
createDisputeEvidence 1 param body → 201401403404406
GET
/disputes/{dispute_id}/evidence
List Dispute Evidence
listDisputeEvidence 4 params → 200401403404406
GET
/disputes/{dispute_id}/evidence/{evidence_id}
Fetch Dispute Evidence
getDisputeEvidence 2 params → 200401403404406
PUT
/disputes/{dispute_id}/evidence/{evidence_id}
Update Dispute Evidence
updateDisputeEvidence 3 params body → 200401403404406
GET
/disputes/{dispute_id}/adjustment_transfers
Fetch Dispute Adjustment Transfers
listDisputesAdjustments 4 params → 200401403404406
POST
/disputes/{dispute_id}/submit
Submit Dispute Evidence
submitDisputeEvidence 2 params body → 200401403404406422
POST
/disputes/{dispute_id}/accept
Accept a Dispute
acceptDispute 1 param body → 200401403404406422
GET
/disputes/{dispute_id}/evidence/{evidence_id}/download
Download Dispute Evidence
downloadDisputeEvidence 2 params → 200401403404406

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are Transfer (37 properties), Dispute (19 properties), AdditionalPurchaseData (12 properties), DisputeEvidence (10 properties). Each schema is shown below with its type and property counts.

IdempotencyId
string
Pass any randomly generated or internal ID to [idempotently](/api/overview/section/Idempotency-Requests) identify Transfers, Authorizations, and refund request…
Amount
integer
The total amount that will be debited in cents (e.g. 100 cents to debit $1.00).
ErrorGeneric
object
2 properties
Messages
array
Message field that provides additional details. This field is typically null.
FailureMessage
string
A human-readable description of why the transaction was declined. This will also include a suggestion on how to complete the payment.
Error403ForbiddenList
object
2 properties
Raw
object
Raw response from the processor.
AcceptDispute
object
1 property 1 required
UpdatedAt
string
Timestamp of when the object was last updated.
PageCursor
object
Details the page that's returned.
2 properties
FeeType
string
Details the type of fee if the Transfer includes a fee.
CardPresentDetails
object
Details needed to process card present transactions.
7 properties
FileDownload
string
The file in question will begin to download.
AdditionalPurchaseData
object
Additional information about the purchase. Used for [Level 2 and Level 3 Processing](/guides/payments/modify/level-2-and-level-3-processing/).
12 properties 2 required
Dispute
object
A Dispute objected created for a chargeback or customer disputes.
19 properties
Transfer
object
37 properties
AdditionalHealthcareData
object
Optional object detailing [specific healthcare amounts](/guides/making-a-payment/hsa-fsa/).
4 properties
DisputeEvidenceList
object
3 properties
SubmitDisputeEvidence
object
1 property 1 required
Error404NotFoundList
object
2 properties
ListLinks
object
For your convenience, every response includes several URLs which link to resources relevant to the request. You can use these links to make your follow-up requ…
2 properties
CreateDisputeEvidenceRequest
object
1 property
LogRef
object
1 property
FailureCode
string
The code of the failure so the decline can be handled programmatically. For more info on how to handle the failure, see [Failure Codes](/guides/developers/erro…
PageOffset
object
3 properties
UpdateDisputeEvidence
object
1 property 1 required
Error406NotAcceptable
object
2 properties
Currency
string
ISO 4217 3 letter currency code.
AdjustmentTransfersList
object
3 properties
DisputeEvidence
object
10 properties
Error401Unauthorized
object
2 properties
CreatedAt
string
Timestamp of when the object was created.
DisputesList
object
3 properties
Tags
object
Include up to 50 key: value pairs to annotate requests with custom metadata. - Maximum character length for individual keys is 40. - Maximum character length f…
AdditionalBuyerCharges
object
Object detailing any [Buyer Charges](/guides/payments/making-a-payment/buyer-charges/) that got included in the Authorization.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

finix-disputes-api-openapi.yml Raw ↑

Other APIs Finix publishes across the network.

Finix Authorizations API
Finix Balance Transfers API
Finix Compliance Forms API
Finix Devices API
Finix Fee Profiles API
Finix Files API
Finix Identities API
Finix Instrument Updates API
Finix Merchant Profiles API
Finix Merchants API
Finix Onboarding Forms API
Finix Payment Instruments API
Where this information came from

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