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

JustiFi Disputes API

A customer may dispute their payment with the card issuer/bank if they believethe charge is erroneous. When this happens, a dispute record is created andassociated with their original payment.

JustiFi Disputes API is one of 28 APIs that JustiFi 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 and authentication docs.

This API exposes 6 operations across 4 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, https://api.justifi.ai/v1.

6 operations 4 paths 6 schemas 2 GET2 PATCH1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.justifi.ai/v1
Terms of Service
Resource Areas
1

Paths & Operations 6

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

Disputes 6

A customer may dispute their payment with the card issuer/bank if they believe the charge is erroneous. When this happens, a dispute record is created and associated with their or…

GET
/disputes
List Disputes
ListDisputes 2 params → 200
GET
/disputes/{id}
Get a Dispute
GetDispute 2 params → 200
PATCH
/disputes/{id}
Update a Dispute
UpdateDispute 3 params body → 200
PUT
/disputes/{id}/evidence
Create dispute evidence
CreateDisputeEvidence 2 params body → 201
PATCH
/disputes/{id}/response
Update dispute response
UpdateDisputeResponse 2 params body → 200
POST
/disputes/{id}/response
Submit dispute response
SubmitDisputeResponse 2 params body → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are DisputeResponse (17 properties), Dispute (13 properties), DisputeEvidence (7 properties), Envelope (4 properties). Each schema is shown below with its type and property counts.

PageInfo
object
4 properties
DisputeResponse
object
17 properties
Dispute
object
13 properties
Envelope-list
object
4 properties
DisputeEvidence
object
7 properties
Envelope
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

justifi-disputes-api-openapi.yml Raw ↑

Other APIs JustiFi publishes across the network.

JustiFi Ach Return Fees API
JustiFi Address API
JustiFi API Credentials API
JustiFi Balance Transactions API
JustiFi Bank Account API
JustiFi Bind Insurance API
JustiFi Business API
JustiFi Checkouts API
JustiFi Document API
JustiFi Fee Configurations API
JustiFi Identity API
JustiFi Payment Method Groups API
Where this information came from

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