Unified Checkout API Reference

POST

book/reservation/reservations/build

Base path:

Pre-production https://api.pp.travelport.net/11/air/

Production https://api.travelport.net/11/air/

Related Content: Unified Checkout Guide

As an alternative to the multi-request booking workflow that takes place in a workbench session, you can send all booking details and commit one unified checkout payload to create a booking. The unified checkout book request does not support some of the optional steps in the booking workflow, such as adding seats or ancillaries. Available for both NDC and GDS.

Seats and ancillaries not yet supported.

Request

As part of the request requirements, also see Authentication and Common Flights API Headers.

Query Parameters

None.

Request Body

The following information applies to both reference and full payload requests.

In addition to the information above, both full payload and reference payload have other details that are required in the request.

Full payload details

GDS only

Reference payload details

When sending a reference payload Unified Checkout request, flight and price details from the previous shop and price transactions are referenced in the Unified Checkout request. Applies to both GDS and NDC.

Response

The response returns all details from the request about the booking, which generally include the offer (actual air segments booked), traveler details, and reservation confirmation information. A successful booking returns a unique six-digit alphanumeric number called the reservation locator in Receipt/Confirmation/Locator.

Example Requests

GDS full payload

The following full payload sends the minimum information needed to book a GDS offer. This example does not send Payment or FormOfPayment so the offer is put on hold and no ticket is issued.

The following full payload sends all information needed to book and ticket a GDS offer, including optional details.

Full payload request for unpriced segments

GDS reference payload

The following reference payload sends the minimum information needed to book a GDS offer. This example does not send Payment or FormOfPayment so the offer is put on hold and no ticket is issued.

The following reference payload sends all information needed to book and ticket a GDS offer, including optional details.

NDC reference payload request

The following reference payload sends the information needed to book and ticket an NDC offer.

 

Example Responses

GDS full payload responses

The following response is from a full payload request that sent the minimum information needed to book a GDS offer. The request did not include Payment or FormOfPayment, so the flights are help but not ticketed.

The following response is from a full payload request to book and ticket a GDS offer, including optional details. Because Payment and FormOfPayment was sent in the request, the offer was both booked and ticketed. The response includes Reservation/Receipt/Document, which provides the ticket information and amount.

Unpriced segment response. Unpriced content is returned in UnpricedSegments object.

GDS reference payload responses

The following response is from a reference payload request with the minimum information needed to book a GDS offer. This example does not send Payment or FormOfPayment so the offer is put on hold and no ticket is issued.

The following response is from a reference payload request that sent all information needed to book and ticket a GDS offer, including optional details. Because Payment and FormOfPayment was sent in the request, the offer was both booked and ticketed. The response includes Reservation/Receipt/Document, which provides the ticket information and amount.

NDC reference payload response

The following response is from a reference payload request that sent the information needed to book and ticket an NDC offer. Because Payment and FormOfPayment was sent in the request, the offer was both booked and ticketed. The response includes Reservation/Receipt/Document, which provides the ticket information and amount.