Here you have all the messages with the functionality our API supports with the message structure.

There are many examples with full end to end message flows that will help you. Messages for the same Order must be processed sequentially, the next message should not be sent until after receipt of the response to the previous message.

Please remember that many new functionalities will only be developed in the latest API version. So we highly recommend you always use the latest version as soon as possible.

3-D Secure payment is being mandated in many markets and is ONLY supported in our 17.2 version using an augmentation point.

The following table is used as the master and embedded in all the other pages

 New or modified element

To be removed/deprecated

Unique to v2 - Branded Fares

Unique to V1 - Fare Families

This section is made up of the following subsections, a description of which can be read at the begining of each subsection:

For full end-to-end flow examples please see our Examples page.