NDC Guide

This guide discusses general NDC support in the JSON APIs and provides a chart of high-level differences by API. The API references provide object-level details on differences in usage or responses. Throughout the help, differences in how NDC and GDS content are requested and returned are noted where applicable.

To access NDC content you must be provisioned for NDC with Travelport and registered with the NDC airline.

Related Content: JSON APIs Guide, NDC FAQs

In this topic:

NDC Basic Concepts

NDC (New Distribution Capability) is a travel industry standard for the distribution and retailing of flight content. NDC is not a system, database, or piece of software - it is a standard for exchanging data.

What is NDC?

The Travelport JSON Air APIs support both NDC and GDS content, or simply NDC and GDS. These terms refer to the content distribution method:

  • GDS stands for Global Distribution System. A GDS aggregates and distributes air, hotel, and car rental content such as schedules, fares, and upsells. Travelport owns the Galileo, Worldspan, and Apollo GDSs, which are also known by the IATA abbreviations 1G, 1P, and 1V.

  • NDC is for New Distribution Capability, a program launched by the International Air Transport Association (IATA), the trade association for the world's airlines, to facilitate content distribution directly from airlines to online travel agencies. NDC is an XML standard for exchanging data, and is intended to replace the EDIFACT protocol that has been used by Global Distribution Systems (GDS). NDC distributes content directly from airlines to online travel agencies, GDSs, and travel management companies. NDC content is provided and fulfilled directly by the airline, and may include differentiated content available only through the airlines' direct channels.

Although most JSON API workflows, requests, and responses are the same for both GDS and NDC, airline-specific processes do create some differences. Some functionality is supported only for NDC, or only for GDS, as detailed later in this guide. Because NDC is available only to provisioned customers, this online help has a separate NDC top-level menu to group information and processes that apply only to NDC.

If the online help doesn't include the text GDS only; not supported for NDC or vice versa, the functionality presented is supported for both NDC and GDS in the same way. Any differences in NDC and GDS functionality are noted where applicable.
Content for both NDC and GDS in the JSON APIs is sourced from the Galileo GDS (Global Distribution System) for most customers. Starting in April 2023, NDC content from the Apollo and Worldspan GDSs is available to specifically provisioned customers. See the NDC Guide for Apollo and Worldspan.

General NDC & GDS Differences

  • NDC is a shopping-led workflow so there is no availability data. Inventory and price are not guaranteed until the booking is fulfilled.
  • NDC supports the ability to send frequent traveler data at shopping (sent in the Search API request in the CustomerLoyalty object).
  • In NDC the airline controls all data available, including offers, booking, storing, servicing, fulfillment, and ticketing.
  • Involuntary changes are sent using order change notifications and don’t use the AIRIMP codes HK/TK. (Involuntary changes not currently supported in the JSON APIs.)
  • NDC generally allows 20 to 30 minutes to create a booking (the offer time limit). Note that per FAQs and Best Practices, Travelport retains a search in cache for 12 minutes so it can be added as an offer to the workbench. A workbench is valid for 30 minutes and must be committed within that time window or it expires.
  • NDC and GDS ticket time limits are the same; a booking will expire if ticketing doesn't take place within a certain time, usually within 24 hours of booking. NDC airlines do not generally return ticket time limit data.
  • NDC has two ticketing models: Issuing the ticket on the airline's own stock or using FLX stock.

NDC in the JSON APIs

Most workflows, requests, and responses across the JSON APIs work the same for both GDS and NDC content, with minor differences noted in the help where applicable.

The exception is that changes to the air itinerary, and voids, exchanges, and refunds, are handled by separate JSON APIs and follow different workflows. This results from differences in how NDC carriers implement these processes.

The NDC menu at the top of every page groups these NDC-specific APIs. Otherwise, all Guides and API References apply to both NDC and GDS.

General Support

The following table outlines broad areas of support in the JSON APIs. More details are provided in the following sections.

NDC Item

Supported in the JSON APIs

