Ticket Retrieve API Reference

POST

ticket/tickets/getbylocator

Base path:

Use this base path if you have not yet received or not migrated to the new credentials from Travelport:

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

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

Use this base path after you have migrated to the new credentials from Travelport (using .net instead of .com):

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

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

Related Content: Ticketing Guide

The Ticket Retrieve request returns details for a single ticket for NDC, or for all tickets associated with a record locator for GDS.

Although the JSON Ticket Retrieve API supports retrieving NDC tickets, not all NDC carriers support retrieving NDC tickets through the EDIFACT/GDS path. For the most consistent and reliable retrieve, best practice is to use Travelport Smartpoint Cloud to display NDC tickets. Note that ticket display functionality for NDC transactions is not supported in terminal programs.

The JSON Air APIs provide the following APIs to retrieve bookings and tickets:

  • To retrieve all booking details either by locator code or ticket number, use Reservation Retrieve.

  • To retrieve a list of all ticket numbers on a reservation, use Ticket List.

  • To retrieve details for all tickets associated with a record locator (GDS only), or for a single ticket for NDC, use Ticket Retrieve.

  • To return a list of documents on a booking, including tickets, invoices, MCOs, and EMDs, use Document List.

  • To return histories of up to six documents on with a booking, including tickets, invoices, MCOs, and EMDs, use Document History.

For differences between GDS and NDC in the JSON APIs, see the support tables for seats, ancillaries, fare rules, and exchanges, and the NDC and GDS Functionality Comparison.
For differences within NDC by individual carriers, see NDC capabilities by airline through JSON API in the Travelport Knowledge Base. If you need login assistance, see Knowledge Base NDC Resources.

Request

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

Query Parameters

None.

Request Body

Response

For each ticket returned, the response returns the reservation locator, traveler name, form of payment details, flight departure and arrival information, a price breakdown by PTC, and agency information. Not all details may be returned if not part of the booking record.

Example Request

Example Response

For additional examples, download the developer toolkits and see Using Postman and Developer Toolkits.