HomePlatformFor Developers

// For Developers

Ship a headless, white-label ticketing stack on your own domain.

INTIX is API-first. Build your own checkout and fan experience on your front end, keep every buyer session and every backlink on your domain, and let the Graph API, webhooks and payments run underneath. Your traffic, your SEO, your data.

Book a Demo →Read the API docs →developer.intix.com/docs

// What you get

Graph API

120+ data points across ticketing, membership and access control

Checkout

Embedded white-label checkout on your own domain, no third-party redirect

Webhooks

Real-time events push every sale, member and scan to your stack

Fan data

100% yours. Legally siloed, never pooled with other organizations

01

White-label checkout on your domain

Build the whole checkout on your own domain, straight on the INTIX API, so fans never leave your brand. An A-League club runs its membership site this way: a fully custom front end wired directly into INTIX, not a templated storefront. The redirect to a third-party ticketing site is where competitors quietly capture your traffic, your retargeting audiences and your search authority. Keep all of it.

  • Your domain, your SEO. Event and checkout pages build authority for your site, not the vendor's.
  • No marketplace surface. Fans see your brand end to end, not a bidding wall of other events.
  • Own the pixel. Buyer sessions stay on your domain so first-party analytics and retargeting keep working.
  • Single basket. Tickets, memberships, merch and add-ons through one API.
checkout.js
// Custom checkout, built from scratch on the INTIX API
// (this is how an A-League club runs its membership site)

// 1. Open a basket for the org
const basket = await intix.post("/baskets", { org: "your-club" });

// 2. Add a membership (or tickets, merch, add-ons)
await intix.post(`/baskets/${basket.id}/items`, {
  price_id: "price_season_2026",
  quantity: 1
});

// 3. Take payment on your own page, then confirm
const order = await intix.post(`/baskets/${basket.id}/checkout`, {
  payment_method: paymentMethodId,
  customer: { email, first_name, last_name }
});
// order.status === "confirmed" -> render your own receipt

02

The Graph API: 120+ live data points

One structured API across ticketing, membership and access control. Read events, orders, tickets, members, seat maps, scans and settlement, and write back into your own systems in real time. Configurable from the admin when you want it, driven from the SDK when you need it.

  • 120+ data points spanning the whole fan lifecycle on one record.
  • REST + JSON. Predictable resources, token auth, versioned endpoints.
  • Write-back. Push segments and enrichment from your CRM back onto the fan.
  • Full reference at developer.intix.com/docs.
graph-api.sh
# Pull orders for an event, straight into your warehouse
curl https://api.intix.com/v1/events/evt_2Xa9/orders \
  -H "Authorization: Bearer $INTIX_KEY"

# => { "data": [ { "order_id": "...",
#      "fan": {...}, "tickets": [...],
#      "channel": "web", "total": 4200 } ] }

03

Real-time webhooks

Subscribe once and INTIX pushes every sale, membership change and gate scan to your endpoints as they happen. No polling, no nightly exports, no gaps between the box office and your CRM or data warehouse.

  • Event-driven. order.completed, member.updated, ticket.scanned and more.
  • Signed payloads you can verify before you trust them.
  • Fan-out anywhere. Warehouse, CRM, marketing tools, server-side tracking.
  • Retries so a downstream blip never loses an event.
webhook.js
// Every sale, in real time
app.post("/intix/webhook", (req, res) => {
  const evt = req.body;
  if (evt.type === "order.completed") {
    crm.upsertFan(evt.data.fan);
    ads.trackPurchase(evt.data.order); // server-side
  }
  res.sendStatus(200);
});

Wire it into the stack you already run

Use INTIX directly or connect it to your CRM, marketing, analytics and support tools. Anything the Graph API and webhooks can reach, you can automate.

HubSpot
Salesforce
Braze
Adobe Experience Cloud
Microsoft Dynamics
Microsoft Power BI
Tableau
Zendesk

Headless on your domain vs. hosted vs. marketplace

Where the traffic, the search authority and the fan data end up depends entirely on where the checkout lives.

INTIX (headless)Hosted checkoutMarketplace redirect
Checkout domainYour own domainVendor's domainMarketplace domain
SEO authority & trafficStays with youSplit with vendorCaptured by marketplace
Fan data ownership100% yours via APIVendor-held, exportablePlatform-owned
Branding at checkoutFully white-labelVendor chromeMarketplace brand
Real-time data exportWebhooks + Graph APICSV / limited APIRestricted
Custom build surfaceAPI-first, headlessTemplatedClosed

For developers

Questions from technical teams.

Build on ticketing you actually own.

Talk to a ticketing operator, not a slide deck. Or dive straight into the API reference and start building today.