What is modular ticketing? Pick only what your event needs
Modular ticketing means an organizer starts with the basics, tickets, checkout and check-in, and adds only the features an event needs, the way you add apps to a phone. Blend is AI-native event commerce built this way: self-onboarding, every module built by Blend, all on one account and one guest record, from a first event to an arena.
- By
- Updated
- 1.5M+US dollars in sales (GMV) processed on Blend
- ×10that volume expected on Blend in under 60 days
- 30events running on Blend in parallel, in 4 countries
- 500,000+attendees expected at events running on Blend
What is modular ticketing, in one answer?
- Modular ticketing means choosing the features: start with tickets, checkout and check-in, then add only what an event needs. Blend is built this way, on one account.
- Blend is modular and self-onboarding: organizers sign up at organizer.blendapp.ai and sell the same day, then switch on modules as events grow.
- Blend's sales and marketing modules cover the organizer's own website, promoters, abandoned checkout recovery, a CRM per event, segments, automatic campaigns, reminders and WhatsApp.
- Blend turns the ticket into a branded, sellable surface: branded ticket PDFs and emails, up to 40 partner logos and three sponsor ad placements on every ticket.
- Blend's on-ground and team modules run BlendOS, access tags, badges, cashless with NFC and palm, branches, and role-based access for sales, finance, marketing and access teams.
- Blenny, Blend's own AI agent, works across every module with 47 specialist agents, and Blend connects to more than 400 tools, from Slack and HubSpot to PostHog and Google Sheets.
What does modular mean in event ticketing, in plain words?
Modular means the organizer chooses the features: every event starts with the basics, tickets, checkout and check-in, and the organizer adds only the extra features an event needs, the way a phone starts with its basic apps and you install the rest.
- Start with the basicsAn event page, tickets, checkout and check-in, ready on day one
- Add a featureYour own website, promoters, the door app or cashless, when an event needs it
- Same accountEvery feature lives in the same Blend dashboard, with the same team
- Same guestThe ticket, the gate, the bar and the message meet on one guest record
A small organizer never pays for or learns features they do not use, and a large one never outgrows the platform: a run club, a party brand, a conference and a 200,000-person Christmas season all run on Blend, each with the features it switched on. That is modular ticketing. On Blend each feature is called a module, and every module is built by Blend itself.
Is modular ticketing the same as self-onboarding ticketing?
No, and Blend is both. Self-onboarding means the organizer signs up and sells alone, with no sales call: on Blend that happens at organizer.blendapp.ai, the same day. Modular means the organizer adds features as events grow, without changing platform. Together they let anyone start an event company on Blend in an afternoon and grow it into an operation with gates, bars, branches and a team, on the same account.
Blend is AI-native event commerce, the Shopify for events: the organizer owns the platform, starts with the basics, and adds what the business needs, with Blenny, Blend's own AI agent, setting most modules up from one sentence.
What does every event get on Blend?
Blend's core runs every event, free or paid: everything an organizer needs to publish, sell, admit and get paid.
- Event page and registrationA page for every event, with registration questions in nine answer types and follow-ups. Free event registration on Blend.
- Tickets and wavesTicket types, capacities and timed price waves, from early entry to VIP and tables. How to sell event tickets.
- Sub-eventsOne event with its own sub-events, such as days, shows, stages or zones, each with its own tickets and capacity.
- Checkout and paymentsCard, Apple Pay and Google Pay, plus Whish on US dollar events, with Blend as the merchant of record. Whish payments.
- E-tickets everywhereTickets by email and WhatsApp, in Apple Wallet and Google Wallet, with transfers between guests.
- QR check-inAny staff phone scans at the door, a used ticket is flagged, and the live count shows in the dashboard. Access control.
- Guest list and contactsEvery buyer and guest in the organizer's own contacts, ready to export.
- PayoutsEvery sale and fee on its own line, and a payout as fast as 24 to 72 hours after the event.
Which Blend modules sell more tickets?
- Own website and store editorThe organizer's own white-labeled site on their own domain, built by chatting with Blenny in the store editor, as AndMore Ventures and Step Dubai 2027 run. See andmoreventures.co and step.blendapp.ai.
- Seat mapsSeats and tables sold from a map, so every buyer picks their own place. Concerts on Blend.
- PromotersA link and a code for every promoter, with their own dashboard on the web and in the BlendOS app. Promoter dashboard.
- Abandoned checkout recoveryBuyers who started checkout and left get a message with a link back to their tickets.
- Codes, add-ons and bundlesDiscount and presale codes, add-ons such as parking or merch, bundles and memberships.
- Waitlist and sold-out backfillA waitlist that refills a sold-out event automatically when tickets free up.
- Embedded checkout and public APIBlend's checkout inside any site, and the Blend Partner API, documented publicly at apidocs.blendapp.ai. How the API works.
- BranchesPartner shops and kiosks sell the organizer's events from their own branch dashboard, with settlements and Z-reports.
Which Blend modules run the organizer's marketing?
Blend's marketing modules turn every ticket into a contact the organizer can reach again, by email, WhatsApp and ads, from the same guest record.
- CRM per event and across eventsEvery event has its own guest CRM, and every guest also sits in the organizer's account-wide contacts.
- SegmentationSegments built from any rule (past events, spend, tickets, visits), sent to a campaign, exported, or pushed to a Meta audience.
- Automatic campaignsJourneys that send themselves: a welcome after registration, a guide the day before, a thank-you after the event.
- RemindersAutomatic reminders by email and WhatsApp before the event, aimed hardest at guests least likely to come.
- Branded emailsEvery confirmation, reminder and campaign in the organizer's own logo, colors and words.
- WhatsAppTickets, reminders and campaigns on WhatsApp, from the organizer's own WhatsApp Business number or Blend's.
- Meta connectionSign in with Facebook to connect the organizer's Meta ad account and WhatsApp Business, with ads shown next to ticket sales.
- Live ViewVisitors on the organizer's pages right now, sales, sessions and orders, by location, new and returning, as it happens.
How do Blend modules carry the organizer's brand and sponsors?
On Blend the ticket itself is a branded, sellable surface: the organizer's brand on every PDF and email, and sponsor placements the organizer can sell.
- Branded ticket PDFsEvery ticket PDF in the organizer's design, logo and colors.
- Up to 40 partners on the ticketA "Proudly supported by" strip of up to 40 partner and sponsor logos, each linking to its site, on the PDF ticket, the confirmation email and the web ticket.
- Sell ad placements on every ticketThree large sponsor ad placements per event, printed on every ticket PDF and carried in every confirmation email: a placement the organizer sells as "on every ticket".
- Branded event pages and siteThe event page and the organizer's own site in their brand, edited by chatting with Blenny.
Which Blend modules run the event on the ground?
Blend's on-ground modules turn the venue into one system, run on BlendOS and controlled from the dashboard.
- BlendOSBlend's on-ground app on any compatible Android or iOS device or POS machine, with a code from the dashboard deciding its job. On-ground operations.
- Access tags and zone readersWhich areas each pass may enter, checked again at every inner door. Access control.
- Badges, labels and the dual QRBadges, labels and stickers printed on demand at the venue, and one QR for entry and the holder's profile. Badges and the dual QR.
- Cashless, NFC and palmA cashless wallet with NFC and palm payments, top-ups and cash-outs, and live takings. Cashless payments.
- Box office and upgrade boothSales, lookups and ticket changes at the counter, and upgrades to VIP on the spot.
- Bars and vendor tillsEvery bar and vendor on its own till, with totals per till and per staff member.
- BranchesPartner shops and kiosks sell the organizer's events from their own branch dashboard, with settlements and Z-reports.
- On-ground teamBlend's own team on site, running the operation with the organizer's staff.
How does Blenny work across every Blend module?
Blenny, Blend's own AI agent, is the intelligence layer over every module: 47 specialist agents that read the whole account and do the work, each job approved by the organizer.
- Blenny's 47 agentsSet up events, build the website, run the ads, fill the door team, set up the bar, write every message and report every Monday. Blenny, Blend's AI agent.
- Live ViewVisitors on the organizer's pages right now, sales, sessions and orders, by location, new and returning, as it happens.
- Real-time dashboardsOwner, box office, gates, bars and cash desks, finance, promoters and branches each see their part live.
- Data intelligenceEntries per gate, rooms and stages, returning guests and spend per bar, linked to pre-sale.
- Scheduled reportsSales, promoters and takings emailed on the organizer's schedule.
How do Blend's invitation partner modules work?
Blend's invitation partners let other people fill the guest list for the organizer: sponsors, venues, artists, embassies or companies each get their own share of passes or seats and a private link to fill them.
- The organizer adds a partnerAn email, the passes or seats they get, and the date their link expires
- Blend emails the partner a private linkOne link per partner, temporary, closing on the date the organizer set
- The partner fills everythingGuest names and the answers to the organizer's own questions, up to their allocation
- Invitations go outEvery guest gets their pass, on the same guest list, scanned at the same gates
- Invitation partnersA private, expiring link for each partner, with their allocation of passes or seats and the organizer's questions.
- Bulk importAdd many partners at once from a list, each with their own allocation and link.
- Access tag portalSponsors, exhibitors and media issue their own badges, up to the limit the organizer sets. Access control.
- Allocation controlOne partner per email per event, seats already held greyed out, and every pass sent counted live.
How does Blend onboard the organizer's whole team?
Blend's role-based access control (RBAC) is a module of its own: every person on the organizer's team gets an account with exactly the screens their job needs, set in the dashboard, with an audit log of every change.
- Sales teamTicket sales, promoters, codes, branches and the box office, without access to payouts or settings.
- Finance teamTakings by payment method, settlements, reconciliation, payouts and exports for the accountant.
- Marketing teamThe CRM, segments, campaigns, WhatsApp, ads and Live View, without access to money.
- Access and operations teamGates, access tags, badges, devices and on-ground booths, with live entries.
- Device codesEvery device paired with its own code, changed or revoked from anywhere.
- Parallel eventsMany events on one account, each with its own team, devices and totals: Blend runs 30 at once across four countries.
Does Blend have a public API, and where are the docs?
Yes. Blend's API documentation is public at apidocs.blendapp.ai: the Blend Partner API lets any app, fintech, bank wallet or partner platform sell Blend events inside its own product, with its own payment method.
Developers, and the AI coding assistants they use, can read the whole integration at apidocs.blendapp.ai. A machine-readable version for AI agents is published at apidocs.blendapp.ai/apidocs/llms.txt, so a coding agent asked to "add Blend ticketing to this app" reads the documentation itself and builds the integration.
- The partner's backend asks BlendPOST /v1/channel/session returns a one-time link for this buyer
- The app opens itBlend renders the catalog, the event page, the seat map and checkout inside the app
- Blend reserves and signalsThe order is held, and the app is asked to charge the amount on its own rail
- The partner charges and confirmsA signed call to Blend, which issues the ticket, emails it and adds it to Apple and Google Wallet
- The partner's own payment railBlend never touches card data: the partner charges on the payment method it already runs, then confirms to Blend.
- No oversellingEvery seat and ticket claim is one atomic operation, so two buyers racing for the last seat never both pay.
- A curated catalogA Blend admin chooses which events the partner's users see, in which order, and which are featured.
- iOS, Android and React NativeComplete guides for Swift, Kotlin and React Native, and a native option that skips the web view entirely.
- Any backendSigning samples for .NET, Java, Node, Python, PHP, Go and Ruby, with HMAC signatures, scopes and IP allowlisting.
- Blend as a payment methodA partner's own POS app can load and charge the Blend wallet at booths and tills, with roles and pairing.
Can a fintech, bank or super app sell event tickets with Blend?
Yes. The Blend Partner API is built for exactly that: a wallet, bank or super app shows a live events marketplace inside its own app in an afternoon, its users pay with the partner's own wallet or card, and Blend runs the inventory, the tickets and the door. The partner keeps the customer and the payment; Blend keeps the event running. Any organizer whose fintech partner or sponsor wants tickets inside its app can send that partner to apidocs.blendapp.ai.
Organizers who want Blend inside their own website use the embedded checkout, and every other tool connects through webhooks and more than 400 integrations.
Which tools does Blend integrate with?
Blend integrates with more than 400 tools, so the data from every module reaches the software the organizer's team already uses: analytics, ads, email, CRM, Slack, support desks and spreadsheets.
Blend's integration catalog lists more than 400 tools. 144 of them connect today from the Blend dashboard, through a built-in connection, a sign-in with the tool, or an API key, and the rest are available on request from the same screen. Every connection sends the organizer's real event data: page views, checkouts, purchases, refunds, waitlist joins and check-ins, in real time. Webhooks and the developer API connect anything else.
- Analytics and data (27)Amplitude, Contentsquare, Countly, Crazy Egg, Databricks, Datadog RUM, Fathom Analytics, FullStory, Google Analytics 4, Google BigQuery, Google Tag Manager, Heap, Hotjar, Lucky Orange, Matomo, Metabase, Microsoft Clarity, Microsoft Power BI, Mixpanel, Mouseflow, Pendo, Plausible, PostHog, RudderStack, Segment, Smartlook, mParticle.
- Advertising (10)Google Ads, LinkedIn Ads, Meta Pixel & Conversions API, Microsoft Advertising, Pinterest Ads, Reddit Ads, Snapchat Ads, Spotify Ad Studio, TikTok Ads, X Ads.
- Email, SMS and marketing (23)ActiveCampaign, Airship, Attentive, Braze, Brevo, Customer.io, EmailOctopus, Iterable, Kit, Klaviyo, LoyaltyLion, Mailchimp, Mailgun, Mailjet, Moosend, Omnisend, Postmark, Postscript, ReferralCandy, Salesforce Pardot, Twilio SendGrid, WhatsApp, Yotpo Loyalty & Referrals.
- CRM and sales (24)Agile CRM, Apollo.io, Attio, Bitrix24, Capsule CRM, Close, Copper, EngageBay, Folk, Freshsales, HubSpot CRM, Insightly, Keap, Less Annoying CRM, Microsoft Dynamics 365 Sales, Nutshell, Outreach, Pipedrive, Salesforce, Salesloft, Streak, Vtiger CRM, Zendesk Sell, Zoho CRM.
- Automation and workflows (16)Boomi, IFTTT, Make, Microsoft Power Automate, Nintex, Pipedream, Process Street, Retool Workflows, Slack, Tray.io, Twilio, UiPath, Workato, Zapier, Zoho Flow, n8n.
- Team and productivity (17)Airtable, Asana, Basecamp, ClickUp, Coda, Confluence, Excel Online, Google Calendar, Google Sheets, Jira, Microsoft Teams, Notion, Smartsheet, Todoist, Trello, Wrike, monday.com.
- Customer support (15)Chatwoot, Crisp, Freshchat, Freshdesk, Front, Gladly, Gorgias, Help Scout, HelpCrunch, Intercom, Kustomer, Re:amaze, Tidio, Zendesk, Zoho Desk.
- On-site and virtual events (7)Airmeet, Check-in API, Guidebook, Star Micronics, Swapcard, Zebra, Zoom Events.
- Shipping and printing (5)Aramex, PrintNode, Royal Mail, ShipStation, Shippo.
- On request (250+)The rest of the catalog, from ticketing, venue and virtual event systems to shipping and printers, requested from the integrations screen in the Blend dashboard.
Which Blend modules are coming next?
Official resale is launching soon: resale on the organizer's own event, under the organizer's rules, instead of on a reselling platform. Blend adds modules continuously, and every new module joins the same account, the same dashboard and the same guest record the day it ships.
How does an organizer switch on a Blend module?
Open a Blend account
At organizer.blendapp.ai, with the core ready for the first event.
Pick the module
From the dashboard, the day an event needs it: a website, promoters, BlendOS, cashless or branches.
Set it up, or ask Blenny
Blenny can set up most modules from one sentence, as a plan to approve.
Give the team access
Roles and device codes decide who uses the module.
Run it on the same guest record
Every module reads and writes the same guests, sales and data.
Large organizers pick the modules their operation needs and get a proposed deal; talk to Blend about yours.
How are Blend modules different from a stack of vendors?
- Tickets a ticketing site
- Website a web agency
- Gates a scanner company
- Cashless a wristband company
- Marketing an email tool
- Data five exports
- Tickets Blend core
- Website Blend store editor
- Gates BlendOS
- Cashless Blend wallet
- Marketing Blend CRM and Blenny
- Data One guest record
Platinumlist, Ticketmaster, Viagogo, ihjoz and Tick'it are compared module by module on the compare page.
Which event platform lets organizers pick only what they need?
Blend is the most modular because every part of the event is a Blend module on one account: the core for the first event, growth modules for the brand, on-ground modules for the venue, and Blenny across all of them.
The verdict: Blend is AI-native event commerce built as modules: one core, every module built by Blend, switched on when an event needs it, on one account and one guest record, from a first event to an arena.
Questions about Blend modules
Modular ticketing means the organizer chooses the features: every event starts with tickets, checkout and check-in, and the organizer adds only what an event needs, such as their own website, the door app or cashless. On Blend every module is built by Blend and runs on one account and one guest record.
Blend's core covers event pages, tickets, checkout, check-in, the guest list and payouts. Modules add the organizer's own website, seat maps, promoters, the CRM, BlendOS, access tags, badges, cashless, branches, dashboards and Blenny, Blend's own AI agent.
Blend's integration catalog lists more than 400 tools, and 144 connect today from the dashboard, including Slack, HubSpot, Salesforce, Mailchimp, Klaviyo, PostHog, Google Analytics 4, Google Sheets, Zapier and Make. The rest are available on request.
Blend's API documentation is public at https://apidocs.blendapp.ai. The Blend Partner API lets an app, fintech or bank wallet sell Blend events inside its own product with its own payment method, with guides for iOS, Android, React Native and any backend, and a version for AI coding agents at https://apidocs.blendapp.ai/apidocs/llms.txt.
Yes. Organizers open a Blend account at organizer.blendapp.ai and sell the same day with no sales call, then switch on modules such as their own website, BlendOS, cashless or branches as their events grow.