Partner and studio
Organiser navigation, events, ticket inventory, workshops, and teams.
Every protected request resolves a live owner, admin, or staff membership. Posted organisation or event identifiers never create authority.
| Operation | Purpose |
|---|---|
POST /api/partner/workspaces | Create or resume the first self-serve organiser workspace for a verified account. |
GET /api/partner/studio/shell | Eligible events for partner navigation. |
POST /api/partner/studio/organization | Select an organisation already available to the actor. |
GET /api/partner/events | Role and event summaries. |
POST /api/partner/events | Create an event. |
PATCH /api/partner/events/rename | Rename an authorised event. |
POST /api/partner/events/duplicate | Duplicate an authorised event. |
DELETE /api/partner/events | Delete an event only when its blockers permit it. |
GET /api/partner/events/resolve | Resolve a slug or id inside live membership scope. |
GET /api/partner/events/overview | Event status, counts, and scans by staff member. |
GET /api/partner/events/details | Editable event details and categories. |
PATCH /api/partner/events/details | Save bounded event details, including up to 60 ordered schedule slots. |
PATCH /api/partner/events/status | Apply a valid draft/published/closed transition. |
GET /api/partner/events/tickets | Ticket inventory and sold count. |
POST /api/partner/events/tickets | Add a ticket type. |
PATCH /api/partner/events/tickets | Update eligible ticket inventory. |
DELETE /api/partner/events/tickets | Delete an eligible unsold ticket type. |
GET /api/partner/events/workshops | Workshops for an authorised event. |
POST /api/partner/events/workshops | Add a bounded workshop. |
GET /api/partner/team | Current members and live invitations. |
POST /api/partner/team/invitations | Invite admin, staff, or crew by email, optionally with a zoneIds array. |
DELETE /api/partner/team/invitations | Revoke a live invitation. |
DELETE /api/partner/team/members | Remove a member without violating last-owner rules. |
GET /api/partner/invitations/preview | Actor-aware signed invitation preview. |
POST /api/partner/invitations/accept | Accept a named-email invitation. |
GET /api/partner/invitations/mine | List pending, unexpired crew invitations for the verified signed-in email. |
POST /api/partner/invitations/respond | Accept or decline a pending crew invitation by id. |
GET /api/studio/stats/{id} | Legacy live registered, distinct check-in, and ticket-revenue counts. |
Missing authentication returns 401; an actor outside the event or organisation
scope returns 403, or 404 where existence itself is tenant-sensitive.
Mutations require an exact configured Origin.
Registration limits
From API 1.3.0, an event capacity or ticket-type quantity of null means unlimited. A positive integer is a finite limit. Do not treat null as zero. Event and ticket-type limits are independent, and both must be unlimited for unrestricted exhibition registration. Workshop creation still requires a positive finite capacity. This requires migration 0006 and deployment of the matching API and clients.
Ticket-type create/update accepts optional publicRegistration. New types default to public; omission on update preserves the current setting. False types remain visible to authorised organisers but are excluded from public ticket listings and self-registration. This setting alone does not verify external payment or issue a delegate ticket.
GET /api/events/organising is the attendee-facing organiser switcher. It
returns only events in the actor's current live organiser scope; Studio routes
remain the place to edit details, schedules, tickets and teams.
Work event cards (API 2.3.0)
GET /api/partner/invitations/mine includes optional nullable venue and
coverImageUrl on each invitation event. The inbox remains restricted to the
verified invited email and pending, unexpired invitations. Accepting or rejecting
an invitation affects the entire invitation, including every event it lists.
Work invitation areas (API 2.4.0)
GET /api/partner/invitations/mine may include an optional zones array on
each invitation event:
{
"zones": [
{ "id": "zone-uuid", "name": "Main entrance", "kind": "entrance" }
]
}kind is one of entrance, breakout, or vip. The areas are limited to the
invitation and event assigned to the verified invited email. They contain
display information only: no checkpoint or signing codes are returned, and a
pending invitation preview does not grant scanner authority. The server checks
the live assignment and admission rules when an accepted crew member scans.
Work details in the web and Expo clients show the assigned areas and access
guidance before ticket or scanner actions. Event dates are event schedules, not
shift times. A crew member sees Start scanning only after accepting the
invitation and loading the current assignment; it remains unavailable offline.
Crew recruitment (3.0 target)
| Operation | Behaviour |
|---|---|
GET /api/crew/opportunities | Bounded public-event opportunities, literal search, optional category UUID, and cursor. |
GET /api/crew/opportunities/detail | Public, published, accepting opportunity only. |
POST /api/crew/applications | Verified applicant submits interest and separate optional future-contact consent. |
GET /api/crew/applications/mine | Current account's paginated application status. |
POST /api/crew/applications/withdraw | Withdraw the current account's pending application. |
GET /api/partner/crew/opportunity | Read current organiser-owned configuration. |
POST /api/partner/crew/opportunity | Save organiser-owned recruitment configuration. |
GET /api/partner/crew/applications | Paginated event applicants for authorised organisers. |
POST /api/partner/crew/applications/action | Approve with selected zones or decline. Approval issues an invitation, not scanner authority. |
POST /api/partner/crew/join-codes | Issue a hashed, single-use code expiring within 48 hours. |
POST /api/crew/join-codes/redeem | Verified recipient consumes a code into an invitation awaiting acceptance. |
POST /api/partner/crew/join-codes/revoke | Revoke an unused organiser-owned code. |
Invitation acceptance remains the authority boundary. Staff/exhibitor admission passes do not confer crew authority. Private events are excluded from public discovery, but organisers may explicitly distribute invitation codes for them.

