Important URLs
Galileo Web Services©
1. The Travel Codes Translator eBL
url: http://testws.galileo.com/GWSSample/TravelCodesTranslatorClient/testpage.aspx
Notes:
standard codes are used in the travel trade through out the world.
For eg., We use City codes
DEL for Delhi or BLR for Bangalore or Airline codes 9W for Jet Airways.
This data can also be updated periodically to keep the DB uptodate.
Video:
2. The Documentation URL
url: https://support.travelport.com/webhelp/GWS/GWS.htm
Notes:
- This URL contains all the XML transactions that can be used,sample requests along with a description of each tag and the values passed in themare explained here.
3. The XML Test Page
url: http://testws.galileo.com/GWSSample/XMLSelectClient/testpage.aspx
Notes:
- This Test Page is used to test all the Galileo Web Services Transactions
Both Sessioned (SubmitXmlOnSession and SubmitTerminalTransaction methods) and Sessionless Transactions (SubmitXml and MultiSubmitXml methods) can be tested using this page.
4. Copy System WSDL
url: https://apac.copy-webservices.travelport.com/B2BGateway/service/XMLSelect?WSDL
Notes:
- The Web Services Description Language for all GWS Transactions in the copy system can be found in this URL.
Travelport Universal API©
1. Register for a Travelport Universal API sandbox access
url: https://developer.travelport.com/
Notes:
- Register for a free sandbox access to start your development, The access is valid for one month.
2. Travelport Universal API Documentation
url: https://support.travelport.com/webhelp/uapi/uAPI.htm
Notes:
- The complete updated UAPI documentation is at this link, Would recommend that you read through the introduction to Travelport Universal API and before you start notes found at this site.
3. Download the latest Universal api WSDLs and Schema
Notes:
- As of 2015, There are 5 releases in a year, Would recommend that the latest release be used at the time of development.
4. Download the latest Travel Industry codes
url: https://developer.travelport.com/euf/assets/developer-network/downloads/ReferenceData.zip
Notes:
- IATA standard codes are used in the travel trade through out the world.
For eg., We use City codes DEL for Delhi or BLR for Bangalore or Airline codes 9W for Jet Airways. - One of the first tasks that a developer performs is to download these codes from the above link.
These codes need to be used in Request XMLs sent to the UAPI Host.
5. Download the sample source code from GitHub
url: https://github.com/Travelport
Notes:
- UAPI is Open Platform and you may use any Technology/Programming language to code, As of Mar 2015 -
Source code is currently available in PHP, C#.NET and Java.
You could also take a tutorial @ http://travelport.github.io/travelport-uapi-tutorial/
6. Test multiple scenario's on the Travelport Demo Site
url: https://demo.travelportuniversalapi.com/
Notes:
- The Travelport Universal API Demo site also contains the actual XML request and responses used in a given search.
Adhvan - Web based solution
Features of Adhvan
[Click on the link to go through the Presentation.]
Presentation on Adhvan
- Adhvan is the White Label Solution, caters both Business 2 Business (B2B) and Business 2 Customer (B2C).
- Within 4 easy steps your staff and your registered client can create booking in less than 2 minutes and on Single window you are able to see all Full service and 3 LCC fares and flight option.
- Client will have an option to filter to search based on Type of journey, Airlines preference, Departure and Arrival date and Time, Number of passengers travelling.
- An agent can create multi sub agents and further sub agent can create their own agency account (multi tier Architecture).
- Admin can update Sub Agency Status- activate and deactivate and also can upload the credit limit for a Sub Agency same can be Increased/Decreased.
- Admin own Galileo PCC and LCC(GO, Indigo & Spicejet web id) will be used to make all bookings, this way you will not lose out onto your own segment generation, adding to it LCC bookings can be done through Direct API's integration in the Adhvan or with clients LCC WEB ID's.
- End customers are allowed to create bookings as Registered user or as Guest user as well.
- Adhvan empower the agency to search and create all Full service carrier through their own PCC and will have option to HOLD or ISSUE TICKET.
- Agency can create their customer profile in Adhvan by adding few information such as -:Meal request, Seat request, Frequent flier number, Passport number and SSR commands.
- Agency can create pre-defined table to add MARKUP & TRANSACTION FEE on all transaction based on routing and carrier wise.
- For Payments Multiple options are available in Advan-: Credit Limit (B2B only) and Third Party payment gateways integration option. We can Integrate Payment Gateway (Bank suggested by you) and the client can punch his credit card onto your portal and the amount will be deposited to your payment gateway against the Booking/Ticket done by the client.
- A high speed storage mechanism. Caching at different level helps to reduce response time.
- Reports-Adhvan system itself generates multilevel of reports to keep a track on Daily bookings, Incentive ,Transaction Fee...etc.
New Enhancements -
1. Mini Fare Rule Integration
- Currently available for Domestic bookings.
2. Change RBD Functionality
- Currently available for Domestic bookings.
3. ACH Special Round Trip Integration
- ACH Special Round trip is now available in Adhvan, customers can get special round trip fares for indigo from Adhvan directly.
4. Indigo seat map
- Seat map of Indigo live on Adhvan, customers can now view and select seat for indigo at the convenience of seat map GUI added in Adhvan.
5. Indigo Hold booking
- Indigo Hold functionality has been integrated and is live in Adhvan, agents can hold an indigo PNR as per airline norms and confirm the same later by making payment.
6. Room master integration with New Look and feel
- Room master content in Adhvan has been revamped to give more welcoming look and increase the convenience of booking rooms.
Few Current Live Sites -
Process Automation Tool
[Click on the link for document.]
Document on PAT
- The Process Automation tool (PAT) , It brings in efficiency and helps both the agency and the corporate working with the agency to reduce costs in terms of time and money.
- The Process Automation Tool has two central themes:-
- Transaction Flow
- Business Flow
1. Transaction Flow
- Transaction flow which consists of the following modules
a. Pre Booking Module
b. Booking Module
c. Post Booking Module
- The Transaction Flow covers the process flow for transactions like retrieving the right corporate and traveller profile, making the booking for the traveller, post booking support such as cancellation and re-issuance typically performed by the travel counsellor. Post booking support would also cover refund as an important function.
2. Business Flow
- Business Flow which consists of the following modules
a. Masters
b. Corporate Configuration and Settings
c. User Settings and Role Centre
d. Business Settings
- The Business Flow covers the process flow for configuring the corporate on PAT and preparing its business layer involving management of codes, commission, discount, transaction fee, handling form of payment, sorting queues etc.
Features and Benefits
- Masters
- Airline mapping code - Pricing code, deal code, tour code, tracking code and promo code setting for GDS and LCC carriers.
- Hotel mapping code - Corporate wise hotel RAC code configuration for negotiated rates.
- FOP(form of payment) mapping - Fop auto setting as per airline, RBD etc.
- Group - Group creation is related to transaction fee, discount, FOP etc.
- Class: Premium economy, business, first class and economy.
- All types of deal and tracking codes can be managed by one master.
- All types of Form of Payment combinations are automated (pass-through, non pass-through, credit, cards etc).
- Activate/deactivate GDS carriers on the basis of business requirement.
- Finance
- Agency IATA Discount - IATA discount setup airline to airline.
- Airline Commission - Airline commission for retail, corporate , Soto and side trip(Airline wise).
- Transaction Fee - Dynamic transaction fee settings i.e. Online, Offline , region, per sector, per transaction and cabin wise.
- Revenue Settings - Hidden mark up/discount apart from Transaction Fee.
- Corporate settings.
- Prevention of financial leakage as discount could be given as per fare type.
- Discount/Mark up covers per transaction, per person, per ticket type of scenarios to ensure proper revenue management.
- Auto ledger for corporates on credit with details of transaction for better fiscal management.
- Special Services
- Online booking for domestic and international airlines(Retail and corporate fare for GDS and LCC both) .
- Online LCC airline bookings with Ancillary services(Seat, Meal ,Baggage ).
- Online Full and Segment wise cancellation for both LCC and GDS carrier.
- Offline reissuance for GDS carrier.
- Online Hotel booking.
- Auto billing sync.
- Automated bookings to ease staff duress with coverage of codes and different scenarios .
- Import facility with auto ticketing for maintaining integrity of data and ensuring billing of all transactions.
- Passive bookings for all transactions to capture vital information for both billing and MIS.
Benefits:
Benefits:
Benefits:
August 2025 – Monthly Bulletin
1. JSON API Search Penalty Object Enhancement
For full advisory details, please visit: Advisory Link
Overview
Previously, when the same penalty information (change and cancel) was returned for multiple PTCs, JSON API Search provided one penalty object per passenger type. With this enhancement, users will now see only one penalty object for multiple PTCs (ADT, CNN, INF) if the penalty information is the same for all passengers in the search response.
Scope
- JSON API Search v11 for GDS content
- Next Leg Search
- Flight Specific Search
- Split Ticketing Search
- Integrated Search (GDS and NDC, impacting GDS information only)
Customer Benefit
- Improved search response with less redundant information
- Parity with JSON API Price
Schema Changes
There is no model version change.
Impacted Services and Schema
No new query parameters are introduced in the JSON Search v11 request.
Detailed Description
When the same Change / Cancel penalties are returned for multiple PTCs, JSON API Search will now return a single Penalty object and reference all applicable PTCs in Penalties.PassengerTypeCodes. This enhancement mirrors the existing improvement in the JSON API Price response.
Example 1:
Before: Request with 1 ADT and 1 CNN (no age). Same penalties are returned for both PTCs, but JSON API Search returns 2 Penalty objects with PassengerTypeCodes ADT.
Now: Only 1 Penalty object is returned with PassengerTypeCodes ADT.
Example 2:
Before: Request with 1 ADT, 1 CNN (age 5), and 1 INF (age 1). Same penalties returned for all, but 3 separate Penalty objects were shown.
Now: Only 1 Penalty object is returned with PassengerTypeCodes ADT, CNN, INF.
2. Hotel JSON SearchComplete – Property Filter Definitions
For full advisory details, please visit: Advisory Link
Advisory Details
- Advisory Number: DA-1086
- Version: 1
- Effective Date: August 04, 2025 – 7:00 AM EDT
- High-Level Description: Introduction of a new PropertyType filter in Hotel JSON SearchComplete by Location to allow users to select which property types to include in the response. Complete set of property filters and definitions provided.
Impact Summary
Users can now select property types from an enumerated list to include in the response.
Reason for Issue
First notification.
Impacted Customers
Developers.
System(s)
Travelport+ (1G)
Load to Pre-Production
July 28, 2025 – 7:00 AM EDT
Overview
Hotel JSON SearchComplete combines Search, Details, and Availability into one request/response sequence. The SearchComplete by Location functionality allows users several options for determining the list of properties returned in the response.
Property Filter Object / Element Details
| Object / Element | Description and Snippet | Required / Optional |
|---|---|---|
| propertyFilter | Top-level object for hotel search data. Filters restrict which properties are returned in the response. | Required |
| maxWaitTime | Numeric. Maximum wait time (milliseconds) for supplier response. Default: 10000. Suppliers not responding within the time limit will return a warning. | Optional |
| location | Object defining the type of search to conduct. | Optional |
| type | String. Defines type of location search: airportIATACode, cityIATACode, coordinates, address. |
Required if using location object |
| details | Object containing details related to location search. | Required if using location object |
| iataCode | 3-character code for city or airport search. Used with airportIATACode and cityIATACode. |
Optional |
| latitude | Latitude value of geocode. Used with search type coordinates. |
Optional |
| longitude | Longitude value of geocode. Used with search type coordinates. |
Optional |
| countryCode | Two-character ISO 3166 code for a country. Used with search type address. |
Optional |
| stateProvince | Two-character state or province code. Used with search type address. |
Optional |
| cityName | Fully spelled-out city name. Used with search type address. |
Optional |
| radius | Object defining the search radius for property search. | Required |
| value | Numeric value for radius length. | Required |
| unit | Two-character designation: mile (mi) or kilometer (km). |
Required |
3. JSON – New Pricing Fields in Exchange API
For full advisory details, please visit: Advisory Link
Overview
Previously, the ModifyPrice section in the JSON API GDS Exchange workflow represented the netted financial impact by combining additional collection and residual amounts across base fare, taxes, and change fees. With this enhancement, two new sections are introduced to provide clear, separate values:
- AdditionalCollectionPrice – Total amount to be collected, with breakdowns by base, tax, and change fee.
- ResidualPrice – Total refundable amount, with breakdowns by base, tax, and change fee.
Scope
Travelport+ JSON Exchange API.
Customer Benefit
This enhancement offers customers a clearer view of both additional collection and residual refund amounts, improving compliance and reducing pricing errors.
- BSP Markets: Resolves difficulty in identifying exact add-collect or residual values, helping prevent commit errors.
- ARC Markets: Supports compliance with airline refund and penalty rules (Category 31) and EMD-based penalty collection logic.
Detailed Description
Current JSON Exchange API pricing sections:
- ReferenceListExchangedPrice: Original ticket price
- Price: Price for the requested itinerary change
- SupplierRetainedPrice: Residual amount ignored by the system
- ModifyPrice: Netted financial obligation (positive for additional collection, negative for refund)
The ModifyPrice section currently nets all components (base, refundable tax, additional tax, and change fee), which may conflict with BSP and carrier-specific rules. The enhancement introduces:
- AdditionalCollectionPrice: Total collection amount with breakdowns.
- ResidualPrice: Total refundable amount with breakdowns.
Updated Pricing Guidelines
| Market | Pricing Logic Updates |
|---|---|
| BSP Markets |
|
| ARC Markets |
|
| Carrier/Region Specific | Some carriers (e.g., Aegean) prohibit netting of residual tax and add-collect base |
Summary
These changes ensure the Exchange API adheres to industry standards and carrier-specific requirements, reducing pricing discrepancies and commit failures. Developers are advised to update workflows and logic that rely solely on the ModifyPrice section.
4. Restful API Microservices – Minimum Connecting Time (MCT) Override
For full advisory details, please visit: Advisory Link
Overview
With this implementation, customers can control MCT (Minimum Connecting Time) warnings and choose whether to accept or create the booking. When an MCT warning is returned by the host, the booking is not immediately created via JSON API (unlike current behavior).
Scope
Travelport + GDS. Does not include NDC.
Customer Benefit
Customers gain explicit control over accepting or rejecting bookings and schedule changes that trigger an MCT warning.
Schema Changes
Yes
Impacted Services and Schema
Restful API Microservices v11.25 and above: ReservationQueryCommitReservation and schedule change flows.
Detailed Description
Previously, when a Minimum Connecting Time warning was received during booking creation or upon accepting a schedule change, a double end transaction was sent to the back end and customers had no opportunity to accept/reject. This update introduces two new indicators inside ReservationQueryCommitReservation:
enableTwoStepCommitIndoverrideMCTInd
These provide the ability to either follow the current behavior (create booking immediately) or to perform a two-step commit where the booking is held (cached) until the customer explicitly overrides the MCT warning.
Customer Examples (Best Practices)
Example A – Preserve current JSON behavior (Immediate booking)
If you want the system to create the booking even when an MCT warning is returned, pass both identifiers as true. The booking is created, the MCT warning is included in the final payload, and the session is closed.
Example A request
{
"ReservationQueryCommitReservation": {
"scheduleChangeAcceptedInd": false,
"enableTwoStepCommitInd": true,
"overrideMCTInd": true
}
}Example A error/response (host message)
CONNECTION DURATION IS LESS THAN MINIMUM CONNECTING TIMEExample B – Two-step commit (Customer must accept to create booking)
To control acceptance, use enableTwoStepCommitInd=true and set overrideMCTInd to false (or omit it) in the first commit. The booking is not created but is saved in cache, and a warning is returned. The client must send a second commit with overrideMCTInd=true to create the booking. If the second commit is not sent, the session remains open for 15 minutes (unless ignored).
Example B — First Commit (warning, booking NOT created)
{
"ReservationQueryCommitReservation": {
"scheduleChangeAcceptedInd": false,
"enableTwoStepCommitInd": true,
"overrideMCTInd": false
}
}Example B — Second Commit (override and create booking)
{
"ReservationQueryCommitReservation": {
"scheduleChangeAcceptedInd": false,
"enableTwoStepCommitInd": true,
"overrideMCTInd": true
}
}Example B responses
First Commit Response:
CONNECTION DURATION SHOULD NOT BE LESS THAN MINIMUM CONNECTING TIME. OVERRIDE MCT OR REBOOK
Second Commit Response:
CONNECTION DURATION IS LESS THAN MINIMUM CONNECTING TIME – Booking Created
Notes for Developers
- Ensure your client tracks commit state (first commit = cached, second commit = finalize) and handles timeout behavior (session cached for 15 minutes).
- When
scheduleChangeAcceptedIndistrue, the same two-step behavior applies. - Update integraton tests and error-handling logic to correctly interpret host warning messages vs final errors.
July 2025 – Monthly Bulletin
1. Introducing Our Enhanced LLM-Based Mini Fare Rule Solution
We’re excited to unveil the next-generation Mini Fare Rule (MFR) system—powered by advanced AI/ML and Large Language Model (LLM) technologies. This upgrade enhances the way fare rules (CAT31, CAT33, CAT16) are interpreted, offering greater accuracy, transparency, and automation.
Legacy vs LLM-Based Endpoints
Service Endpoint URLs
| Service | Environment | Legacy URL | LLM URL |
|---|---|---|---|
| MFR | PreProd | https://preprod.itq.in/MiniRule/MiniService.svc/Service1.svc | https://minirulellmstg.itq.in/MiniService.svc/Service1.svc |
| MFR | Prod | https://minirules.itq.in/MiniService.svc/Service1.svc | https://llmmfr.itq.in/MiniService.svc/Service1.svc |
| VR3 | PreProd | https://preprod.itq.in/VR3ServiceUat/Service1.svc/Refund | https://preprod.itq.in/VR3coreUAT/service1.svc/Refund |
| VR3 | Prod | https://vr3service.itq.in/Production/Service1.svc/Refund | https://llmvr3.itq.in/service1.svc/Refund |
What’s New in the LLM-Based System?
- Mandatory Time-Slab Penalties included in all responses
- New Departure Type: "BEFORE DEPARTURE BEYOND TIME" clarifies if penalties apply
- Penalty Discrepancy Indicators for CAT31/CAT33 vs CAT16
- CAT16 Fall-back Logic ensures complete rule coverage
- TraceID included in every response for better traceability
- Improved Error Structure with clear, traceable diagnostics
Key Benefits
- Handles complex and ambiguous fare rules
- Adapts to airline-specific formats and exceptions
- Tracks frequent changes or special cases
- Applies AI-driven contextual understanding
- Delivers accurate, rule-based penalty insights
Important Notice
Note: The legacy Mini Fare Rule system will soon be deprecated. Please integrate the new LLM-based endpoints, especially focusing on Time Window-based penalties and TraceID support to ensure uninterrupted service.
If you need any assistance during integration, we are here to help!
Key Benefits
- Handles complex and ambiguous fare rules
- Adapts to airline-specific formats and exceptions
- Tracks frequent changes or special cases
- Applies AI-driven contextual understanding
- Delivers accurate, rule-based penalty insights
Fare Rule Matrix Example
Download Technical Specifications
2. DA-1068 – Restful API Microservices: Minimum Connecting Time Override
Effective Date: August 28, 2025 – 5:00 PM EDT
Travelport System: Travelport+ (1G)
Reason for Issue: First notification
Overview
With this implementation, customers gain control over the Minimum Connecting Time (MCT) warning behavior when using the Restful API. When an MCT warning is returned by the host, bookings will no longer be auto-created via JSON API. Instead, customers can choose whether to proceed with or reject the reservation.
Impacted Services and Schema
ReservationQueryCommitReservationSchedule Changes- Applies to schema version 11.25 and above
Detailed Description
Previously, when an MCT warning was triggered during booking or schedule change, a double end transaction was silently processed, without customer control.
With this change, two new indicators are introduced under ReservationQueryCommitReservation:
enableTwoStepCommitIndoverrideMCTInd
These fields give customers control to accept or reject the booking based on MCT warnings.
Behavior Example
If you want to preserve the current JSON behavior (i.e., allow booking despite MCT warning), set both indicators to true.
Example A – Request
{
"ReservationQueryCommitReservation": {
"scheduleChangeAcceptedInd": false,
"enableTwoStepCommitInd": true,
"overrideMCTInd": true
}
}Example A – Error Response
CONNECTION DURATION IS LESS THAN MINIMUM CONNECTING TIME3. DA-1072 – Hotel JSON Property Rating Provider Update
Effective Date: June 19, 2025 – 6:00 AM EDT
Travelport System: Travelport+ (1G)
Reason for Issue: First notification
Overview
Travelport Hotel JSON messaging returns property-specific content to users, including ratings from trusted sources. Previously, ratings were provided by NorthStar Travel Management and AAA. With this update, two new rating providers have been added:
- Booking.com
- GIATA GmbH
Scope
Ratings are only returned when available. Despite support for four providers, some properties may not display any ratings. Booking.com ratings will appear only for authorized users. Supported message types include:
- V11 Search
- V11 Details
- V12 SearchComplete
Customer Benefit
Displaying ratings helps travelers compare properties more effectively and make informed booking decisions.
Schema Changes
No schema changes are introduced with this update.
Impacted Services and Schema
The provider field within the Rating (V11) or ratings (V12) array may now include any of the following:
NTM– NorthStar Travel ManagementAAA– AAABooking– Booking.comGIATA– GIATA GmbH
Detailed Description
Whether to display these ratings is up to the user. If your application filters or formats based on the provider value, make sure to support the new values below.
Provider Mapping
| Provider Value | Rating Source |
|---|---|
Booking |
Booking.com |
GIATA |
GIATA GmbH |
4. DA-1080 – Travelport Universal API Release 25.3.1: Release Notes and Defect Fixes
Effective Date: June 26, 2025 – 5:59 PM EDT
Travelport System: Travelport Galileo (1G), Travelport+ (1G)
Reason for Issue: First notification
Overview
This advisory summarizes key enhancements and defect fixes introduced in Travelport Universal API Release 25.3.1.
Schema Changes
No schema changes were introduced with this release.
System Codes
- 1G – Travelport+
- ACH – Airline Content Hub
Key Feature
Segment Status Change for NDC Bookings (Provider: Air, Universal.xsd | System: 1G)
Universal API (SOAP XML Services) now supports retrieval of NDC bookings with segments in ZK and HK status.
When NDC segments are present, the following warning will appear:
<common_v53_0:ResponseMessage Code="101018" Type="Warning">
PNR has NDC segment(s) QF|403,QF|402,QF|401,QF|402. NDC segment(s) cannot be modified or cancelled using UAPI.
</common_v53_0:ResponseMessage>
Attempting to modify such a PNR through Universal API will return an error:
<faultstring>
PNR has NDC segment(s) AA|2364. NDC segment(s) cannot be modified or cancelled using UAPI.
</faultstring>
Users must contact their Travelport Account Representative to opt-in for NDC segment support. Refer to advisory DA-1065 for further details.
5. DA-1079 – JSON API Error Message List
Effective Date: June 24, 2025 – 2:00 PM EDT
Travelport System: Travelport+ (1G)
Reason for Issue: First notification
Overview
A multi-phase update to JSON API error handling was released in June 2024 across all JSON APIs. This update ensures consistent error messaging across GDS and NDC content. The new and revised errors apply to all JSON Air APIs.
This advisory informs developers of the latest error codes. The complete list can be viewed on the official support site.
Customer Benefit
Developers now receive uniform and clearly categorized error responses, helping streamline integration and error resolution workflows.
Impacted Services and Schema
All Travelport JSON APIs.
New Error Messages (Sample)
| Code | Message | Status | Category |
|---|---|---|---|
| 2529 | NDC AIRLINE UNABLE TO PROCESS. RETRY | 200 | Temporary |
| 4460 | TRAVELER EMAIL CANNOT MATCH TRAVEL AGENCY EMAIL | 200 | Validation |
| 4467 | EXTENDED PAYMENT CANNOT BE APPLIED TO MULTIPLE TRAVELERS | 200 | Validation |
Revised Error Messages (Sample)
| Code | Message | Status | Category |
|---|---|---|---|
| 2527 | NDC AIRLINE UNABLE TO PROCESS. RESTART | 200 | Process |
| 4126 | REFUNDED DOCUMENT CANNOT BE VOIDED | 200 | Validation |
| 4455 | RESERVATION IDENTIFIER CANNOT BE BLANK OR NULL. PROVIDE VALID IDENTIFIER | 400 | Validation |
June 2025 - Monthly Bulletin
1. Travelport Universal API Release 25.2.3 Release Notes and Defect Fixes
Advisory Number: DA-1070
Effective Date: May 29, 2025 7pm EDT
High Level Description: Release notes and defect fixes for Release 25.2.3 of Travelport Universal API.
Impact Summary: All customers on all schema versions will benefit from the defect fixes. Please note that only customers who upgrade to the latest schema versions may benefit from enhancements. The expected risk is low.
Overview: Features and defect fixes for Release 25.2.3 of Travelport Universal API.
Schema Changes: No schema changes were made related to the new features or defect fixes.
Release Notes: See the Universal API Help System Release 25.2 Release Notes for further information.
Provider Features
Feature: Segment Status Change for NDC Bookings Retrieved via SOAP XML API Services
Description: On June 26, 2025, Universal API (SOAP XML API Services) will be able to retrieve NDC bookings with segments containing both ZK and HK status.Users who want to retrieve NDC bookings with ZK or HK status returned on NDC segments should reach out to their Travelport Account Representative and opt-in for NDC bookings. See DA-1065 for more details.
ACH - IndiGo Stretch Business Class
Feature: IndiGo Stretch Business Class fares are now accessible.
Description: The delivery is in two phases:
- Phase 1 delivery May 1, 2025 - Does not allow fare combinations.
- Phase 2 delivery June 12, 2025 - Allows for fare combinations.
See DA-1067 for further information.
2. New Segment Status Display for NDC Air Segments
Advisory Number: PA-4517
High Level Description: Travelport+ users will see the NDC air segment status in their Booking as HK. This is a change from the current ZK to new HK status in Travelport+ Passive Booking File.
Impact Summary: No new entries, though this change may affect agency workflows when HK is returned vs ZK. An AAT update is required to allow NDC ZK segments to display as HK.
Overview: When Opted-IN, Travelport+ users will see the NDC air segment status in their Booking as HK. This change from the current ZK to HK status in the Travelport+ Passive Booking File aligns our system more closely with industry standards and improves overall booking accuracy. Agencies can opt in by contacting their Travelport Account Manager or Customer Success Manager.
Customer Benefit: The ZK to HK transition, for NDC Segments, serves as a crucial foundation for our upcoming improvements around Order Change Notification (OCN) related to flight disruption management system and other notifications from the Airline(s) to keep Orders synchronized between Travelport+ and the Airline(s) system. This update prepares our platform for the implementation of airline reply/advice/status codes handling, such as but not limited to UN (Unable-flight doesn't operate) and TK (Confirming/Holds confirmed-Advise passenger of a new scheduled times/details), enhancing our ability to manage flight disruptions effectively. A separate advisory will be released at a later date describing all the improvements around this area. With the implementation of HK status, we anticipate a smoother and more efficient hand-off to back office operations. This improvement will streamline workflows and reduce potential errors in booking management.
This change will benefit users of both Smartpoint Desktop and Smartpoint Cloud. Users will need to be on Smartpoint Desktop v11.7 or higher in order to be able to use the N indicator to open the Flight Search Plugin to service the booking. This change is available on v11.7, released on the 24th April and all future versions.
3. IndiGo Stretch Business Class
Advisory Number: PA-4523
Effective Date: May 01, 2025 5:45pm EDT
High Level Description: Travelport+ customers can now book IndiGo Stretch Business Class Fares.
Impact Summary: Travelport+ customers can now book IndiGo Stretch Business Class Fares. The delivery will be in two phases:
- Phase 1 (May 1, 2025) – Does not allow for fare combinations
- Phase 2 (May 29, 2025) – Allows for fare combinations
Overview
IndiGo Stretch is IndiGo’s new business class service offering wider seats, priority check-in, complimentary meals and drinks.
IndiGo Stretch fares are also combinable with IndiGo Corporate and Super 6E fare types; however, this initial delivery will not allow such combinations.
Note: Stretch combined with Stretch+ will be enabled with the Phase 2 delivery.
A planned subsequent delivery for May 29, 2025 will include fare type combinations. The included ancillary services are outlined below:
Included Services
| Service | Stretch (C) | Stretch Plus (E) |
|---|---|---|
| Seat Selection | Complimentary | Complimentary |
| Meal & Beverage | Complimentary – Standard veg meal box with beverage | Complimentary – Standard veg meal box with beverage |
| Check-in Baggage | 30Kg (2 pcs) | 40Kg (2 pcs) |
| Hand Baggage | 12Kg (1 pc) | 12Kg (1 pc) |
| Fast Forward | Yes | Yes |
4. Cathay Pacific (CX) New Carrier NDC Content Launch
| Advisory Number: | PA-4532 |
| Version: | 1 |
| Effective Date: | June 02, 2025 9am EDT |
| High Level Description: | This advisory details the initial launch of Cathay Pacific (CX) NDC content. |
| Impact Summary: | NDC content is booked through Travelport+ in Smartpoint or via API RESTful/JSON services. |
Overview
NDC content from the carriers listed will be available in the countries listed from the dates indicated below.
| Carrier(s) | From | Accepted Form of Payment | Countries / Timeline |
|---|---|---|---|
| Cathay Pacific (CX) | June 02, 2025 | Cash and Credit Card |
Thailand Vietnam (Q3 2025) Singapore (Jul) France, Switzerland (Jul) Sri Lanka (Q3) India (Mid-Aug) Saudi + UAE (Oct, Q4 2025) |
Please note that NDC content is released on a carrier and country basis in collaboration with the carriers. See the appendix for full details.
Look out for further advisories as we roll out NDC more widely.
Customer Benefit
Future NDC deals will offer better pricing, personalized offers, and bundled ancillaries. Airlines can tailor content based on traveler data, such as loyalty status or corporate IDs.
- Personalized rewards and unique fares.
- Bundles including seats, bags, and other ancillaries.
- Airline-controlled differentiation varies by carrier.
- This advisory focuses on immediate agency benefits, not all airline features.
For more details, visit the full advisory here.
May 2025 - Monthly Bulletin
1. JSON API Price: Kilogram Baggage: Quantity Field Removed
Effective July 21, 2025, JSON API Price will no longer return the quantity field in BaggageItem when baggage is measured in kilograms. This change applies to GDS content and aligns with JSON API Search v11.
Impacted: Reference and Full Payloads
Schema: No model version changes
Details: Read Full Advisory
2. New OTP & Password Reset Email Address
Effective May 12, 2025, OTP and password reset emails will be sent from a new address: noreply@identity.travelport.net, replacing noreplyauth@travelport.com.
Action Required: Customers must allowlist identity.travelport.net and travelport.net to ensure email delivery.
Travelport has updated OTP notifications and shared the info with MyTravelport users on April 24. Operators are asked to proactively inform customers especially IT teams about this change to avoid disruptions.
Communication templates are available via Seismic and the Operator Brand Hub.
3. Oman Air (WY) Fare Class Re-Alignment Notification
Effective: Changes made after April 26 that move travel to June 1 or later must follow the new RBD structure based on updated Oman Air fare rules.
Impacts:
- Tickets issued after April 26 should process normally via Automated Exchanges assuming ATPCO fare updates.
- Tickets issued before April 26 but changed on/after April 26 with travel starting June 1+ may require manual handling.
Action: Please inform relevant users to review the policy and proceed with caution for affected bookings, as automated tools may not reflect accurate calculations.
Refer to the official Oman Air trade notification shared by the airline or contact your Travelport Operator Success Manager for support.
April 2025 - Monthly Bulletin
1. JSON API Price: Quantity Field Removal for KG Baggage
Advisory: DA-1064 | Version: 1
Effective: July 21, 2025, 3pm EDT
Description: JSON API Price will no longer return the quantity field when baggage allowance is in kilograms for GDS content.
Impact: Developers must update code if currently validating quantity for KG-based baggage.
Pre-Prod Load: June 17, 2025, 3pm EDT
Applies to: Reference & Full Payload | Travelport+ (1G)
Benefit: Cleaner baggage data output for KG allowances.
Note: No schema version changes required. Affects only BaggageItem in GDS path.
More Info: Travelport Advisory
2. NEW OTP and Password Reset Email Address for Customers
Effective: May 12, 2025
Whats Happening?
OTP (One-Time Passcode) and password reset emails will now come from noreply@identity.travelport.net instead of noreplyauth@travelport.com.
Reminder: OTP is a temporary code used for verifying identity as part of Multi-Factor Authentication (MFA).
Action Required: Customers must allowlist identity.travelport.net and travelport.net domains to ensure uninterrupted email delivery.
Communication
- MyTravelport users received this update on April 24.
- OTP email content is being updated to reflect the new sender address.
How You Can Help
Please share this information with your customers, especially their IT teams. Allowlisting both domains is critical to avoid disruptions.
A Seismic email template is available for your use and also on the Operator Brand Hub. Use it to inform customers using impacted products as soon as possible.
Thank you for your continued support. For questions, please contact your Travelport Operator Success Manager.
3. Travelport Advanced Notification: Oman Air (WY)
Action: Awareness for Operator Helpdesks, Training Teams, and Connected Customers
By: All Travelport Operators
Deadline: On or before April 25, 2025
Purpose: Oman Air joins Oneworld Alliance Fare Class Re-Alignment (FCR) Notification
Supplier Info
Airline: Oman Air
Supplier Code: WY
Please review the official notification received from Oman Air and share with customers where appropriate. Oman Air should also be notifying trade partners directly.
Key Points
- Voluntary changes made after April 26 that shift travel to June 1 or later must follow the new RBD fare structure.
- Tickets issued after April 26 should align with Oman Air's adjusted ATPCO filings and work with Automated Exchanges.
- Tickets issued before April 26 and reissued after that date for travel after June 1 may require manual processing.
- This change could increase exchange requests that cannot be handled through Automated Exchanges.
Important: Ensure users are aware of this policy update and proceed carefully with affected bookings, as automation may not calculate expected values.
For questions, contact your Travelport Operator Success Manager.
March 2025 - Monthly Bulletin
1. JSON API Search v11 Cross Origin and Destination
With this enhancement, JSON API Search and Next Leg Search for GDS content only and Integrated Search (GDS plus NDC content) return offers that have multi-cities for which one or more are stopovers.
Changes to the JSON API Search and Next Leg Search response for all GDS offers:
- The
“Price”object is not returned. - The
“Surcharges”and“Commission”objects are returned in the“BestCombinablePrice”object, as the“Price”object is no longer returned. The surcharges and commission amounts are for the entire journey. - The
“CombinabilityCode”will return“jc”with a number (starting with“1”) for offers that have multi-cities where one or more have stopovers. For example“jc1”,“jc2”, etc.
Note: This capability does not affect “JSON AirPrice”, “AirReservation”, and “AirTicketing”.
Activation Details
JSON API Search and Next Leg Search v11 customers can request the activation of this capability in pre-production and production system(s) anytime. If you would like to activate this change prior to March 2025, please request this by emailing AirBendersSupport@Travelport.com and copy your Travelport representative indicating the following:
“JSON Search v11 Cross Over 1 Origin and Destination (O&D)”- Requester full name
- Requester e-mail address
- Agency name
- Pseudo City Code
- The environment (pre-prod and production)
The activation can take up to one week.
We recommend activating this in the pre-production environment first, then testing the capability and identifying the changes you need to make. After this, you can request the activation in production.
“JSON API Search”and“Next Leg Search”for GDS content only“Integrated Search”(GDS plus NDC content)
Future Enhancements
- Removal of the
“Price”object from the NDC content “Flight Specific Search v11”(reference-based and full payload)
Customer Benefit
- Return the lowest fares/offers for GDS content for itineraries that have multi-cities for which one or more are stopovers.
- Return the lowest fares/offers for GDS content for itineraries that have side trips.
Further Reference
For more details, please visit: Travelport Advisory
2. JSON API Error Message List
A multi-phase update to JSON API error handling was released in June 2024 across all JSON APIs. Consistent error messages are now returned for all content, including GDS and NDC, across all JSON Air APIs. The updated Error Message List can be viewed at the Error Message support site.
This Developer Advisory is to inform of new and revised error messages supported by JSON APIs.
Customer Benefit
Consistent error messages are returned for all content, including GDS and NDC, across all JSON Air APIs.
Impacted Services and Schema
All Travelport JSON APIs.
Detail and Customer Examples
The following tables list the new and revised error messages returned in the JSON APIs for all objects in Error/Result except SourceID, which may return API, a supplier code, or the GDS code 1G.
Further Reference
For more details, please visit: Travelport Advisory