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
Tabby

Tabby Disputes API

The Disputes API is designed to simplify the process of handling disputes and help merchants resolve issues with customer orders more efficiently. Merchants can use this API to retrieve a list of disputes, view details about a specific dispute, and approve or challenge a bunch of disputes. It mirrors the functionality available in Tabby Merchant Dashboard and operates exclusively with live payments using live credentials. A secret key is required for using the Disputes API.

Documentation Provider Profile APIs.io OpenAPI GitHub

Tabby Disputes API is one of 4 APIs that Tabby publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 7 JSON Schema definitions.

Tagged areas include Disputes. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 7 JSON Schemas.

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

Requests are made against 2 base URLs: https://api.tabby.ai/, https://api.tabby.sa/.

6 operations 6 paths 21 schemas 2 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.tabby.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Tabby Disputes API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth).

  • bearerAuth — Bearer authentication header of the form Bearer , where is your secretkey.

Paths & Operations 6

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

Disputes 6

The Disputes API is designed to simplify the process of handling disputes and help merchants resolve issues with customer orders more efficiently. Merchants can use this API to re…

GET
/api/v1/disputes
Get disputes list
getDisputes 4 params → 200400401404500
GET
/api/v1/disputes/{disputeId}
Get dispute by id
getDispute 1 param → 200400401404500
POST
/api/v1/disputes/{disputeId}/provide-evidence
Provide evidence for a dispute
postDisputeProvideEvidence 1 param body → 200400401404409500
POST
/api/v1/disputes/approve
Approve disputes
postDisputesApprove body → 200400401404500
POST
/api/v1/disputes/challenge
Challenge disputes
postDisputesChallenge body → 200400401404500
POST
/api/v1/disputes/attachments/upload
Upload attachment
postUploadAttachment body → 200400401500

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are Dispute (14 properties), DisputeNoHistory (13 properties), DisputeHistoryItem (7 properties), Evidence (6 properties). Each schema is shown below with its type and property counts.

Error_500
string
DisputeCreatedAt
string
Date and time the Dispute was created, in UTC, and displayed in ISO 8601 datetime format.
DisputeID
string
ID of the dispute.
DisputeDaysLeft
integer
How many days left before dispute will be automatically approved.
Evidence
object
6 properties 5 required
DisputeNoHistory
object
13 properties 13 required
DisputeComment
string
The customer additional comments on the causes of the dispute.
DisputeExpiredAt
string
Date and time of the expiration of the Dispute, in UTC, and displayed in ISO 8601 datetime format.
Error_400_bad_request
object
3 properties
Error_401_invalid_secret_key
object
3 properties
DisputeOrderItem
object
3 properties 3 required
PaymentID
string
Unique identifier for the payment (UUID), assigned by Tabby. Save it on your side!
Currency
string
ISO 4217 currency code for the payment amount. Currently there are 3 possible currency options - depending on the country where the store is located: - AED - U…
DisputeAttachments
array
Array of links to images which were uploaded by customer.
Error_404
string
DisputeStatus
string
The current status of the dispute: - new - dispute pending merchant approval for refund or initiate a challenge - declined - dispute was declined by Tabby supp…
Error_409
object
3 properties
DisputeReason
string
Cause of the dispute was created (selected by customer). There are only four reasons: - unreceivedrefund - a refund not received - identitytheft - I did not pl…
Dispute
object
14 properties 14 required
DisputeHistoryItem
object
7 properties 6 required
Error_404_dispute_not_found
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tabby-disputes-api-openapi.yml Raw ↑

Other APIs Tabby publishes across the network.

Tabby Checkout API
AE Profile APIs.io
Tabby Payments API
AE Profile APIs.io
Tabby Webhooks API
AE Profile APIs.io
#Disputes
← Back to T APIs
API Details
ID
tabby:tabby-disputes-api
Base URL
https://api.tabby.ai
Docs
https://docs.tabby.ai/api-reference/disputes
Provider
Tabby
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=tabby-disputes-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/tabby-disputes-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 Tabby 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.