Skip to content

More

Aggregators

Reference only. Not a decision unless cited in product/DECISIONS.md.

Aggregators

Multi-venue platforms integrate with AXYN through a white-glove engagement for commercial onboarding and deep multi-tenant runbooks. The API surface they build on is the same sold contracts first-party apps dogfood.

Two sale types (do not conflate)

Direct-to-venue: the venue buys AXYN and uses our admin (admin.axyn.events). One commercial sale ≈ one venue.

Aggregator: a platform partner sells AXYN-powered ticketing as their product to their venue customers. They host their admin UI on our APIs (Sold Partner + Sold Organizer Admin). AXYN still takes the same per-ticket fee path, plus a monthly white-label fee. One commercial sale ≈ hundreds–thousands of venues.

Decision record: product/axyn/decisions/ADR-AXYN-0010-three-api-contracts.md. Commercial floors (MAG/MRR, partner fee on top with no AXYN cap): product/axyn/prds/PRD-aggregator-contract.md.

Who this is for

Teams that sell many organizers or venues under one product surface (our infrastructure, their surface).

What is different from a single venue

  • Multi-tenant catalog and key topology (product intent; see honesty section)
  • Opt-in channel distribution (planned): an organizer lists an event once on AXYN and turns your channel on per event. You publish acceptance rules, set your own partner fee (organizer-absorbed by default, so buyers see the same all-in price everywhere), and receive aggregate demand data (no buyer PII, with a minimum group size so no buyer can be singled out) on the events in your channel. All channels sell from one inventory ledger. Product doc: product/axyn/prds/PRD-channel-distribution.md.
  • Custom branding across many producers
  • Own organizer admin UI calling Sold Organizer Admin (/v1/tenants/...) instead of requiring hosted axyn-admin as the only staff surface
  • Volume, rate limits, and webhook fan-out
  • Commercial SLAs and implementation services (MAG/MRR, white-glove)

What you can use from public docs

  1. Sold Partner API — OpenAPI, auth headers, error envelope, and @axyn/web-sdk primitives. Start with Authentication and API reference.
  2. Sold Organizer Admin API — tenant-staff routes under /v1/tenants/:tenantId/... (staff JWT / dual-auth). Same contract axyn-admin dogfoods. Full OpenAPI coverage is completing under milestone M46t; Connect and tenant create are already in the catalog.

Platform ops (/v1/admin/*, /v1/internal/*) are not partner APIs.

Honesty: built vs not yet

Built / usable as substrate today

  • Per-tenant API keys, catalog, checkout, Connect MoR (one tenant at a time)
  • Wholesale / affiliate fee channel (fee_channel, affiliate_relationship)
  • tenants.kind includes aggregator (self-serve signup still creates direct)
  • White-label buyer/headless packaging for a single tenant (e.g. Rotation / ENG-431) — not multi-tenant key topology
  • First-party axyn-admin dogfood of Organizer Admin paths

Not built yet (white-glove / separate milestones)

  • One partner API key that spans hundreds of venue tenants
  • Partner portal fleet UI and MAG/MRR invoicing automation
  • Full public OpenAPI for all Organizer Admin routes (M46t / ENG-564)

Runtime isolation stays one API key → one tenants row. Scaling an aggregator deal means many child tenants (and affiliate links), operated from the partner’s own surface via sold APIs — not a single shared key for the fleet.

What these docs will not do

There is no public end-to-end "launch your aggregator" commercial tutorial. Deep runbooks and deal structuring stay white-glove during partnership engagement. That is separate from documenting the Organizer Admin API.

How to start

Email partners@axyn.events (or your AXYN contact) to begin white-glove onboarding. Marketing overview: axyn.events/partners.

Next