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 Consumer API.

It articulates 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 section.

• 1. Availability
  • getAvailability
  • getNextAvailability
• 2. Options
  • getOptions
  • setOptions
• 3. Prices
  • getPrices
  • setPrices
• 4. Booking Creation
  • createBooking
• 5. Questions
  • getQuestions
  • setQuestions
• 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
85948244	minParticipants required	This product requires a minimum of 2 participants to be booked
139315704	Question with OPTIONS type	This product is one of the few that require a question of tip OPTIONS in their Questions step. To get it, you need to previously select the Option ‘Kayak Tour with Hotel Pickup”
139008719	Option with TEXT type	This product is one of the few that require an option of type TEXT in their Options step. To get it, you need to select Custom Location for the option called Pickup Location.

Headers

Instruction about language and currency to be utilized in the Booking Flow are given via the following HTTP headers. The value of these headers should remain consistent all alonmg the flow, and will trigger specific errors if not.

Header	Description	Accepted values
Accept-Language	language for which the flow should be localized	EN, ES, FR, IT
currency	currency to which all prices and amounts should be converted	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 currencies. In case it’s not possible to convert to the requested currency, the catalog default currency will be returned instead.