Skip to main content
GET
Retrieve an existing checkout session
This endpoint is intentionally hidden from the main API documentation and should only be used in specific integrations where its purpose is well understood. It is accessible via direct link for those who require it, but is not intended for general use or new standard implementations.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <secret_key>, where <secret_key> is your secret_key.

Path Parameters

id
string<uuid>
required

ID of the session.

Example:

"session id, uuid format"

Response

Success. Checkout session object is returned.

id
string<uuid>
read-only

Unique identifier for the checkout Session, assigned by Tabby.

Example:

"session id, uuid format"

configuration
object

Some details associated with the current session.

token
string | null

In the response, this field will be filled with token value if session status is 'approved'. You can use that token for Tokenized Payments and Web Checkout.

Example:

null

payment
object

Payment object associated with the current session.

status
enum<string>
read-only

Status of the current session. Used at the pre-scoring and session creation steps.

  • created is returned when the request is approved and the customer is eligible to use Tabby
  • rejected means that there are no available products for a customer
  • expired and approved - used for specific type of integration, kindly ignore them if not communicated directly
Available options:
created,
rejected,
expired,
approved
Example:

"created"

merchant_urls
object
merchant
object
read-only

Merchant the session was created for.