IATA NDC schemas

17.2, 18.1, and 18.2

Itineraries supported

Single airline on a booking, multiple passengers

Payment

Cash, credit card, and banked funds (see Supported Forms of Payment below)

Settlement

ARC and BSP

Travelport booking file

Passive segment (ZK)

Mid and back office

MIR/TAIR (DI lines)

Services

Search, AirPrice, Seats, Ancillaries, AirReservation, AirTicketing, Reservation Divide, Air Modify and Exchange, Reservation Cancel, Ticket Void and Refund

Prerequisites

To access NDC content you must be provisioned for NDC with Travelport and registered with the NDC airline. Validation occurs at these levels when a request for NDC content via any JSON API is received:

  • Validation that the requester is provisioned for NDC within Travelport.
  • Request details are sent to the airline system. Airline validates that the requester is registered with them for NDC content.
  • Aggregated NDC and GDS content is returned as requested.

Participating Carriers

The JSON APIs have been certified to provide NDC content from the following carriers:

  • Qantas (QF)
  • United Airlines (UA)
  • American Airlines (AA)
  • Singapore Airlines (SQ)
  • Air France (AF)
  • KLM (KL)
AF/KLM NDC do not yet support booking seats or ancillaries.

Information about additional carriers will be provided here as they join.

Supported Forms of Payment

The forms of payment and credit card types accepted for NDC content varies by carrier. The tables below list the forms of payment and credit card types supported by each carrier.

Form of Payment Support by NDC Carrier
Airline Cash Credit Card Debit Card

Qantas (QF)

Yes

Yes

Yes (handled same as credit card)

American Airlines (AA)

Yes

Yes

Yes

United Airlines (UA)

No

Yes

Yes (UA does not differentiate between credit and debit cards)

Singapore Airlines (SQ)

Yes

Yes

Yes (handled same as credit card)

Air France (AF)/KLM (KL)

Yes

Yes

Yes (handled same as credit card)

Credit Card Type Support by NDC Carrier

Airline

Visa Mastercard American Express Diners Club JCB UATP Discover Card Universal Air Travel Card

Qantas (QF)

Yes

Yes

Yes

Yes

Yes

No

Yes

Yes

American Airlines (AA)

Yes

Yes

Yes

Yes

Yes

No

Yes

No

United Airlines (UA)

Yes

Yes

Yes (except CO)

Yes (except GB, SE, IN)

Yes (US & JP only)

Yes (US and others, limited)

Yes (US and others, limited)

No

Singapore Airlines (SQ)

Yes

Yes

Yes

Yes

Yes

No

No

No

Air France (AF)/KLM (KL)

Yes

Yes

Yes

Yes

Yes

Yes

No

No

Filed Fares, Passive Booking Record, and MIR

In the traditional GDS distribution channel, Travelport issues the ticket using the GDS ticketing system, while for NDC the airline itself issues the ticket and handles payment and any subsequent changes. Because the NDC carrier maintains its own booking record (also called a PNR), Travelport maintains on its host system a passive booking record or passive PNR . This passive PNR generally mirrors the carrier PNR and allows the JSON APIs to return and store information about the booking. At applicable points in the booking workflow, the JSON APIs synchronize this passive booking record with the carrier's booking record.

With AirReservation 23.11.34 and later, the following handling is applied to filed fares in the passive PNR:

  • Updates handling of filed fare details so that if the price changes between the time of booking and ticketing, the passive booking record reflects the updated price at ticketing.

  • Updates handling of filed fare details so that if there is any change in the itinerary (date change, time change, routing change, etc.) and the airline exchanges the original ticket for a new ticket, the filed fare for the original ticket is canceled and replaced with the filed fare for the exchanged ticket. This ensures the exchange is handed and reported per ARC/BSP standards and that the same information is sent to the MIR (management information report) and the back office system. (In the BSP market, when the original ticket is exchanged for a new ticket, the fare is collected either as a NO ADC or an ADC. In the ARC(US) market, the fare is created with the total values which includes base fare, taxes and total fare.)

