Ticket Revalidation API Reference

Currently available in pre-production to all customers. Will be available in production on October 21, 2026.

POST

ticket/tickets/revalidate

Base path:

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

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

Related Content: GDS Order Change Notification Handling Guide

Following an airline-initiated schedule change, the updated itinerary may require the associated ticket to be synchronized with the newly confirmed flight details. The existing ticket can be revalidated where supported, allowing the revised itinerary and ticket coupon information to remain aligned without requiring a ticket reissue.

The original ticket number remains the same.

GDS only

Ticket revalidation is subject to airline participation. If the airline is not a participant in ticket revalidation, an even exchange has to be initiated after accepting the schedule change.

Ticket revalidation is dependent on the carrier’s revalidation rules and the eligibility of the affected itinerary.

  1. Retrieve the PNR using the Reservation Retrieve request.

  2. Get the ticketing details from the PNR (Ticket number, Coupon, Segment, Place).

  3. Send the ticket revalidation request with the information gathered from the reservation retrieve response.

  4. If it is successful, no action required.

  5. If it is unsuccessful, process even exchange manually.

Request

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

Query Parameters

None.

Request Body

Response

The response contains the latest ticket information after revalidation. The response body is the same as the Ticket Retrieve API response. Refer to Ticket Retrieve response for details.

 

Example Request

Example Response