JSON APIs Required Full Workflow

The following diagram shows the API requests in the minimum required workflow to ticket a flight in the JSON APIs. Also see JSON APIs Full Workflow with Optional Steps and All Book and Ticketing Workflows for additional options.

Each box in the diagram represents one API call in the workflow.

Related Content: JSON APIs Guide, Air Shopping Guide, Booking Guide, Ticketing Guide

Note that the above JSON APIs workflow uses reference payload In the JSON APIs, an API call that sends identifers referring to a previous response for the itinerary to be shopped, priced, added, etc. instead of full itinerary details. requests, which send identifiers to select an offer In the JSON Search APIs, an offer is a product available at a specific price under a set of terms and conditions. An offer includes the flight or connecting flights for one leg of the itinerary, plus a service level that includes the cabin class and any fare codes that may apply. At booking, the selected offer from the Search response - including the flight/s, service level, price, terms and conditions, and brand if applicable - is converted into a single Offer object that is subsequently returned for that booking. from previous JSON API responses. Optionally, you can send the AirPrice full payload request and omit the Search request, or send an Add Offer full payload request and omit the Search and AirPrice requests. This allows you to source your flights outside the JSON APIs and skip these steps of the JSON workflow.