Skip to main content

Getting Started

The Ticket Buyback Partner API enables approved third-party partners and affiliates to integrate ticket resale functionality directly into their own platforms.

With a single integration you can discover events, browse seat availability, generate price quotes, and create confirmed orders — all without handling end-customer payment details.

Base URL​

All API requests are made to:

https://api.ticketbuyback.com/partner

How It Works​

The full partner flow follows these five steps:

1. Authenticate        →   Exchange credentials for an access token
2. Discover Events     →   Search events, venues, and performers
3. Browse Seats        →   Get available sections and rows
4. Create a Quote      →   Lock in a price for a seat/quantity combo
5. Create an Order     →   Convert the quote into a confirmed order

Once an order is confirmed, Ticket Buyback returns a ticket transfer email address — your customer accepts the transfer directly from that address.

Before You Begin​

You must have the following before making any API calls:

RequirementDetails
TBB Partner AccountProvisioned manually by Ticket Buyback during onboarding
client_idPublic identifier issued at onboarding
client_secretSecret key issued at onboarding — treat like a password
Routable Payment MethodMust be configured on your TBB account before quotes or orders can be created
Need an account?

Contact the Ticket Buyback team at support@ticketbuyback.com to get your partner account provisioned.

What You Can Do​

CapabilityAPI Flow
Discover events, venues, performersDiscovery API
Browse available sections and rowsSections & Rows API
Request a sell price quote for a ticket groupCreate Quote API
Convert a quote to a confirmed orderCreate Order API
Receive ticket transfer email for your buyerOrder Response

What You Cannot Do​

  • Access another partner's quotes or orders
  • Bypass the Routable payment configuration requirement
  • Receive end-customer funds through Ticket Buyback
  • Create orders without a valid, unexpired quote
  • Use the API without a pre-provisioned TBB partner account

Core Design Principles​

Partner-centric billing — Ticket Buyback charges and pays the partner. You manage your own end customer.

No end-user PII required — TBB does not collect or store end-customer emails, phone numbers, or payment details.

Pre-configured payment methods — Partners must configure Routable payout methods on their TBB account before API access is granted.

Scoped token authentication — Each partner account gets isolated API credentials. Tokens are short-lived and cryptographically signed.

Quote-based ordering — All orders require a valid, unexpired quote. Quotes have a defined TTL and become the binding price contract.

Authentication Overview​

The API uses a two-step authentication pattern:

Step 1 — Post your client_id and client_secret to /v1/auth/token to receive a short-lived access token.

Step 2 — Include that token as a Bearer token in the Authorization header on every subsequent request.

Authorization: Bearer <your_access_token>

Tokens are valid for 1 hour. After expiry, re-authenticate to get a new token.

→ See the full Authentication guide for details.

Standard Request Headers​

Authorization: Bearer <token>       # Required on all authenticated endpoints
Content-Type: application/json      # Required on POST/PUT requests
Accept: application/json            # Recommended
X-Request-ID: <uuid>                # Optional — echoed back for tracing

Response Format​

All responses follow a standard envelope:

{
  "success": true,
  "data": { },
  "meta": {
    "request_id": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-02-26T10:30:00Z"
  }
}

Errors always return "success": false with an error object:

{
  "success": false,
  "error": {
    "code": "QUOTE_EXPIRED",
    "message": "The requested quote has expired. Please create a new quote.",
    "details": {
      "quote_id": "qt_abc123",
      "expired_at": "2026-02-26T09:00:00Z"
    }
  },
  "meta": {
    "request_id": "550e8400-e29b-41d4-a716-446655440000",
    "timestamp": "2026-02-26T10:30:00Z"
  }
}

→ See the full Error Reference for all error codes.

Next Step​

Once your account is provisioned and Routable is configured, start here:

→ Authentication — Get your access token

Last updated on