The flow (recommended)
1) Search lounges at an airport
You show lounge options for an airport (IATA code), including pricing for adults/children.
2) User selects an offer and variant
Your UI should clearly show:
- terminal and location (where to go)
- opening hours (with timezone)
- included features and paid add-ons
- restrictions (dress code, age limits, etc.)
3) Create an order (one per guest)
Create an order for the guest and store the returned order ID in your system.
What to show in your UI
Offer details
Offer details
When the user browses lounges, show:
- lounge name and terminal
- where to find it (for example “after security” and gate context)
- opening hours (with timezone)
- included features and paid add-ons
- restrictions (dress code, age limits, etc.)
Booking details (what to collect)
Booking details (what to collect)
You typically collect:
- guest name
- flight number (when applicable)
- visit date
- guest type (adult/child) if pricing differs
After booking (what to show)
After booking (what to show)
After the booking is confirmed, show:
- booking status
- lounge location instructions
- the access code the guest presents at reception
UX guidance (what to communicate)
Show time and location clearly
Show time and location clearly
Users miss lounges because the terminal/location is unclear. Put the terminal, gate context, and “after security” style hints near the access code.
Explain payable features
Explain payable features
If a feature is marked payable, explain that it may require payment on-site.
Explain guest rules
Explain guest rules
This API uses one order per guest. If the user needs to book for multiple travelers, your UI should support repeating the booking flow.

