EventcubeDevelopers

For developers

Enterprise ticketing API, built into your product

Eventcube runs ticketing for arenas, festivals and global conference series — white label, on your own domain, at scale. Embed a branded box office in an afternoon, or drive the entire catalogue and checkout through the API.

Read the docsStart with an embed

REST · Bearer auth · JSON · no SDK required

Create a cart
POST /api/v1/carts
Authorization: Bearer {api_token}
{
  "items": [
    { "ticket_id": 1, "quantity": 2 }
  ]
}
// 200 OK — created cart
{
  "token": "abc123token",
  "checkout_url": "https://your-store.eventcube.io/checkout/payment/abc123token",
  "totals": {
    "currency": "GBP",
    "subtotal": "5000",
    "fees": "300",
    "total": "5300"
  }
}

A ticketing system trusted by global brands

Logos of brands running ticketing on Eventcube, including Uber, H&M, TikTok, Red Bull, AEG Presents, TEDx, The O2 and American Express

Three ways in

Pick the depth of integration you actually need

Most teams start with an embed and move deeper later. Nothing you build early gets thrown away.

Minutes

Embed a box office

Drop your ticket store into any page. It resizes to fit, takes your branding, and handles the entire purchase without you writing a line of backend code.

Start with embeds →

Full control

Build on the API

Create events, tickets, carts and orders programmatically. Run your own checkout UI, or hand off to Eventcube-hosted payment with a single redirect.

Explore the API →

No code

Wire up your stack

Connect ticket sales to the tools you already run — CRM, email, spreadsheets, internal alerts — through Zapier's 6,000+ app directory.

See integrations →

White label by default

Your customers never see us

White label isn’t a logo-removal setting bolted on at the end. The platform was built to disappear behind whatever you put in front of it.

  • Sell on your own domain — stores carry their own custom domains, not a subdomain of ours
  • Your own Stripe account via Stripe Connect — charges settle to you, not through us
  • Your customer data stays yours — queryable over the API and exportable in full
  • Confirmation emails from your own address and sender name, with an optional custom sending domain
More on white label ticketing →
Your domain, your token
# The store is resolved from the hostname —
# there is no store ID header to pass.
curl https://tickets.yourbrand.com/api/v1/events?only_listable=1 \
  -H "Authorization: Bearer YOUR_API_KEY"

Checkout

A working purchase flow in three calls

1

Create a cart

POST /carts with ticket IDs and quantities. You get back a cart token, live totals, and a hosted checkout_url if you want to stop here.

2

Attach the buyer

PATCH /carts/{token} with customer details and ticket holders. Apply a discount with POST /carts/{token}/discount-code.

3

Create the order

POST /orders with the cart_token. Or skip it entirely and redirect to checkout_url to let Eventcube collect payment.

Money is in minor units, every date and time is UTC, and inventory conflicts come back as 409. The conventions page covers the rules that apply to every endpoint.

Cart → order
POST /api/v1/carts
{
  "items": [
    {
      "ticket_id": 1,
      "quantity": 2,
      "ticket_holders": [
        { "first_name": "Alice", "last_name": "Smith" },
        { "first_name": "Bob", "last_name": "Jones" }
      ]
    }
  ]
}
POST /api/v1/carts/abc123token/discount-code
{ "code": "SAVE10" }
POST /api/v1/orders
{
  "cart_token": "abc123token",
  "customer": {
    "email": "buyer@example.com",
    "first_name": "Buyer",
    "last_name": "Test",
    "country": "GB"
  }
}

Enterprise

What you get beyond the endpoints

An API is the easy part. The reason large organisations move onto Eventcube is everything around it.

Built for volume

The same platform behind arenas, festivals and international conference series — not a small-events tool stretched upward.

You own the relationship

Your domain, your own Stripe account, your customer records. Nothing routes through us that doesn't have to.

Security you can audit

A public trust centre and a vulnerability disclosure programme, so your security review has something real to read.

Advisors, not ticket queues

Technical advisors will work through your requirements and put together an architecture that fits before you write code.

Eventcube Enterprise

What teams build

One engine, very different products

Arenas and large venues

Push a season of fixtures from the scheduling system your team already runs, and pull orders back for reconciliation and reporting.

Festivals and multi-day events

Tiered releases, complex ticket types and ticket-holder data captured per attendee — created programmatically rather than by hand.

Global conference series

One platform across many events and regions, each selling on its own domain with its own branding and its own payment account.

Platforms reselling ticketing

Offer ticketing to your own customers as a feature of your product, with Eventcube as the engine and your brand on every surface.

“Eventcube have been the perfect tech partner to integrate with. Their ticketing API is comprehensive and robust. They act more like an agency than a ticketing provider and are always on hand to troubleshoot any questions we had along the way.”

Lokkaroom

Build it with us

Tell us what you're integrating and we'll point you at the right endpoints — or hand you to a technical advisor who has built it before.

Talk to usRead the docs