Exhibition operations

Location-scoped crew access, VIP admission and attendance reporting.

These additive endpoints are available in API 2.2.0. Availability requires the exhibition migrations and a verified deployment; local implementation does not establish production availability.

OperationPurpose
GET /api/exhibition/operationsOrganiser's event locations, pass names, assignments, invitation states and crew counts.
POST /api/exhibition/invitations/actionResend a pending crew invitation or cancel it for this event.
POST /api/exhibition/zonesCreate an entrance, breakout or VIP location.
POST /api/exhibition/assignmentsAssign a current organisation member to a location.
POST /api/exhibition/assignments/replaceReplace one crew member's assigned locations with the supplied zoneIds array.
POST /api/exhibition/admissionsExplicitly permit a confirmed event registration at a VIP location.
DELETE /api/exhibition/assignmentsRevoke a crew location assignment.
DELETE /api/exhibition/admissionsRevoke a VIP visitor permission.
GET /api/exhibition/crewRead the signed-in crew member's assigned locations.
POST /api/exhibition/scanValidate and save a location admission.
POST /api/exhibition/checkpointResolve a checkpoint code to its event location.
GET /api/exhibition/pass-configurationRead organiser pass questions and zone access configuration.
POST /api/exhibition/pass-configurationSave or publish pass questions and zoneIds access mapping.
GET /api/exhibition/form-analyticsRead aggregate pass-question and nationality responses.

Organiser operations require current owner, admin or staff membership. Crew scanning additionally requires an active assignment to the selected location. Membership, registration and VIP permission are checked on the server; a QR code or a location label alone is not authority.

The scan outcome distinguishes accepted, already and denied. A repeat of the same ticket at the same location on the same Malaysian calendar day does not increase successful admissions. Only entrance scans contribute to the legacy event check-in records used by the MATRADE draft; breakout and VIP visits remain separate.

This location scanner requires a live connection. Existing legacy offline queues remain separate and must be synchronised before changing devices or origins. The online location endpoint does not certify a previously downloaded offline permission list.

POST /api/partner/team/invitations accepts optional zoneIds (and retains the legacy singular zoneId) for a crew invitation. Each location must belong to the inviter's organisation. Acceptance binds the pending locations to the email-verified member once; replaying an accepted invitation must not restore revoked access.

Operations includes event-linked crew invitations with assigned zoneIds and expiry. Declined, cancelled and expired invitations remain visible for organiser history; accepted crew appear in the roster. Invitation tokens are never returned. Resend reuses the existing token and reports an actionable error when the mail provider does not accept the message; it does not claim inbox delivery. Cancellation expires the invitation while retaining its audit history.

Pass forms support the eight published field types in the contracts, with required answers validated again at registration. Form analytics are aggregate counts; they do not expose another visitor's answers.

See the generated OpenAPI document for exact request and response schemas and the event-day guide.

Work assignment cards (API 2.3.0)

GET /api/exhibition/crew includes optional nullable venue and coverImageUrl on assigned events for Work cards and details. Existing membership and assignment checks still determine access; a displayed card does not grant scanner permission.

Work areas in assignment lists (API 2.4.0)

GET /api/exhibition/crew adds an optional zones array to each event summary. Each area contains id, name, kind and eventId, drawn only from the actor’s live, non-revoked assignments. Work can search area names without fetching every assignment separately. The existing top-level zones for a selected event remain unchanged; no checkpoint codes are included. Scanning still rechecks current access.

Personal Work scan activity (API 2.5.0)

GET /api/exhibition/crew?event=<id-or-slug> adds optional nullable scanStats for the signed-in crew member. A current membership and active area assignment in that event are required. No user ID is accepted from the caller. Without a selected, accessible event, scanStats is null; older servers may omit it.

accepted counts saved area admissions, todayAccepted counts those on today's Malaysian calendar date, and uniquePeople counts distinct attendees across those admissions, including multiple passes or areas for the same person only once. lastScannedAt is nullable; asOf identifies when the snapshot was requested. zones contains each visited area's zoneId, zoneName, accepted and todayAccepted. With no accepted scans, totals are zero and zones is empty.

Repeat and denied attempts do not increase these counts. Legacy offline check-ins remain separate. These personal totals are not the organiser's MATRADE visitor report. Responses are private and not cached; Work can refresh them when the crew member returns from scanning or requests a refresh.

