Skip to content

Ticket allocation · sales channels

Set aside seats for every audience, from one seat map.

Hold seats for sponsors, give agencies their own access, run a member presale, and keep the box office and public sale on the same event. Each audience gets its own seats, prices and report, and a seat can never be sold twice. Built for stadium and arena on-sales as well as theatres.

Allocations, links and reports cost nothing.

You pay only when a seat is confirmed sold: $0.50 a hosted ticket, or 10¢ to 5¢ a sold seat on the SDK.

Friday Evening · one event, one seat mapOn sale · assignment version 12

0 of 200 seats sold across five audiences, from one inventory.

One inventory, never copied. A seat sold in one channel is gone from every other channel at once.

Ticket allocation

What is a ticket sales channel?

A named group of seats inside one event, such as sponsors or a presale. It is not a copy of the event or a second seat map.

Direct answer

A channel can represent public sales, a sponsor, an agency, a member presale, a group coordinator, or box office. Each seat belongs to one channel at a time, and you decide who can buy from which channels.

Everyone sells from the same live seats, so once a seat sells, it cannot be sold again through another audience.

One event · one seat map · no duplicate inventory

Friday Evening · event inventory

  • 1,000seats of capacity
  • 4audiences
  • 1inventory source
  • Public · 800
  • Travel agency · 120
  • Sponsor · 50
  • Box office · 30

1,000 / 1,000 assigned. Current allocation can change safely; sales attribution stays with the selling channel.

Sponsors, agencies, presales and the box office, on one event.

Choose the seats for each audience, then how they reach them: a private link through SeatLayer checkout, or through your own checkout with the SDK. Inviting named people rather than opening a channel? See invitations.

  • Sponsors & VIP

    Protect a named seat pool.

    Set aside exact sponsor or VIP seats, send a private link, and share a report for just those seats.

  • Agencies & partners

    Distribute inventory without a copy.

    Give a partner its own login to sell its seats, or send its buyers a private link. No copy of the event.

  • Presales

    Control access and price.

    Give a presale group its own seats by private link or through your own sign-in, with its own prices only where they differ.

  • Box office

    Sell from the same event.

    Staff sell at the counter while online buyers keep seeing live availability.

One released model

Use the same five controls for every audience.

  • Assign exact reserved inventory
  • Override only audience prices that differ
  • Authorize a buyer or staff route
  • Freeze sales attribution at booking
  • Share a one-channel report
  • Release unsold seats with version checks

How it works

From allocation to partner report.

These five capabilities form one allocation workflow, not five disconnected feature flags.

Choose access by trust level, not convenience alone.

Knowing a channel id never grants access. The route must carry authorization that matches the buyer or operator job.

Access methodBest forWhat it can exposeSecurity boundary
Scoped buyer sessionSigned-in buyers and integrated checkoutYour trusted server creates the browser session.One or more allowed channels, with the exact buyer scope your application chooses.Restrict by event, parent origin, allowed channels, and expiry. Keep account secrets server-side.
Hosted-access linkSponsors, invited groups, and lightweight partner distributionAvailable on Hosted Ticketing events; no buyer account handoff is required.One channel, optionally including public inventory, followed by SeatLayer checkout, Orders, tickets, and Door.A bearer URL with expiry and redemption limits. Anyone holding a valid link can use it; rotate or revoke when needed.
Partner accessRecurring agencies, sponsors, schools, and resellersThe partner accepts with its own SeatLayer account; your channel appears as a context in its workspace switcher.Only the assigned event and channel, plus organizer-enabled distribution, return, request, report, and CSV actions.A membership checked on every request, with a Viewer, Coordinator, or Partner manager role. The organizer controls permissions, release date, and can revoke a person, the assignment, or the whole partner organisation.
Staff surfaceBox office and event operationsAuthorized operators work inside a controlled surface.The inventory and actions allowed by the staff session.Use short-lived staff authorization and do not share an operator route as a buyer invitation.

Partner access

Partner access: their own account, your one channel.

An agency, sponsor, school, or reseller works the allocation you assign, using its own SeatLayer account, inside a partner context that shows nothing else of yours.

Invite once, revoke any time, never share credentialsPartner access, end to end
  1. 01 · AllocateAssign exact seatsto a private channel, e.g. “Sponsor guests” · v12
  2. 02 · Set up partner accessPartner org, email, rolepermissions: links · returns · requests · release date · access end
  3. 03 · Invitation emailSingle-use link, 7 daysbound to the invited email; no organizer credentials involved
  4. 04 · Sign inOwn SeatLayer accountthe usual email code; created on the spot if new
  5. 05 · BindEmail must matchmembership → account, checked on every request
  6. 06 · In controlAudit trail, revoke, releaseremove a person, the assignment, or the whole partner organisation
  7. 07 · Partner contextAppears in the switcherOverview · Allocations · Distribution · Reports · Team
  • Inventory never leaves the event.
  • The channel is the only thing the partner can reach.
  • A different account cannot accept, even with the link.

