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.

OperationPurpose
POST /api/partner/workspacesCreate or resume the first self-serve organiser workspace for a verified account.
GET /api/partner/studio/shellEligible events for partner navigation.
POST /api/partner/studio/organizationSelect an organisation already available to the actor.
GET /api/partner/eventsRole and event summaries.
POST /api/partner/eventsCreate an event.
PATCH /api/partner/events/renameRename an authorised event.
POST /api/partner/events/duplicateDuplicate an authorised event.
DELETE /api/partner/eventsDelete an event only when its blockers permit it.
GET /api/partner/events/resolveResolve a slug or id inside live membership scope.
GET /api/partner/events/overviewEvent status, counts, and scans by staff member.
GET /api/partner/events/detailsEditable event details and categories.
PATCH /api/partner/events/detailsSave bounded event details, including up to 60 ordered schedule slots.
PATCH /api/partner/events/statusApply a valid draft/published/closed transition.
GET /api/partner/events/ticketsTicket inventory and sold count.
POST /api/partner/events/ticketsAdd a ticket type.
PATCH /api/partner/events/ticketsUpdate eligible ticket inventory.
DELETE /api/partner/events/ticketsDelete an eligible unsold ticket type.
GET /api/partner/events/workshopsWorkshops for an authorised event.
POST /api/partner/events/workshopsAdd a bounded workshop.
GET /api/partner/teamCurrent members and live invitations.
POST /api/partner/team/invitationsInvite admin, staff, or crew by email, optionally with a zoneIds array.
DELETE /api/partner/team/invitationsRevoke a live invitation.
DELETE /api/partner/team/membersRemove a member without violating last-owner rules.
GET /api/partner/invitations/previewActor-aware signed invitation preview.
POST /api/partner/invitations/acceptAccept a named-email invitation.
GET /api/partner/invitations/mineList pending, unexpired crew invitations for the verified signed-in email.
POST /api/partner/invitations/respondAccept 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)

OperationBehaviour
GET /api/crew/opportunitiesBounded public-event opportunities, literal search, optional category UUID, and cursor.
GET /api/crew/opportunities/detailPublic, published, accepting opportunity only.
POST /api/crew/applicationsVerified applicant submits interest and separate optional future-contact consent.
GET /api/crew/applications/mineCurrent account's paginated application status.
POST /api/crew/applications/withdrawWithdraw the current account's pending application.
GET /api/partner/crew/opportunityRead current organiser-owned configuration.
POST /api/partner/crew/opportunitySave organiser-owned recruitment configuration.
GET /api/partner/crew/applicationsPaginated event applicants for authorised organisers.
POST /api/partner/crew/applications/actionApprove with selected zones or decline. Approval issues an invitation, not scanner authority.
POST /api/partner/crew/join-codesIssue a hashed, single-use code expiring within 48 hours.
POST /api/crew/join-codes/redeemVerified recipient consumes a code into an invitation awaiting acceptance.
POST /api/partner/crew/join-codes/revokeRevoke 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.

On this page