In addition, AirReservation 23.11.34 added support to generate a MIR (management information report) for ticket issuance, ticket exchanges, and ticket voids for NDC in the same format as currently exists for GDS ticket issuance and exchange. This ensure consistent mid- and back-office reporting and handling for NDC as well as GDS itineraries.

Filed fares and MIRs are not accessible through the JSON APIs but rather through agency-based software such as Smartpoint Cloud.
All of the above features can be configured on or off in the configuration file settings for your PCC (pseudo city code, provisioned from Travelport). Contact your Travelport representative for assistance with this setting if needed.

NDC by Country

NDC carrier content is available for booking through the JSON APIs in the countries listed below. NDC content is rolled out on a country basis, so check back if your country is not listed, or if content of interest is not available.

Where NDC content is available, your Travelport account manager will ensure you have been enabled for the content. You may need to register directly with the airline to gain access to the NDC content.

Country American Airlines (AA) NDC Qantas Airlines (QF) NDC Singapore Airlines (SQ) NDC Air France (AF) / KLM (KL) NDC
Afghanistan      

 

Albania     Yes

 

Antigua Yes    

 

Argentina Yes    

Yes

Aruba Yes    

 

Australia Yes Yes Yes

 

Austria Yes Yes  

Yes

Bahamas      

 

Bahrain   Yes  

 

Bangladesh     Yes

 

Belarus     Yes

 

Belgium Yes Yes Yes

Yes

Bonaire Yes    

 

Bosnia & Herzegovina     Yes

Yes

Botswana      

 

Brazil Yes    

Yes

Bulgaria     Yes

 

Cambodia (Vietnam)     Yes

 

Canada Yes Yes  

 

Chile Yes    

Yes

China Yes   Yes

 

Colombia Yes    

Yes

Cook Islands      

 

Croatia Yes Yes Yes

Yes

Curacao Yes    

 

Cyprus Yes   Yes

Yes

Czech Republic Yes Yes Yes

Yes

Denmark Yes Yes Yes

Yes

Dominican Republic Yes    

 

Ecuador Yes    

 

Egypt      

 

Eire (Ireland) Yes Yes  

 

Estonia Yes   Yes

Yes

Fiji   Yes  

 

Finland Yes Yes Yes

Yes

France Yes Yes Yes

Yes

French Guiana

 

 

 

Yes

French Polynesia   Yes  

 

Germany Yes Yes Yes

Yes

Ghana      

 

Greece Yes Yes Yes

Yes

Guatemala Yes    

 

Guyana Yes    

 

Hong Kong Yes Yes Yes

 

Hungary Yes Yes Yes

Yes

Iceland     Yes

Yes

India Yes Yes Yes

 

Indonesia   Yes Yes

 

Ireland

 

 

 

Yes

Israel Yes Yes Yes

 

Italy Yes Yes Yes

Yes

Japan Yes Yes Yes

Yes

Jordan Yes Yes  

 

Kenya Yes    

 

Kuwait Yes Yes  

 

Latvia     Yes

Yes

Lebanon Yes Yes  

 

Lesotho   Yes  

 

Lithuania     Yes

Yes

Luxembourg   Yes Yes

Yes

Macau      

 

Macedonia     Yes

Yes

Malaysia   Yes Yes

 

Maldives     Yes

 

Malta   Yes Yes

Yes

Mexico Yes    

 

Moldova Yes   Yes

 

Monaco

 

 

 

Yes

Mongolia      

 

Montenegro Yes Yes Yes

Yes

Myanmar (Thailand)     Yes

 

Namibia   Yes  

 

Nepal     Yes

 

Netherlands Yes Yes Yes

Yes

New Caledonia   Yes    
New Zealand Yes Yes Yes

 

Norway Yes   Yes

Yes

Oman Yes Yes  

 

Pakistan   Yes Yes

 

Papua New Guinea   Yes  

 

Peru Yes    

Yes

