Skip to main content
In this part of the documentation all the needed API calls for Tabby Integration can be found and tested:
  • Checkout - it is a whole process of customer data collection and payment authorization.
  • Payments - the core of Tabby is a payments flow enabling you to handle payments at your webstore.
  • Webhooks - serve to ensure a seamless payment verification flow.
  • Dispute webhooks - notify you when a dispute is opened on your payment or changes its status.
  • Disputes - help merchants resolve issues with customers orders more efficiently.

​
Base URLs

Tabby uses region-specific domains. Choose the base URL based on the merchant’s operating country: All API paths and payloads are identical across both domains. Tabby identifies the environment (test or live) based on the API keys used.
Use the base URL that matches the merchant’s region for every call. Many existing integrations call api.tabby.ai for all regions and rely on Tabby-side request routing — but not every endpoint is routed (e.g. payments retrieval and disputes), and cross-region calls can return 404/403. New integrations must pin all calls — session creation, payment retrieval, captures, refunds, webhooks, dispute webhooks, disputes — to the regional base URL.

​
OpenAPI Specification

To access and download the raw OpenAPI specification file kindly use this: openapi.yaml. You can also view this API specification using ReDoc, the same is present below: