Exhibitor CRM

Consent, exhibitor assignments, and event lead follow-up.

The exhibitor CRM records booth follow-up leads for an event. It is separate from admission: scanning a visitor QR here never checks the visitor in, issues a pass, or grants scanner authority.

Every route requires a valid Better Auth session. The API rechecks the current company membership, company role, event assignment, and event scope on every request. UUIDs from the browser, a selected workspace, or a hidden control do not grant authority. Responses are tenant and event scoped and are served with Cache-Control: private, no-store; contact data must not enter a shared cache.

MethodPathPurpose
GET/api/exhibitors/consent?eventId={uuid}Read the signed-in attendee's consent and contact fields for one event.
POST/api/exhibitors/consentGrant or withdraw event-specific sharing consent.

The attendee chooses whether the current consent wording and version allow exhibitors to receive their name, email, company, job title, and phone number when staff scan their event QR. A withdrawal blocks subsequent server disclosure and new scans. It cannot retract contact data that an exhibitor already downloaded, including a CSV export.

The consent routes are GET /api/exhibitors/consent and POST /api/exhibitors/consent.

Company and event workspace

MethodPathPurpose
GET/api/exhibitors/workRead the signed-in user's bounded event and company work overview; optionally filter by eventId.
GET/api/exhibitors/companiesList companies the user owns or belongs to.
POST/api/exhibitors/companiesCreate a company or update an owned company profile.
GET/api/exhibitors/invitationsList invitations visible to the user, company, or event scope.
POST/api/exhibitors/invitationsHost-owner action to invite a company to an event, optionally with its booth crew (API 4.12.0).
POST/api/exhibitors/team/inviteInvite a manager or staff member to a company event assignment.
POST/api/exhibitors/invitations/respondAccept, decline, or revoke an invitation tied to the current identity.
GET/api/exhibitors/eventList active exhibitor assignments for an event.
POST/api/exhibitors/eventConfigure one company's booth and CRM assignment for an event.
GET/api/exhibitors/event/teamOrganiser read of an assigned company's on-site team (API 4.10.0).
POST/api/exhibitors/event/team/inviteOrganiser invites a booth manager or crew member for an assigned company (API 4.10.0).
POST/api/exhibitors/event/invitations/crewOrganiser adds booth crew to a pending company invitation (API 4.12.0).
GET/api/exhibitors/teamList team members and event assignment state.
POST/api/exhibitors/teamChange role or event assignment for a team member.

Company owners manage company profiles, team membership, and company invitations. Owners and managers may read their event team; only owners receive team-management capability. Host event operations use live host membership or an accepted, designated appointed-organiser membership. Staff can use an exhibitor event only when they hold a live, non-revoked assignment. Host and exhibitor company records are isolated by both event and company; membership in one does not expose another.

The workspace routes are GET /api/exhibitors/work, GET /api/exhibitors/companies, POST /api/exhibitors/companies, GET /api/exhibitors/invitations, POST /api/exhibitors/invitations, POST /api/exhibitors/team/invite, POST /api/exhibitors/invitations/respond, GET /api/exhibitors/event, POST /api/exhibitors/event, GET /api/exhibitors/event/team, POST /api/exhibitors/event/team/invite, POST /api/exhibitors/event/invitations/crew, GET /api/exhibitors/team, and POST /api/exhibitors/team.

List responses expose nextCursor and use bounded cursor pagination. Standard CRM lists return 25 rows per page. The work overview is a bounded overview with its own service page-size contract and does not promise the 25-row size. Pass eventId={uuid} to limit the work overview to one authorised event. The server still verifies the current identity, company membership, and assignment; the filter does not grant access to an event.

Organiser crew invitations (API 4.10.0)

An event organiser can invite crew for a company that has an active assignment to that event, without being a member of the company.

  • POST /api/exhibitors/event/team/invite takes eventId, merchantId, email and an optional role (staff by default, or manager). It requires live event authority: host membership as owner, admin or staff, or a designated member of an accepted organiser appointment. Events outside that authority, companies not assigned to the event, and inactive assignments are refused. It creates the same invitation and email as the company owner's (delivery is sent or unavailable), with the organiser as inviter, so the recipient joins on sign-in. It returns 409 while an invitation to that email is pending. Accepting the invitation re-checks that the organiser still holds that authority; withdrawing the organiser's access or appointment first makes it unavailable. The company owner's POST /api/exhibitors/team/invite is unchanged.
  • GET /api/exhibitors/event/team?eventId={uuid}&merchantId={uuid} lists the company's owner, joined and revoked crew, and pending, expired or revoked invitations for that event, with email, display name (null until the person has joined), role, status (joined, invited, expired or revoked) and invitation expiry. It returns at most 200 rows and never returns lead data.

Inviting a company together with its crew (API 4.12.0)