Philippines Yes Yes Yes

 

Poland Yes   Yes

Yes

Portugal Yes Yes  

Yes

Qatar Yes Yes  

 

Romania Yes   Yes

Yes

Russia     Yes

 

Saba Yes    

 

Saint Eustatius Yes    

 

Saint Lucia Yes    

 

Saint Maarten Yes    

 

Samoa      

 

Saudi Arabia Yes Yes  

Yes

Serbia Yes Yes Yes

Yes

Singapore Yes Yes Yes

Yes

Slovakia Yes Yes Yes

Yes

Slovenia Yes Yes  

Yes

South Africa Yes Yes Yes

Yes

South Korea Yes Yes Yes

Yes

Spain Yes Yes Yes

Yes

Sri Lanka (India) Yes Yes Yes

 

Suriname Yes Yes  

Yes

Swaziland   Yes  

 

Sweden Yes Yes Yes

Yes

Switzerland Yes Yes Yes

Yes

Taiwan Yes Yes Yes

Yes

Thailand Yes Yes Yes

 

Trinidad & Tobago Yes    

 

Turkey Yes Yes Yes

Yes

Ukraine     Yes

 

United Arab Emirates Yes Yes Yes

Yes

United Kingdom Yes Yes Yes

Yes

United States of America Yes Yes Yes

 

Uruguay      

 

Vietnam Yes Yes Yes

 

Venezuela      

 

Carrier Specific Notes

Qantas:

  • Sending customer loyalty numbers (CustomerLoyalty object) in the Search request is supported only for Qantas. If sent, the response returns the CustomerLoyaltyCredit object in TermsAndConditions.
  • When running a multiple passenger search, Qantas supports only these PTCs: ADT, CHD, CNN, INF. Sending any other PTC may result in an error at ticketing.
  • Qantas supports only one account code. If multiple codes are sent, only the first code is processed.

United Airlines:

  • UA returns baggage text in TermsAndConditionsAir/BaggageAllowance/BaggageItem.

Singapore Airlines:

  • Singapore Airlines returns tax codes but not tax descriptions in responses.
  • OB fees are added to the total fare only if a credit card BIN number is provided in the AirPrice request. If this is not done, and a credit card is then used to ticket the booking which had been held without an FOP or with a FOP different from the one subsequently used to ticket, then ticketing will fail due to price mismatch. Support will be added in a future release to support this workflow and ensure the ticketing does not fail.
  • Singapore Airlines charges OB fees when a credit card is used as a Form of Payment in the following point-of-sale countries: United Kingdom, Netherlands, Australia, New Zealand, and Belgium. For these countries, OB fees are charged when provided with BIN number at the time of Price. OB fees are added to the offer price when the booking is created.

Air France and KLM:

  • Billing address is required with a debit/credit card form of payment.

  • Some Private Fare support must be requested using special PTCs (passenger type codes):

    • For VFR (visit friends and relatives) Private Fares, the fare request in the UK market must use PTC JCB (ADT), JNN (CHD), or JNF (INF).

    • For Tour Operators, the supported passenger types are IIT, INN, and ITF.

NDC Content for Apollo and Worldspan

Content for both NDC and GDS in the JSON APIs is sourced from the Galileo GDS (Global Distribution System) for most customers. Starting in April 2023, NDC content from the Apollo and Worldspan GDSs is available to specifically provisioned customers. See the NDC Guide for Apollo and Worldspan.

NDC and GDS Functionality Comparison Chart

Travelport is an active participant in NDC while still providing a single, consistent workflow for searching, booking, and managing travel. As the NDC technology continues to develop, the JSON APIs handle certain functionality differently between NDC and GDS.

In the traditional GDS distribution channel, Travelport issues the ticket using the GDS ticketing system, while for NDC the airline itself issues the ticket and handles payment and any subsequent changes. Although the general JSON API booking workflow is the same for both GDS and NDC, voids, exchanges, refunds, and certain modifications are handled by separate JSON APIs and use different workflows. This results from differences in how these processes are implemented by the NDC carriers. Seats, ancillaries, and EMD payment processes can also differ for NDC and for individual NDC carriers.

