# How it works

The White-Label API gives you one job: **call REST over `/v1`**. Everything that
makes a ticket trustworthy and every cent of settlement happens behind that
boundary, automatically. You think in events, tickets, prices, and customers —
nothing else.

You make a normal HTTPS request with a bearer key; we do the hard parts and
return plain JSON. No SDK is required, though the
[OpenAPI document](#introduction) makes one easy to generate.

## The object model

Everything you create lives in a simple hierarchy, plus a few free-standing
resources that hang off it.

```text
Account  (you — the partner)
  └─ Events               a show, match, conference, etc.
        └─ Tiers           price levels within an event (GA, VIP, …)
              └─ Tickets   issued to a customer, each tamper-proof

Organizations  read-only organizer directory your account can browse
Customers      email-first people who hold tickets
Payments       card charges that gate issuance and upgrades
Queues         on-sale waiting rooms for high-demand events
Listings       secondary-market resale entries for tickets
Payouts        fiat transfers of your balance to your bank
```

| Object | What it is | Reference |
| --- | --- | --- |
| **Account** | Your partner account — branding, mode, settlement currency. | [Account](#api-account) |
| **Organization** | An event organizer your account can read from the catalog. | [Events](#api-events) |
| **Event** | A single event you sell tickets for. | [Events](#api-events) |
| **Tier** | A price level on an event (name, price, supply, perks). | [Events](#api-events) |
| **Ticket** | An issued, tamper-proof ticket held by a customer. | [Tickets](#api-tickets) |
| **Customer** | A person who holds tickets, identified by email. | [Customers](#customers) |
| **Payment** | A card charge, computed and verified server-side. | [Payments](#money-and-currencies) |
| **Queue** | The waiting room gating issuance for a high-demand on-sale. | [Events](#api-events) |
| **Listing** | A secondary-market resale of a ticket. | [Marketplace](#api-marketplace) |
| **Payout** | A fiat transfer of your balance to your bank. | [Payouts](#payouts) |

## Built-in guarantees

Several hard problems are handled by the platform itself — there is nothing to
integrate, configure, or operate on your side. You get the benefits without the
complexity:

* **Tamper-proof tickets** — every ticket is verifiable and cannot be forged or
  duplicated.
* **Built-in anti-scalping** — resale rules are enforced automatically on the
  marketplace.
* **Automatic resale royalties** — you keep earning on the secondary market with
  no extra work.
* **Plain fiat, end to end** — prices, charges, refunds, and payouts are all in
  your account's currency.

> **Note:** You work entirely in business language: events, tiers, fiat prices, customer
> emails, QR codes, and bank payouts. The tamper-proof layer is an implementation
> detail you never have to learn.


## Test vs live

Every account has an isolated test mode (`sk_test_…`) and live mode
(`sk_live_…`); test data never mixes with live. See
[Test & live modes](#test-and-live-modes).