Open QR Code

March 5, 2025

The AnyRoad QR code on guest tickets (digital, apple wallet, or printed) is readable by 3rd party systems, allowing you to identify guests by scanning their AnyRoad ticket and provide them a more customized experience.

For example, a customer used Open QR Codes with their on-site photo booth. When a guest arrived at the photo booth, they scanned the QR code on their AnyRoad ticket and automatically sent their photo to them afterwards using their AnyRoad registration information.

By scanning the QR Code with a 3rd party scanner, you can directly extract the AnyRoad booking ID, ticket ID, and guest ID. No API calls are needed to extract and decode these IDs. You can then match these IDs to booking and guest first party data that is collected via AnyRoad APIs or Webhooks before or afterwards.

Open QR Codes support guest tickets but not add-on tickets.

FullView versus Non-FullView tickets

FullView is an AnyRoad feature that allows you to collect first party data about all guests on a booking, not just the booking guest.

If FullView is enabled on your account, AnyRoad tickets correspond to a specific guest (e.g., John Smith). If FullView is not enabled, tickets correspond to a particular ticket type (e.g., Adult, Child, etc.) on a booking, but not a specific guest. The Open QR code includes guest_id if the ticket is a FullView ticket. If it’s not a FullView ticket, guest_id is omitted from the QR code.

Practically, this means that:

• For FullView tickets, you can extract Guest ID from the QR code, query the Guest API, and capture the first party data associated with that individual guest.

• For non-FullView tickets, you can extract Booking ID from the QR code, query the Bookings API, and capture the booking guest information, which will be the same across all tickets on a booking.

How it Works

• Scan the QR code with a 3rd party scanner to extract the full string. It will be a Base64 encoded JSON object that looks like this:

data:application/json;base64,eyJib29raW5nX2lkIjoiMzAzNjI1NiIsInRpY2tldF9pZCI6IjQyMzUyNjIi LCJndWVzdF9pZCI6IjMxNTg3MDEifQ==

• Parse the string by splitting it using the “,” and keep the right string. This will give you a Base64 encoded JSON object string that looks like this:

eyJib29raW5nX2lkIjoiMzAzNjI1NiIsInRpY2tldF9pZCI6IjQyMzUyNjIi LCJndWVzdF9pZCI6IjMxNTg3MDEifQ==

• Base64 Decode the parsed string.

For FullView tickets, this will give you the following string where:

• b = Booking ID

• t = Ticket ID

• g = Guest ID

{"b":"3036256","t":"4235262","g":"3158701"}

For Non-FullView tickets, this will give you the following string where:

• b = Booking ID

• t = Ticket ID

{"b":"3036256","t":"4235262"}

• You can then parse the JSON string to a JSON object in your code and access the various properties:

• Booking ID (“b”) - will be the same ID across all tickets on the same booking. You can use this ID to query the AnyRoad Booking API to extract booking information, including the booking guest contact information.

  • Ticket ID (“t”) - each individual ticket has a unique ID. The ticket_id is not currently available via AnyRoad APIs.

  • Guest ID (“g”) - this field only appears on FullView tickets. It corresponds to an individual guest record. You can use this ID to query the AnyRoad Guest API to extract guest first party data.