The NDC menu at the top of every page groups these NDC-specific APIs. Otherwise, all Guides and API References apply to both NDC and GDS with differences noted where applicable. General differences are noted in guides, while object-level differences are noted in the API reference for each API.

The following table charts functionality differences between NDC and GDS in the JSON APIs.

API and Functionality

NDC Only

GDS Only

Supported for both with differences

General

Identifier values for system-generated IDs

   

The value returned in responses for Identifier/authority value for GDS is Travelport while for NDC this value is the code for the issuing NDC carrier.

See Identifiers in the JSON APIs for more about identifiers across all JSON APIs.

Identifier values for short IDs

   

NDC and GDS use a different numbering scheme for short identifiers for offers, products, brands, etc., in which NDC incorporates the carrier code while GDS does not.

For example:

  • NDC offer ids on Qantas start as QF_CPO0, QF_CPO1, etc.
  • NDC product ids on Singapore Airlines start as SQp0, SQp1, etc.
  • These numbers for GDS would start with o0 and o1 for offers on all carriers and p0 and p1 for products on all carriers.

See Identifiers in the JSON APIs for more about identifiers across all JSON APIs.

Branded fares

   

Branded fares are returned for both NDC and GDS with the following minor differences:

  • NDC does not return the brand tier.
  • UA and AA do not return an Identifier value.

Net fares net ticket data (NTD)

Several APIs return several objects with NTD for any fare with a private fare component; however, NDC does not support net fares.

 

GDS only

 

Errors and warnings

   

NDC warning and error messages include the carrier code.

Enhanced error handling for NDC is under development; error messages may differ from GDS errors.

AvailabilitySourceCode object (returned in ReferenceList/ReferenceListFlight to assist in troubleshooting)

 

GDS only

Returned in the Search, AirPrice, and AirReservation commit responses for GDS only.

Search

Search Control Console

 

GDS only

 

Sending frequent flyer details in the request (CustomerLoyalty)

NDC only; Qantas only

 

 

Flight Specific Search

 

 

Only the reference payload Flight Specific Search request is supported for NDC. GDS supports both the full and reference payload requests.

Infants per adult passenger    
For NDC carriers, only 1 INF (infant in lap) is allowed per 1 adult PTC. NDC content is not returned if there are more INF than adults.

TravelerGeographicLocation objects residentGeographicCode, specialLargeFamilyResidentDiscountInd, and generalLargeFamilyResidentDiscountInd

NDC only; required to support local citizen fares

   

The following optional indicators in the Search request:

  • excludePenaltiesInd

  • excludeSurchargesInd

  • excludeBaggageFeesInd

  • includeFareCalculationInd

  • excludeUnbundledFaresInd

  • accountCodeFaresOnlyInd

 

GDS only

 

The following pricing modifiers (PricingModifiersAir) in the Search request:

  • Fare restrictions such as excluding the return of fares that are non-refundable or that require an advance purchase.
  • Currency override to override the PCC default currency
  • Net fares (NDC does not support net fares)
  • Fares based on sell or ticket location (sellCity and ticketCity)
  • Whether to return CAT16 change and cancel penalties (excludePenaltiesInd)
  • Return information about only specified brand attributes (BrandAttributeInclusion)
  • Search by departure time range (DepartureTimeRange)
  • Set brand restriction preferences (returnMostRestrictiveBrandInd)
  • Request only fares that meet certain change criteria (ChangeOptions)
  • Request only fares that meet certain refund criteria (RefundOptions)

 

GDS only

 

Refundability and changeabiility options, sent in PricingModifiersAir/FareSelection in the Search request.

 

 

Up to 6 selection criteria can be sent in for NDC; up to 12 are supported for GDS.

The following pricing modifiers (PricingModifiersAir) in the Search request:

  • PromotionalCode

