Sharing essential product information with your customers

Clear and timely provided product information helps build trust, avoid confusion, and reduce customer support requests. Whether it's setting expectations before checkout or showing exactly what was booked, the Tiqets API makes it easy to guide your users smoothly through their journey.

This guide walks you through the key API endpoints and shows you—step by step—how to surface relevant details before and after purchase.

Show important information before the Booking

Before the customer reaches the payment screen, it's important to display clear information about what’s included in the ticket, who qualifies for discounts or not, or essential information to be aware of before the booking.

Use the following endpoint:

GET /products/{product_id}/checkout_information

{
    "success": true,
    "api_version": {
        "major": 2,
        "minor": 5,
        "patch": "v250422-1134.1"
    },
    "additional_information": {
        "must_know": "* You may expect some waiting lines before the security check",
        "pre_purchase": "* Free entrance with valid ID for: EU residents under 26 yo, Non EU residents under 18 yo, disabled visitors + carer, French jobseekers, and you must **book a free timeslot on the Louvre website**.",
        "usage": "* Enter via the Pyramid, using the line for Louvre ticket holders with a timeslot\r\n* Show your Louvre Museum ticket\r\n* If you leave the museum, you won't be allowed back in with the same ticket\r\n* Please note that if you miss the timeslot you'll need to join the line for ticket holders without timeslots\r\n* Ticket holders may be asked to present a valid photo ID. Without it, access to the museum will be refused",
        "post_purchase": "* This e-ticket is personal, non-transferable, valid only for the date and time printed. Access to the museum is subject to its validity\r\n* Keep your e-tickets during the visit",
        "good_to_know": "* Due to the size of its collections and its day-to-day agenda, the museum can't keep all of its rooms open every day. Please note that galleries may occasionally close on short notice. For further details, please check the official website\r\n* You can download a self-guided tour from the Louvre's website or pick up a multimedia guide (both for a fee of €6, may require a valid ID deposit)\r\n* Please note that items exceeding 55 cm x 35 cm x 20 cm are not permitted in the museum. Self-service lockers are available free of charge beneath the Pyramid",
        "included": "* Fast-track entry to Louvre Museum\n* Access to the temporary exhibitions\n* Access to the permanent collection\n* Access to Eugène Delacroix Museum (within 48 hours of your Louvre visit)",
        "excluded": "* Skip the security line \r\n* Fast-track access to the temporary exhibitions"
    },
....
}

What to include in your UI Here are the fields to extract and display:

• must_know – Entry requirements that apply to all visitors.

• pre_purchase – Eligibility notes (e.g., age limits, ID requirements).

• usage – Instructions on how to access the venue.

• post_purchase – Details users need immediately after completing their booking.

• good_to_know – Bonus tips or extras worth mentioning.

• included / excluded – What the ticket covers, and what it doesn’t.

Presenting this information clearly from product to checkout reduces uncertainty and builds confidence.

Here is an example for one of the Sagrada Família products and how we choose to emphasise the important information at the participant selection stage.

Example of important checkout information show at the participant step

Confirm what was booked

Once the purchase is complete, your user expects a clear summary of what they have just bought. That’s where the ticket confirmation endpoint comes in.

Use the following endpoint: GET /orders/{order_reference_id}/tickets

This endpoint returns a snapshot of the exact ticket and its conditions at the time of booking.

{
  ...
  "how_to_use_info": "Show your smartphone ticket at the entrance gate",
  "post_purchase_info": "Free shuttle from Plaza every 20 mins...",
  "must_know": "* Pets not allowed, children must be accompanied...",
  "included": "* Park entry, live exhibitions...",
  "excluded": null,
  "tickets_pdf_url": "https://api.tiqets.com/voucher.pdf",
  "starting_point_address": "351 High Street",
  "starting_point_latitude": 55.949865,
  "starting_point_longitude": -3.191227
  ...
}

What to include in your UI

• how_to_use_info – How to present the ticket (e.g., show it on a phone).

• post_purchase_info – Tips on reaching the venue or using the ticket.

• must_know, pre_purchase, good_to_know – Re-display key rules and helpful tips.

• included / excluded – Recap of what’s included in the ticket.

• starting_point_address / coordinates – If there is a meeting point.

• tickets_pdf_url – Provide access to the PDF version of the ticket.

It is strictly forbidden to alter or modify the provided PDF tickets in any way. The tickets are checked by staff at the entrance or starting point of the experience. If prohibited alterations are suspected, the customer may be denied access to the experience without entitlement to any compensation.

Example of confirmation email with showing important informations

Why this matters

Always display the ticket information from the /orders/.../tickets endpoint after the purchase, even if you have already shown the checkout_information beforehand. The information may differ depending on the ticket actually selected. (see Maximising availability using Multi-sourcing)