Invite once by email. The partner accepts with its own account, and your channel appears as a context in its workspace switcher.

One account, two contexts.

A partner keeps its own events and billing; the partner context carries only Overview, Allocations, Distribution, Reports, and Team. Pick a context to see the menu change.

Left menu
Organizer pages vs. partner pages
Data scope
Your inventory vs. one assigned channel
Role
Your org role vs. Viewer / Coordinator / Partner manager set by the organizer
Settings and billing
Yours only, never the organizer's
What stays the same
Account, sign-in, profile, appearance
Maya Patelmaya@northstar.example

Your workspaces

Partner access

  • Overview
  • Allocations
  • Distribution
  • Reports
  • Team · managers

Partner context · only what was assigned

Sponsor guests · 50 assigned

16 free · 34 sold · server-scoped

Authorization lives on the server. Each request re-checks the membership.

What a partner can see, and what it never sees.

The partner sees

  • Exact seats of its channel: label, section, category, status
  • Allocation now: assigned · free · held · booked
  • Sales attributed at booking: frozen, even if seats move later
  • Its own buyer links and team: create, revoke, invite, remove
  • Audit trail and CSV export: both sides see the same actions
  • Channel prices the organizer set

One event · one inventory

Friday Evening · 1,000 seats

  • Public sale820
  • Sponsor guests · assigned to Northstar50
  • Agency B · not visible to Northstar60
  • Box office · staff surface only70

Held and booked seats never move.

The partner never sees

  • Sibling channels: names, allocations, or sales of others
  • Unassigned inventory or event-wide totals derived from it
  • Buyer identities: names, booking references, active holds
  • The organizer's settings: billing, payments, API keys, webhooks
  • Other events and workspaces: only explicitly assigned channels
  • Any way to grow its own allocation

The boundary is enforced on the server on every request. Sibling channels, buyers, and your settings never enter a partner context.

RoleCan
ViewerSee the assigned allocation, exact seats, attributed sales; export the CSV.
CoordinatorViewer, plus the actions you enable: create and revoke buyer links inside your limits, return free seats against a reviewed version, request more inventory.
Partner managerCoordinator, plus invite and remove teammates and change their roles.
  • Release date: still-free seats return to Public sale automatically, audited.
  • Requests: allocate N free Public-sale seats straight from the partner’s request, or decline.
  • Revoke: a person, the assignment, or the whole partner organisation, immediately.
Read the partner access guide

During a live sale

Change a live allocation with version checks.

Move seats between audiences during a live sale. Seats already held or sold never move, and you see exactly what changed.

  1. Read and previewConfirm the current assignment version and the exact seats the audience will see.
  2. Apply against that versionIf someone changed it since you looked, nothing moves and you are told.
  3. Inspect every result bucketHeld or sold seats stay put, and you get a list of what moved and what was skipped.
Your server · atomic allocation change
applyAllocation({  channelId: "sponsor",  labels: ["A-10", "A-11", "A-12"],  assignmentVersion: 12})
  • Moved2
  • Skipped held1
  • New version13

A-10 and A-12 moved to the sponsor channel. A-11 is held by a buyer, so it stayed where it was.

Example only; see the API reference for exact fields.

Reporting

Where a seat is now, and who sold it, are kept apart.

So a partner’s sales report stays right even after you move their unsold seats elsewhere.

Allocation · now

Where is this seat assigned today?

Use current allocation to operate the on-sale event and decide which audience may reach unsold inventory.

  • May change after review
  • Held and booked seats are protected
  • One current channel per exact seat

Attribution · at booking

Which channel produced this sale?

Attribution freezes the selling channel when the seat is booked, so later allocation changes do not rewrite the sale.

  • Preserves historical channel result
  • Can differ from current allocation
  • Supports channel sell-through reporting

Why can sell-through exceed 100%?

125%sell-through

10 seats sold through the channel, attributed at booking. Current allocation: 8 seats.

If a channel sold ten seats and its current allocation later shrinks to eight, attribution still records the ten real sales. That is expected, not a duplicate booking.

Partner report · included

Useful one-channel visibility.

  • That channel's allocation and confirmed sales
  • Search, filters, and CSV export
  • Booked value only when you enable it
  • A revocable read-only bearer route

Partner report · excluded

A deliberate privacy boundary.

  • Buyer identities and active holds
  • Booking references
  • Sibling channels
  • Event-wide totals

Recurring partner? Give it Partner access instead of sharing organizer credentials. Its context preserves the same one-channel reporting boundary and adds only the distribution, return, and request actions you explicitly enable.

Read the reporting and privacy contract

What Sales Channels are for, and what they are not.

Use them for the jobs on the left; the ones on the right need a different tool.

Use Sales Channels today for

  • Exact reserved-seat allocations
  • Public, sponsor, agency, presale, group, and box-office audiences
  • Sparse audience-specific price overrides
  • Scoped sessions and limited bearer links
  • Versioned changes while sales are live
  • Role-based partner access and scoped reports