NDC only

   

The following journey modifiers (SearchModifiersAir) in the Search request:

  • Exclude interline connections (NDC does not support interline connections) (excludeInterlineConnectionsInd)
  • Prohibit change of airport (prohibitChangeOfAirportInd)
  • Class of service preferences (ClassOfServicePreference)
  • Cabin preference at the leg level (CabinPreference at the itinerary level is supported for NDC)
  • Exclude ground transportation (excludeGround)
  • Maximum connection duration (MaxConnectionDuration)
  • Maximum overnight time (MaxOvernightDuration)

 

GDS only

 

Applying journey modifiers (SearchModifiersAir) at the leg level in the Search request instead of to the full itinerary.

 

GDS only

 

In the Search response, the following objects are returned only for GDS:

  • ProductBrandOptions/flightRefs
  • Brand/tier
  • PriceBreakdownAir/Commission (returned for GDS if an airline files a commission in a CAT35 fare)
  • PriceBreakdownAir/Surcharges
  • Flight:
    • Departure/terminal
    • Arrival/terminal
    • IntermediateStop
  • subjectToGovernmentApprovalInd indicator

  • secureFlightPassengerDataRequiredInd indicator

  • ReferenceList/Product/PassengerFlight/FlightProduct/ticketDesignator (ticket designators are returned for NDC in FlightProduct/fareBasisCode by appending a slash (/) and the ticket designator after the fare basis code)

  • ReferenceListProduct/Product/FlightSegment/boundFlightsInd (in Next Leg Search)
  • PassengerFlight/FlightProduct/fareTypeCode
 

GDS only

 

In the Search response, the following objects in PriceDetail are returned only for NDC:

  • currencyCode
  • PriceBreakdownAir/Amount/currencyCode
  • PriceBreakdownAir/Amount/Taxes/Tax/description

NDC only

   

The UpsellOffering object in the Search response is returned by default for NDC offers on United Airlines (UA) only when dynamic bundle fares (DBF) are available and NDC content has been requested. Not returned for other NDC carriers.

NDC only; United Airlines only

   

AirPrice

AirPrice request

 

 

While AirPrice is generally an optional but recommended step, it is required for some NDC carriers.

Only the reference payload AirPrice request is supported for NDC.

GDS supports both the full and reference payload requests.

Pricing based on sell location (SellCity)

 

GDS only

 

validateInventoryInd to check availability in requested class of service

  GDS only; NDC carriers already validate inventory at pricing  

Local citizen fares (TravelerGeographicLocation)

 

GDS only

 

Fare calculation ladder (net fares - NDC does not support net fares)

 

GDS only

 

Ancillaries

Support for specific ancillaries (e.g, paid bags, carbon offset)

   

Supported ancillaries differ for NDC and GDS, and by NDC carrier.

See the support section of the Ancillaries and EMDs Guide.

Ancillary workflow support    

Both NDC and GDS ancillaries can be added to an existing reservation.

At this time, only NDC ancillaries can be added during the initial booking session.

See the Ancillaries and EMDs Guide.

Ancillary price

NDC only

   

EMD refund & void

 

GDS only

 

Seats

Seats support in various booking workflows

   

Support varies for NDC and GDS, and by NDC carrier.

See the support section of the Seats Guide.

Request seat map after Search and outside of a workbench session

 

GDS only

 

Request seat map after AirPrice and outside of a workbench session

 

GDS only

 

Seat book response

   

NDC responses return an identifier for each booked seat and no seat details. GDS responses return an identifier plus seat assignment details.

Seats bundled with airfares (UA dynamic bundled fares only); available for shop but not currently available for booking

NDC only; United Airlines only

   

Standalone Fare Rules

Fare rules

   

Fare rule support varies between GDS and NDC.

See the Fare Rules Guide.

AirReservation

Instant Pay workflow (create reservation and issue the ticket in the same initial booking session)

NDC only

   

