INTEGRATION: TICKETING
See Tickets, validated at your gate.
Bloop checks ticket barcodes against See Tickets and registers the scan back, so a barcode used at the north entrance is dead at the south one. Guest list entries you create in Bloop are pushed to See so the box office and the door agree.
WHAT MOVES, AND WHICH WAY
↔ BOTH WAYS
Guest list entries
Names, emails, ticket type and plus-ones you manage in Bloop are pushed to See Tickets, and barcodes come back onto the entry.
→ INTO BLOOP
Scan counts
Door counts pulled back from See so event control sees one number, not two.
→ OUT OF BLOOP
Scan registration
A barcode scanned in Bloop is registered back to See, so it cannot be reused elsewhere.
SETTING IT UP
- Ask See Tickets for API access for your account.
- We add your token to the deployment and link each Bloop event to its See show code.
- Run a preview sync first: it shows exactly what would be created before anything is written.
WHERE IT STOPS
- The link is per event: each Bloop event is bound to one See show code.
- Preview and live sync are separate actions, deliberately. Nothing is written until you ask.
- Scan registration needs connectivity to reach See; scans queue locally and register when the signal returns.