Do not model these as Sales Channels

  • Season-ticket renewal or shared season entitlements
  • First-class resale or seat upgrades/exchanges
  • True partial-GA capacity splits between channels
  • Partner-controlled pricing, arbitrary suballocations, or commission settlement
  • Buyer identity or CRM inside a shared report
  • A channel id used as authorization

Fixed multi-performance seat selection is separately released as Performance Groups. Renewable plans of 2 to 25 dates, seat rights and renewal offers belong to the separate Seasons API. Neither product turns a channel into authorization or a resale listing.

Capability source: SeatLayer’s sales-channel model, channel API, and reporting contract.

Pricing

Two ways to pay. Both start free.

The SDK is billed per sold seat and hosted ticketing per ticket. Same engine, same account, and no subscription for either.

SDK · the seat map in your product

Pay per sold seat.

$0
to go live
100
sold seats free every month
10¢ → 5¢
per sold seat after that
  • No subscription and no monthly minimum
  • Credits you buy never expire
  • Holds and unsold seats are free
  • No SeatLayer badge for buyers, on any plan
Hosted ticketing · sell on your website

Pay per ticket.

25
first tickets free
$0.50
per ticket after that
$0
a month, no subscription
  • Buyers pay you directly, through your own payment account
  • Stripe, PayPal, Square and 11 more gateways
  • Sell online, at the box office and at the door
  • Embed on WordPress, Wix, Webflow, Squarespace, Shopify or any page

Sales channels across SeatLayer

Sales channel questions

16 questions

A ticket sales channel is a named allocation and attribution lane inside one event. It can represent public sales, a sponsor, an agency, a presale, or box office. A channel does not create a second copy of the chart or inventory.

Assign the exact seats to a sponsor or partner channel inside the existing event. The seats remain in the event's authoritative inventory, but only authorized buyer or staff surfaces can sell from that allocation.

Yes. A channel can apply sparse audience-specific price overrides. Seats without an override keep the event's base price, so the pricing model stays authoritative rather than becoming a copied price table.

An authenticated buyer session is created by your trusted server and can expose one or more allowed channels for a buyer flow. A hosted-access link is a redeemable bearer URL for one channel, with expiry, redemption, quantity, and session limits. Hosted links require a Hosted Ticketing event and open SeatLayer checkout. Anyone who possesses a valid bearer link can use it, so it must be handled like a ticket or invitation.

If you set a release date on the assignment, whatever is still free in that channel returns to Public sale automatically at that moment, through the same versioned move an organizer would make by hand, and both sides see it in the audit trail. Held, booked, and blocked seats never move.

Yes. Allocation changes use a known assignment version. If that version is stale, the request fails and moves nothing. Held or booked seats are not moved, and the result reports which requested seats moved or were skipped.

Allocation reports where inventory is assigned now. Attribution records the channel from which a seat was sold and is frozen at booking. A seat can therefore move later without rewriting the original selling-channel result.

A partner report is read-only and restricted to one channel. It can show that channel's allocation and sales, with booked value optional. It excludes buyer identities, active holds, booking references, sibling channels, and event-wide totals.

They can. On a Hosted Ticketing event, a hosted-access link enters SeatLayer checkout and the SeatLayer Order, ticket, and Door lifecycle. In SDK mode, use a trusted-server-created buyer session: SeatLayer scopes inventory, holds, booking, and attribution, while your platform owns checkout, payment, Orders, tickets, refunds, and fulfilment.

Yes. An AI assistant connected to the SeatLayer MCP can plan a channel, move seats into it, and create buyer and report links. Each change is shown to you as a plan first, and nothing changes until you say yes.

An organizer grants Partner access on a private channel: it names the partner organisation, invites one person by email, and picks a Viewer, Coordinator, or Partner manager role with assignment-specific permissions. The partner accepts with its own SeatLayer account. There is no second login and no separate portal, and the channel appears as a partner context in its workspace switcher, next to its own workspaces. A Partner manager can invite teammates. The organizer can remove a person, the assignment, or the whole partner organisation at any time.

Yes. Partner access is a membership, not an account type. The same account keeps its own workspaces, events, floor plans, and billing, and switches into a partner context only to work the inventory another organizer assigned to it.

No. A channel id is a label, not authorization. Private inventory requires an authorized staff surface, a trusted-server-created buyer session, a Partner access membership, or a valid hosted-access link.

An exact seat has one current channel assignment. An authorized buyer session may expose multiple channels, but the seat itself is not duplicated across them.

Not in the current release. Sales-channel allocation is for exact reserved inventory; true partial-GA capacity splits between channels are outside the released contract.

No. Creating allocations, sessions, access links, and reports does not consume sold-seat credits. One credit is consumed when one seat is confirmed sold.

Didn't find your answer?

Bring one audience allocation into test mode.

Start with one sponsor, partner, presale, or box-office lane. Verify its seats, price, buyer scope, allocation change, and report before you expand the model.