Add Product booking workflow (alternate workflow that skips the Search and AirPrice requests that usually initiate the JSON APIs workflow; includes the Add Product and Standalone Price requests)

 

GDS only

 

Add Offer request

 

 

Only the reference payload Add Offer request is supported for NDC.

GDS supports both the full and reference payload requests.

Pricing modifiers in Add Offer request

 

GDS only

 

Add offer to reservation with expired booking

 

GDS only

 

Add Traveler Telephone/extension object

 

GDS only

 
Sending the account code/corporate ID number at workbench commit, if that code was sent as a pricing modifier in OrganizationInformation/OrganizationIdentifier in the Search request. 

NDC only

   

Add Form of Payment (FOP):

  • Adding FOP during hold and pay (NDC supports FOP only in the instant pay and ticketing flows)

  • Non-standard credit cards FOP

  • Cash FOP

  • Agent invoice FOP

  • Multiple FOP on one reservation

 

GDS only

 

Add Form of Payment credit card CVV

 

 

Required for NDC, optional for GDS.

In the workbench commit:

  • In the request, sending scheduleChangeAcceptedInd to accept a flight schedule change.

  • In the request, sending Notification/Date to update or delete the ticketing time limit date.

  • In the response, returning a notification message if the flight time or fare has changed since the offer was added.

 

GDS only

 

Reservation Retrieve request:

  • Request reservation details by ticket number with identifierType parameter (only the retrieve by reservation locator is supported for NDC)

  • Request the return of brand attributes (viewBrandCompleteInfoInd)

  • Request the return of additional baggage details (viewBaggageDetailInd)

 

GDS only

 

The following are not returned in the reservation retrieve response for NDC:

  • Fare rules
  • Certain ticketing information including terms and conditions specific to ticketing, and ticketing time limits. NDC does not return the notificationDate object, which returns the ticketing time limit.
  • Tax code description
  • subjectToGovernmentApprovalInd indicator
  • secureFlightPassengerDataRequiredInd indicator

 

GDS only

 

Modify air itinerary on a reservation

NDC only

 

 

Modify passenger name

NDC only; carrier support varies

 

 

Shell bookings (a reservation that does not have any air segments booked and contains only traveler details)

 

GDS only

 

Reservation cancel

   

Canceling a reservation for NDC requires a workbench session and a cancel request that sets the RetainFlag parameter to false to indicate the cancel operation.

Send a single request to cancel a GDS reservation. Does not use RetainFlag.

Remarks & Service Requests

Specific remarks:

  • Minimum secure flight SSR
  • Form of ID (FOID) SSR
  • Child DOB (SSR CHLD)
  • Document override remarks, including traveler-specific commission

 

GDS only

See the Remarks and Service Requests Guide / API Reference for detailed remark/SSR support and carrier-specific details.

Additional request in the same workbench session to add or delete same type of remark

   

On an existing reservation, to send an additional request for the same type of item (such as deleting an SSR and adding a new SSR, or deleting two SSRs):

  • For GDS you can make multiple adds or deletes for in the same workbench session, but you must retrieve the workbench between each request.

  • For NDC you can add or delete only one of the same type of item per workbench commit.

AirTicketing

Apply the balance on an unused ticket as form of payment to a separate booking

NDC only; AA only

   

Display fees in the Workbench Commit response

 

GDS only

 

Ticket void, cancel, and refund

   

For NDC, use the same process to void a ticket or cancel and issue a refund, depending on whether the ticket is inside the allowable void period.

For GDS, at this time only ticket void is supported for GDS. Cancel/refund functionality for GDS is under development.

Air Modify, Exchanges, and Refunds

Air modify and exchanges

   

Use the NDC Air Modify and Exchange APIs (Reshop and Reprice) to modify the air itinerary on an NDC reservation, or to exchange an NDC ticket.

Use the GDS Exchange APIs (Exchange Eligibility, Search, and Ticketing) to exchange a GDS ticket. Modifying the air itinerary for a GDS reservation is not supported; you must cancel and rebook.

Refunds

NDC only