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 Checkout API

Checkout is a whole process of customer data collection and payment authorization.

Documentation Provider Profile APIs.io OpenAPI GitHub

Tabby Checkout 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 Checkout. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 7 JSON Schemas.

This API exposes 2 operations across 2 paths, and defines 39 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/.

2 operations 2 paths 39 schemas 1 GET1 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 Checkout 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 2

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

Checkout 2

Checkout is a whole process of customer data collection and payment authorization.

POST
/api/v2/checkout
Create a session
postCheckoutSession body → 200400401403404500
GET
/api/v2/checkout/{id}
Retrieve an existing checkout session
getCheckoutSession 1 param → 200400401403404500

Schemas 39

The contract defines 39 schemas that model the data the API accepts and returns. The most detailed are OrderItem (19 properties), OrderItemHistoryRequest (19 properties), OrderItemResponse (15 properties), CheckoutCreation (10 properties). Each schema is shown below with its type and property counts.

Buyer
object
Customer information
4 properties 3 required
Error_400
object
3 properties
OrderItemResponse
object
15 properties 4 required
CheckoutConfigurationProduct
array
HotelReservationDetails
object
5 properties 3 required
Error_500
string
Error_401_merchantNull
object
3 properties
OrderResponse
object
6 properties 2 required
PaymentCreatedAt
string
Date and time the payment was created, in UTC, and displayed in ISO 8601 datetime format.
AttachmentPaymentHistorySimple
object
4 properties
CheckoutProductRejectionReason
string
The reason why this product is not available to use Possible values: orderamounttoohigh - 'This purchase is above your current spending limit with Tabby, try a…
Attachment_V1
object
Extra data (booking info, insurance, flight reservations, ...) as serialized JSON
2 properties 2 required
InsuranceDetails
object
3 properties 2 required
FlightReservationDetails
object
5 properties 3 required
CheckoutSession
object
6 properties
Error_403
object
2 properties
Error_401_key_doesnt_exist
object
3 properties
OrderItem
object
19 properties 4 required
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…
PaymentID
string
Unique identifier for the payment (UUID), assigned by Tabby. Save it on your side!
AttachmentPaymentHistoryFull
object
9 properties
Error_404
string
PaymentAmount
string
Total payment amount, including tax, shipping and any discounts. Allows to send up to 2 decimals for AED and SAR, up to 3 decimals for KWD.
PaymentStatus
string
Status of the current payment: - CREATED means that the payment is created successfully, but not finished yet; - AUTHORIZED and CLOSED mark the successfully ap…
MerchantUrls
object
Used for redirecting the customer after Tabby Checkout flow. Required for Web integration, optional for Mobile App integration.
3 properties
BuyerHistory
object
Customer information. registeredsince (as a date of the customer's registration in the App), loyaltylevel (as a number of successful orders) and wishlistcount…
6 properties 2 required
Marketplaces
object
Sellers' details within marketplaces.
7 properties 7 required
CheckoutProduct
object
3 properties 2 required
LanguageCode
string
Session language, used to launch HPP with desired language.
EducationDetails
object
Education-vertical risk signals for the current session.
3 properties 3 required
Meta
object
Merchant-defined data about the payment. This field is a key-value map. The example properties provided below.
2 properties
ShippingAddress
object
3 properties 3 required
OrderItemHistoryRequest
object
19 properties
CheckoutResponsePayment
object
Payment object associated with the current session.
10 properties 7 required
FlightPointsSimple
object
2 properties 2 required
CheckoutCreationOrderHistory
object
7 properties 5 required
Error_400_CheckoutPost
object
3 properties
CheckoutCreation
object
Payment object associated with the current session.
10 properties 7 required
Order
object
6 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tabby-checkout-api-openapi.yml Raw ↑

Other APIs Tabby publishes across the network.

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