Booking flow

Overview

The Reseller API Integration Guide describes a RESTful API that operates on a mediation model, where Consumer Systems serve as intermediaries between end customers and ticket vendors. The booking API delivers data on products, their availability, and purchase options, and provides the reseller with the capability to create and manage bookings.

• Workflow sequence Diagram
• Flags and state machine Diagram
• Learn by example - Postman collection
• Learn by example - Swagger-UI

Implementation Guidelines

The Amadeus Discover Booking Flow enables the booking of an Amadeus Discover product through the Quick Connect.

It is articulated in 6 steps.

At any point after the Creation step, it’s possible to retrieve the booking information. After the confirmation, it’s possible to retrieve the activity voucher to expose to the user and to cancel the booking (if the cancellation policy allows it). These capabilities are detailed in the last section, about Post Booking.

• 1. Availability
  • getAvailability
  • getNextAvailability
• 2. Options
  • getOptions
  • setOptions
• 3. Prices
  • getPrices
  • setPrices
• 4. Booking Creation
  • createBooking
• 5. Questions
  • getQuestions
  • setQuestions
  • Follow-up questions
• 6. Confirmation
  • confirmBooking
• 7. Post Booking
  • getBooking
  • cancelBooking

Useful products to test

Here’s a list of product IDs for products that have interesting use cases to verify the solidity of your implementation.

ID	Summary	Description
139046601	No Options	This product has no option, the user should proceed directly from availability to pricing step
139303211	minParticipants required	This product requires a minimum of 2 participants to be booked
139315704	Question with OPTIONS type	Example product exposing an OPTIONS question in the Questions step after specific upstream selections.
139008719	Option with TEXT type	Example product exposing a TEXT option in the Options step based on selected option values.
139653931	Multiple level of questions	Example product with conditional follow-up questions. You may need multiple putQuestions calls, each time resubmitting all known answers and adding newly requested follow-up answers.
139271894	Conditional follow-up questions	Example Viator product with conditional follow-up questions.
138999781	Option with BOOLEAN type	This product is one of the few that require an option of type BOOLEAN in their Options step. To get it, first select the first 2 levels of Options
139513627	Question with ACCEPT type	This product is one of the few that require a question of type ACCEPT in their Questions step.

Headers

Instructions about language and currency to be used in the Booking Flow are provided via the following HTTP headers. The values of these headers should remain consistent throughout the flow; otherwise specific errors can be returned.

Header	Description	Accepted values
Accept-Language	language for which the flow should be localized	EN, ES, FR, IT, AR, DA, DE, FI, JA, NO, PL, PT, SV, TH, ZH
(DEPRECATED) currency	currency to which all prices and amounts should be converted (see 3. Prices)	AED, AUD, BRL, CAD, CHF, DKK, EGP, EUR, FJD, GBP, INR, MXN, NAD, NOK, NPR, NZD, PEN, QAR, SAR, SEK, SGD, THB, USD, ZAR

Note

• Please note that not all suppliers or products support all languages. In case it’s not possible to localize to the requested language, the catalog default language will be returned instead.

• Please note that not all suppliers or products support all currencies. In case it’s not possible to convert to the requested currency, the catalog default currency will be returned instead.