API 3.0 completion changes — implementation pending production rollout

  • GET /api/exhibition/attendees: literal name/email/company search (q, maximum 120 characters), 20-row UUID cursor pagination. Operations now supplies at most 20 initial attendee options.
  • GET /api/exhibition/form-responses: individual immutable registration answers, optional pass/search filters and 25-row cursor pagination.
  • GET /api/exhibition/form-responses/export: streams text/csv in bounded batches. Spreadsheet formulas are escaped. It requires organiser authority, like the response table.
  • GET /api/exhibition/summary: unique event attendance, separately labelled zone visits, crew scans and overlapping active-pass participant categories. generatedAt identifies freshness.
  • GET and POST /api/exhibition/pass-offers, plus POST /api/exhibition/pass-offers/action: recipient-bound offers for restricted passes. Creation/resend distinguishes provider acceptance (sent) from not_sent; neither asserts inbox delivery. Offers expire after seven days. Revoking an unclaimed offer does not revoke an issued pass.

Booking, published-form reading and registration accept optional offerToken. The API checks the verified recipient email, event, pass, expiry and revocation before exposing a restricted form. Registration validates the current form version and consent and atomically consumes the offer. Applications and pass offers do not create crew authority.

Online QR scans aggregate active passes for one person in one event. Old printed codes remain identity anchors even after one pass is revoked; they confer no access without another eligible active pass. VIP zones require explicit organiser grants. Event attendance counts one person once; per-zone/per-day visits remain separate. Participant-category counts may overlap and must not be summed as attendance.

Scan and registration request allowances use verified user identities to support shared venue Wi-Fi. Anonymous and other endpoints retain an IP allowance. Throttling returns HTTP 429, not an internal server error.

Crew briefing (3.0 target)

  • GET /api/exhibition/briefing reads the event briefing for an authorised organiser.
  • POST /api/exhibition/briefing saves reporting time, shift, instructions and contact.
  • GET /api/work/briefing returns briefing details only to a current assigned crew member. Applications and pending invitations do not grant this access.

GET /api/exhibition/pass-offers lists recipient-bound offers for the organiser-owned event using a bounded cursor.

Event analytics (API 4.11.0)

GET /api/exhibition/summary keeps every existing field and adds three optional additions for the Studio Analytics page. Older servers omit them, and older clients can ignore them.

  • day (input, YYYY-MM-DD): a Kuala Lumpur calendar day. When present, totalUniqueAttendance, arrivals, zones and crew count only that day. An impossible date such as 2026-02-30 is rejected with 400. Omit it for every day. participantCategories is never filtered: it counts confirmed active passes, not admissions.
  • arrivals: each person's first admission on each KL day (entrance check-ins and zone visits, with the same identity rules as totalUniqueAttendance), grouped into 30-minute KL buckets and ordered oldest first. bucketStart is the bucket's start as an ISO instant and count is a positive integer; buckets with no arrivals are omitted. With day, the counts sum to totalUniqueAttendance. Without it, a person who returns on a second day is counted once per day, so the sum can exceed totalUniqueAttendance.
  • crew[].crewEmail: the crew member's sign-in email, or null, so same-named crew can be told apart. Only an organiser can read this endpoint.

Event People (API 4.4.0)

GET /api/exhibition/people returns current event role entries for an authorised host manager or a designated manager in an accepted organiser appointment. Crew and exhibitor membership alone do not authorise this endpoint. All authority is checked against live memberships and the selected event on every request.

Pass event as a UUID or slug. Optional q searches display names and team names (maximum 120 characters; %, _ and backslash are literal). Optional role is one of organiser, event-organiser, event-crew, exhibitor, exhibitor-crew or attendee. Reuse nextCursor with the same filters for the next 25 entries. Rows are ordered by a stable role/team/person identifier, not alphabetically.

The response contains event identity, display name, role and team. It excludes email addresses, telephone numbers and private exhibitor lead notes. A person may appear in several role/team entries; this is not a unique-person count or an attendance report. Confirmed registration records are labelled registered attendees, never inferred to be staff assignments or MATRADE visitor categories. Attached live companies remain visible while CRM is disabled; directory participation does not grant scanning or lead access. Revoked assignments, removed members, deleted companies and cancelled registrations are excluded.

Responses use Cache-Control: private, no-store. The Studio People page links to existing crew, exhibitor, analytics and trade fair report workflows. No database migration or change to scanner permissions is required.

On this page