Warming up the decks…
BlendPartner APIblendapp.aiPowered by Blend
Ticketing that lives inside your app.
Your users browse real events, pick real seats and pay with your own payment method — without leaving your app. Blend runs the inventory, the tickets and the door. You keep the customer.
# Your backend. One call — the app never holds a key.
curl -X POST https://api.blendapp.ai/api/v1/channel/session \
-H "x-blend-key: ck_live_xxxxxxxxxxxxxxxx" \
-H "x-blend-secret: cs_live_xxxxxxxxxxxxxxxx" \
-d '{"buyerName":"Rami","buyerEmail":"rami@example.com"}'
# → open data.url in your WebView. That is the integration.
{ "url": "https://blendapp.ai/channel/session?token=0f3a…" }Cannot oversellEvery claim is one atomic compare-and-set. Two buyers racing for the last seat: one wins, the other is told before any charge.
Your payment railBlend never touches card data. You charge on the rail you already run, then confirm to Blend with a signed call.
A catalog you agreeAn admin picks the events your users see, orders them and features them. Nothing appears that was not switched on.
iOS and AndroidOne message contract, both platforms, with a visible failure state when no bridge is registered — never a dead Pay button.
The whole integration
Five steps. Your backend makes two calls, your app registers one handler, and Blend does the rest — catalog, event pages, seat maps and checkout all render inside your WebView.
Lifecycle
1. Your backend POST /v1/channel/session
-> a one-time WebView URL for this buyer
2. Your app open that URL in a WebView
-> Blend renders catalog, event, seats, checkout
3. Blend reserves the order, then signals your native code:
{ type: "charge", orderId, amount, currency }
4. Your app charge on your own rail
Your backend POST /v1/channel/orders/confirm (signed)
-> Blend issues the ticket
5. Blend shows the ticket in the WebView, emails it,
and adds it to Apple / Google WalletYour app never holds a Blend credential
Every call that needs the secret is a backend call by design. The app only ever receives a URL from your own server and a message asking it to charge.
Start here
QuickstartA working integration end to end, in build order.How it worksThe architecture, in plain language, for whoever approves it.AuthenticationWhich key goes where, and what to do if one leaks.Inventory & seat holdsHow overselling is made impossible, precisely.Taking the paymentThe native bridge on both platforms, and its trust model.Mobile guidesSwift, Kotlin and React Native, copy-paste complete.