Ticket inspectors

A ticket inspector is someone authorized to validate (scan) tickets at the event. Two flavors:

• External — a one-off person not on the board. You provide their name, email, phoneNumber directly.
• Board member — a board administrator. You provide a boardMemberId; the server pulls name/email/phone from the linked user.

Both implement the TicketInspector interface (id, name, email, phoneNumber). See the Tickets concept for context — note that boardMemberId refers to an internal Administrator record, not a Member returned by members.

All mutations on this page require a JWT — get one from the homepage first. The API key needs the events:write scope. Allowed while draft or published; only blocked once the event is completed.

Add an external inspector

Use this when you have the inspector's contact details directly.

mutation addExternalInspector($input: AddTicketInspectorInput!) {
addTicketInspector(input: $input) {
  ticketInspector {
    __typename
    id
    name
    email
    phoneNumber
  }
}
}

Validation when type: External:

• name, email, phoneNumber are all required.

Add a board-member inspector

Use this when the inspector is one of the board's administrators. Pass type: BoardMember and boardMemberId — name, email, phoneNumber in the input are ignored (the server reads them from the administrator's user record).

mutation addBoardMemberInspector($input: AddTicketInspectorInput!) {
addTicketInspector(input: $input) {
  ticketInspector {
    __typename
    id
    name
    email
    phoneNumber
  }
}
}

Validation when type: BoardMember:

• boardMemberId must reference an existing administrator on your organization (otherwise: Board member not found).

The boardMemberId is not a Member.id from the members query — it's the internal Administrator ID. If you don't have administrator IDs available through your integration, prefer external inspectors.

Remove an inspector

mutation removeTicketInspector($input: RemoveTicketInspectorInput!) {
removeTicketInspector(input: $input) {
  success
}
}

Errors:

• Ticket-inspector with id: <id> not found.
• Cannot remove ticket inspector from an event, which is completed.
• Cannot remove ticket inspector, who has already checked-in tickets — once the inspector has scanned at least one ticket, the relationship is preserved as audit history.