An organiser can invite the booth crew while the company's own invitation is still waiting for its manager, so the whole team is in place when the manager signs in.

  • POST /api/exhibitors/invitations accepts an optional crew: up to 20 email addresses, invited as staff. The company invitation and its crew invitations are saved in one transaction. The response keeps id and delivery and adds crew, one entry per address with an outcome of invited (with the crew invitation id and its own delivery), already-invited or manager-email (the address is the manager's own, so no crew invitation is made).
  • POST /api/exhibitors/event/invitations/crew takes invitationId (the company invitation), emails (1 to 20) and an optional role (staff by default, or manager), and returns results in the same shape. It adds crew to a company invitation that is still pending, which is how crew are added to invitations sent before 4.12.0. It requires live event authority over that invitation's own event and returns 404 for an invitation of another event, and 409 once the company invitation has been accepted, declined, revoked or has expired; from then on use POST /api/exhibitors/event/team/invite.
  • Each crew member is emailed straight away. Their invitation is a team invitation with no company yet. It cannot be accepted, and accepting it returns 409 ("Waiting for the company to join"), but it is not consumed. In GET /api/exhibitors/invitations it carries awaitingCompany: true.
  • When the company manager accepts, every still-pending crew invitation is attached to the company in the same transaction and becomes an ordinary team invitation, valid for at least another seven days. The crew are then added on their next sign-in to Work, exactly as for any team invitation. The manager's own address and an address that already has a pending invitation to the company are withdrawn instead of attached.
  • If the company declines, or the organiser revokes the company invitation with POST /api/exhibitors/invitations/respond, its pending crew invitations are revoked with it. An organiser can revoke a single crew invitation the same way, using its invitation id.
  • GET /api/exhibitors/invitations?eventId={uuid} (organiser) returns each company invitation's crew: id, email, role, status and expiresAt for every crew invitation made with it, including those that have since been attached and answered.
  • One address can hold one pending pre-invitation per event. Inviting the same address again before the first is answered or expired reports already-invited.

GET /api/exhibitors/event also returns an optional summary with event-wide activeCompanies, pendingInvitations, uniqueLeads and leadsToday (Malaysia time), independent of search and cursor, and each company may include managerEmail (the company owner's account email) and crewCount (crew currently assigned to the event, excluding the owner). All of these are absent from API builds before 4.10.0.

Survey before CSV download (API 6.0.0)

The exhibitor survey is event-scoped and separate from lead capture. The owner or manager answers once for the company; a later submission updates that company's response while the survey is open. Existing responses remain valid when the organiser changes questions or moves the survey to draft or closed.

GET /api/exhibitors/leads/export requires both live company owner/manager authority and a saved exhibitor response for the same company and event. Without that response, the endpoint returns 403 before any CSV content or attachment headers:

{
  "code": "exhibitor_survey_required",
  "message": "Complete the exhibitor survey before downloading leads.",
  "surveyStatus": "open"
}

surveyStatus is open, closed, or unavailable (missing or draft). Only an open survey accepts new answers. Existing responses count regardless of status or later question edits, so completed companies can still download. Companies without a response must ask the organiser to open/reopen a missing, draft or closed survey.

GET /api/exhibitors/leads remains accessible without a response. Owners/managers receive optional exportSurvey: { completed, status }; staff do not. canExport is true only when the caller has export authority and the company has answered. Scanning, CRM viewing and lead updates remain available under their existing role and visitor-consent rules. Organiser exports of survey responses are unchanged.

Survey submission and organiser survey-response exports are documented in the Surveys API.

Visitor survey insights (API 6.2.0)

MethodPathPurpose
GET/api/exhibitors/insightsPer-question totals of the event's visitor survey.

Call GET /api/exhibitors/insights with eventId and merchantId. Any assigned owner, manager or staff member may read it. The totals cover every visitor who answered the event's visitor survey, not only this company's leads, and no individual answer is returned.

  • Below minimumResponses (currently 10) the response carries responseCount and an empty questions list.
  • Each question uses the same summary shape as organiser survey results: count, distribution for ratings and choices, average for ratings and numbers, and total for numbers.
  • Open-answer questions are left out, and min and max are always null, because one unusual answer could identify one visitor.

Lead capture and follow-up

MethodPathPurpose
GET/api/exhibitors/leadsList consent-backed leads for one company and event.
POST/api/exhibitors/leads/scanScan a visitor QR and record a booth follow-up interaction.
POST/api/exhibitors/leadsUpdate lead status, notes, follow-up date, or assignment.
GET/api/exhibitors/leads/exportDownload a private CSV of the selected event's leads.

Lead scans are CRM activity, not admission. A scan succeeds only for assigned exhibitor staff with an active CRM assignment and a visitor who granted the current event consent. The lead remains isolated to the selected company and event. Owners and managers can export and manage the company's leads. Staff can read and update only leads they captured or that are assigned to them; response capability flags are authoritative for the current role.

Who captured a lead (API 4.7.0)

Each lead in GET /api/exhibitors/leads may include an optional capturedByName: the display name of the crew member who first scanned the visitor (profile name, then account name, then the email's local part). It is absent from API builds before 4.7.0, so clients should treat a missing value as unknown. capturedBy is unchanged.

CSV responses are private and marked no-store. Withdrawing consent prevents new server disclosure, but the API cannot recall a file or contact data already downloaded by an exhibitor.

The lead routes are GET /api/exhibitors/leads, POST /api/exhibitors/leads/scan, POST /api/exhibitors/leads, and GET /api/exhibitors/leads/export.

On this page