Skip to main content

Data model overview

A high-level map of the entities you'll encounter as you query and mutate the External API. Read this first — every other concept page drills into one part of this graph.

The shape​

The authenticated organization (your board) is the root of everything. From there, two major branches:

  • Members: the people on the board — ClaimedMember (linked to a Unioo platform user) and UnclaimedMember (invited but not yet claimed). Both implement the Member interface.
  • Events: ticketed events your board hosts. Each event carries dates, an optional location, ticket specifications (the SKUs people buy), purchased tickets, and inspectors. Once tickets are sold, ticket holders show up via a separate query.
Organization ─┬─ Members ─┬─ ClaimedMember (UserId)
              │           └─ UnclaimedMember (InvitationDate)
              │
              └─ Events ──┬─ EventDate[]                       (start/end slots)
                          ├─ EventLocation[]                   (venue or "no location")
                          ├─ TicketSpecification[] ─┬─ EventTicket[]   (sold tickets)
                          │                         └─ EventDates[]
                          ├─ TicketInspector[]      ─┬─ ExternalTicketInspector
                          │                          └─ BoardMemberTicketInspector
                          └─ EventTicketHolder[]    (queried via getTicketHolders)
                                  └─ BuyOrder[]     (state, charge session, comments)

Organization scoping​

Every query is filtered to your organization automatically — derived from the organizationId claim on your JWT. You can't query another board's data, and you don't need to pass an organizationId argument anywhere. The organization query returns the single record for your own board.

Lifecycles​

  • Events progress: draft (default) → published (isActive: true) → completed (isCompleted: true). Most edits are blocked once an event is published, and almost everything is blocked once it's completed. See the Events concept for which mutations are allowed in each state.
  • Tickets are owned by BuyOrder rows whose state is Pending, Paid, or Expired. Refunds are tracked on the EventTicket itself via IsRefunded / IsRefundInProgress.

Where to go next​

  • Organization — your board's contact and branding fields.
  • Members — claimed and unclaimed members, their statuses.
  • Events — events, dates, locations, and the lifecycle that gates everything.
  • Tickets — specifications, ticket holders, buy orders, and inspectors.