Assign inspectors

A ticket inspector is the person who scans tickets at the door. You can assign external one-off inspectors (typed in by hand) or board-member inspectors (looked up via an internal administrator ID).

All steps require a JWT — get one from the homepage first. The API key needs the events:write scope.

Option A — external inspector

The straightforward path: type in name, email, and phone. Use this when you don't have a board-member administrator ID handy, or when the inspector is hired one-off staff.

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

Repeat for each external inspector you want to assign.

Option B — board-member inspector

Only viable if you have an internal boardMemberId (an Administrator ID — not the Member.id from the members query). When the type is BoardMember, the server pulls name, email, and phone from the linked user automatically; the input fields are ignored.

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

The administrator ID isn't exposed via this API — you'd typically obtain it from the Unioo platform UI or another internal system. If you don't have it, prefer Option A.

Verify the inspector list

query verifyInspectors($id: UUID!) {
events(where: { id: { eq: $id } }, first: 1) {
  nodes {
    id
    name
    ticketInspectors {
      __typename
      id
      name
      email
      phoneNumber
    }
  }
}
}

Remove an inspector

If you assigned the wrong person — or someone dropped out — remove them. Refused if they've already scanned at least one ticket (audit trail).

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

Next: monitor sales as people start buying — see Monitor sales.