Get a voucher
Retrieve the full partner voucher payload for a booking. Use the bookingId and voucherId returned in the booking response from the create, list, or get booking endpoints.
{bookingId} is that response’s bookingId, and {voucherId} is its voucherId.
For a walkthrough of every section and field — what each one holds, when it is null, and how it renders on the voucher — see Voucher API deep dive, under Key concepts in the Guides.
Authorizations
Path Parameters
The booking the voucher belongs to. Use the bookingId returned in the booking response from the create, list, or get booking endpoints.
The voucher ID to retrieve. Use the voucherId returned in the booking response from the create, list, or get booking endpoints.
Response
Successful response
Full partner voucher payload for a confirmed booking.
Current lifecycle state of the booking, using the same vocabulary as Get Booking. See Voucher booking status.
PENDING: Payment captured — confirmed with supplier.COMPLETED: Booking fulfilled.CANCELLED: Booking cancelled.
ticketSection and checkinButton are null for a cancelled booking, and ticketSection is usually null until the booking reaches COMPLETED. Bookings that were never captured (UNCAPTURED, CAPTURE_TIMEDOUT) have no voucher and return 404.
PENDING, COMPLETED, CANCELLED The layout this voucher is meant to be rendered in — SINGLE_PAGE for a single screen, MULTI_PAGE for a longer multi-section layout. Follow it: venue staff check vouchers against the expected layout, and rendering in a different one risks the guest being turned away. See Voucher template.
SINGLE_PAGE, MULTI_PAGE Booking identifiers and product summary. Always returned, for every booking status.
Ordered array of information banners to display on the voucher. Render every entry in the order returned, showing title as a heading and htmlDescription as its body — the HTML is pre-sanitized. Returned empty when the booking has no callouts.
Guest, schedule, seats, and location details. Null when no booking details are available for this voucher.
Check-in URL when the experience supports online check-in. Null for most bookings, and always null for a cancelled booking.
Downloadable tickets and QR codes. Null when no tickets are attached to the booking. The guest then follows the redemption instructions: if they include steps to generate or collect tickets, the guest must complete them; if not, no ticket is required and the guest presents the voucher at the venue. Also null for a cancelled booking. See a live example of a voucher with no ticket section.
Redemption instructions. Null when no instructions exist. Exactly one of legacy or structured is non-null — branch on which field is present. See Voucher API deep dive.
Vendor/operator contact details. Null when the operator has not provided contact information.
Legal disclaimer text to display at the bottom of the voucher. Null when not applicable.