Document History API Reference

POST

documents/history

Base path:

The base path for this API varies from that for other JSON Air APIs and does not include air at the end.

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

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

Travelport has updated all JSON API authentication and authorization endpoints. Previous pre-production endpoints were deprecated 5 Dec 2025. Previous production endpoints are scheduled for deprecation 30 Jan 2026. API transactions using these endpoints after these dates in those environments will fail. See Endpoint Migration for details.

Related Content: Air Booking Guide

Document History retrieves the history of all documents associated with a record locator code. This request can retrieve this information even after the booking and tickets are purged from the airline's database. You can request documents by any of the following:

  • Record locator: Returns all documents associated with that locator

  • Document type: Returns all documents of the specified type/s

  • Document number: Returns history of the specified document/s only

The response can return the following types of documents as applicable and as requested:

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

  • To retrieve all booking details, use Reservation Retrieve. Returns all booking, payment, and ticketing information currently on a booking,

  • 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.

Request

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

Query Parameters

None.

Request Body

Response

The objects returned in documentHistories vary according to the type of document returned. See the developer toolkits for the Swagger files for full specifications.

Example Request

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

The request payload requires the locator code. Sending one ore more document numbers associated with that locator code is optional.

Example Response

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

In response to a request that sends a record locator and a specific ticket number, the following response returns one instance of documentHistories, for the requested document.

In response to a request that sends only a record locator, the following response returns tickets and an invoice associated with that locator.