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.
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.1.0, at version 1.0.0.
Requests are made against 2 base URLs: https://api.tabby.ai/, https://api.tabby.sa/.
Metadata
The identity and technical contract details declared by the specification.
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.
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…
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.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Tabby 3
Other APIs Tabby publishes across the network.