Skip to main content

Revalidate Itinerary

5.4.0
Air
Search
REST API
Try now
release_note
  • The API Request is now enhanced with the following new features:
  • New REST JSON API response format - Grouped Itinerary Response (GIR). Note: OTA JSON Response type is no longer available with the new version.
  • Branded Fare Attributes - request associated brand attributes.
  • Exclude Non-Branded Fares - allows for only branded fares to be returned when requesting single or multiple brands.
  • Alternate Airport Cross Border Indicator - allow alternate airports to be in other country than the main city-pair when mileage is used.
  • Shop by Fare Basis Code – exclude a fare option based on Fare Basis Code.
  • Shop by Class of Service – exclude a fare option based on Class of Service (Reservation Booking Designator).
  • Shop with Parity Mode – allows to control the brand parity mode for the lowest fare returned.
  • Enhanced Multi-Ticket – allows to specify the requested number of One-Way solutions in Multi-Ticket processing.
  • Multiple Branded Fares at Multiple Fares Per Itinerary level - the existing parameter related to Multiple Brands are now also applicable for Multiple Fares Per Itinerary.

API Information

Response Format
JSON
Method/Endpoint
/v5.4.0/shop/flights/revalidate
Current Version
5.4.0
Target Audience
TN
Environment
Production

What's New

  • The API Request is now enhanced with the following new features:
  • New REST JSON API response format - Grouped Itinerary Response (GIR). Note: OTA JSON Response type is no longer available with the new version.
  • Branded Fare Attributes - request associated brand attributes.
  • Exclude Non-Branded Fares - allows for only branded fares to be returned when requesting single or multiple brands.
  • Alternate Airport Cross Border Indicator - allow alternate airports to be in other country than the main city-pair when mileage is used.
  • Shop by Fare Basis Code – exclude a fare option based on Fare Basis Code.
  • Shop by Class of Service – exclude a fare option based on Class of Service (Reservation Booking Designator).
  • Shop with Parity Mode – allows to control the brand parity mode for the lowest fare returned.
  • Enhanced Multi-Ticket – allows to specify the requested number of One-Way solutions in Multi-Ticket processing.
  • Multiple Branded Fares at Multiple Fares Per Itinerary level - the existing parameter related to Multiple Brands are now also applicable for Multiple Fares Per Itinerary.

Business Value

  • Each of these enhancements enable greater personalization and efficiency to further refine the search and response structure.

New Features

In the Request

Optional

Parameter: NonBrandedFares

Type: complexType

Description: New Parameter to allow to exclude non-branded fares in the shopping response. When the PreferLevel is set to “Preferred" this means “Use non-branded fares”. If this is single filter (no other preferred elements) the meaning is “Use ONLY non-branded fares”. If other preferred filters are also used the meaning is “Use non-branded fares or fares with given (in filters) brands”. When the PreferLevel is set to “Unacceptable" this means “Do not use non-branded fares”. If this is single filter (no other unacceptable elements) the meaning is “Use ONLY branded fares – skip all non-branded”. If other unacceptable filters are also used the meaning is “Use only branded fares excluding fares matching given (in filters) brands”.

Sample Value:

{
	"PriceRequestInformation": {
		"TPA_Extensions": {
			"BrandedFareIndicators": {
				"SingleBrandedFare": "true",
				"BrandFilters": {
					"Brand": {
						"Code": "A3",
						"PreferLevel": "Unacceptable"
					},
					"NonBrandedFares": {
						"PreferLevel": "Preferred"
					}
				}
			}
		}
	}
}
Note: In the Revalidate Itinerary schema version 5.4.0, the NonBrandedFares were added in all 4 levels: Main fare, Main fare leg, Flex fare, Flex fare leg. This section covers Main Fare. Used to indicate a level of preference for an associate item: unacceptable or preferred.

Functional Updates And Enhancements

In the Request

Optional

Parameter: BrandFilters

Type: BrandFiltersType

Description: Defines preferred or excluded brand type codes for main fare leg.

Sample Value:

 
Note: Simplification of the schema. For the BrandFilters attribute, the extra choice of BrandFiltersType has been reduced to NonBrandedFares or Brand choice.

Relase note ID: 13780


  • Revalidate Itinerary has been enhanced with the following new optional search parameters:
  • Shop by Fare Type Code – to support the capability for shopping to include/exclude a fare option based on Fare Type Code.
  • Shop by Brand ID Code – to support the capability for shopping to include/exclude a fare option based on Brand ID code.

API Information

Response Format
JSON
Method/Endpoint
Current Version
4.3.0
Target Audience
TN
Environment
Production

What's New

  • Revalidate Itinerary has been enhanced with the following new optional search parameters:
  • Shop by Fare Type Code – to support the capability for shopping to include/exclude a fare option based on Fare Type Code.
  • Shop by Brand ID Code – to support the capability for shopping to include/exclude a fare option based on Brand ID code.

Business Value

  • Each of these enhancements enable greater personalization and efficiency to further refine the search.

New Features

In the Request

Optional

Parameter: FareType Code

Type: FareTypePrefType

Description: New parameters to support the capability for shopping to include/exclude a fare option based on Fare Type Code. The parameter to be used in a search for the whole journey.

Sample Value:

{
	"TravelPreferences": {
		"TPA_Extensions": {
			"FareType": [
				{
					"@Code": "EOU",
					"@PreferLevel": "Preferred"
				},
				{
					"@Code": "ERU",
					"@PreferLevel": "Unacceptable"
				}
			]
		}
	}
}
Note: New parameter at the shopping, to filter fares by Fare Type Code filters out all unbundled (basic economy fares) which are fares filed with a fare type code = EOU (economy one-way unbundled) or ERU (economy return unbundled).
Parameter: FareType Code

Type: FareTypePrefType

Description: New parameters to support the capability for shopping to include/exclude a fare option based on Fare Type Code. The parameter to be used in a search, at the leg level.

Sample Value:

{
	"OriginDestinationInformation": {
		"@RPH": 1,
		"DepartureDateTime": "2018-10-10T00:00:00",
		"OriginLocation": {
			"@LocationCode": "DFW"
		},
		"DestinationLocation": {
			"@LocationCode": "KRK"
		},
		"TPA_Extensions": {
			"SegmentType": {
				"@Code": "O"
			},
			"FareType": [
				{
					"@Code": "EOU",
					"@PreferLevel": "Preferred"
				},
				{
					"@Code": "ERU",
					"@PreferLevel": "Preferred"
				}
			]
		}
	}
}
Note: New parameter at the shopping, to filter fares by Fare Type Code filters out all unbundled (basic economy fares) which are fares filed with a fare type code = EOU (economy one-way unbundled) or ERU (economy return unbundled).
Parameter: Brand Code

Type: BrandCodePrefType

Description: New parameter to support the capability for shopping to include/exclude a fare option based on Brand ID code. The parameter to be used in a search for the whole journey.

Sample Value:

{
	"PriceRequestInformation": {
		"TPA_Extensions": {
			"BrandedFareIndicators": {
				"@SingleBrandedFare": "true",
				"BrandFilters": {
					"Brand": [
						{
							"@Code": "A3",
							"@PreferLevel": "Preferred"
						},
						{
							"@Code": "A2",
							"@PreferLevel": "Preferred"
						}
					]
				}
			}
		}
	}
}
Note: If brand filters are used in either single brand mode or multiple brand mode both cheapest and upsells fares will be considered for filtering. If “preferred” brands are given then only branded fares matching the brand codes will be returned. If “unacceptable” brands are given then branded fares matching this brand codes will be excluded (non-branded will stay in processing).
Parameter: Brand Code

Type: BrandCodePrefType

Description: New parameter to support the capability for shopping to include/exclude a fare option based on Brand ID code. The parameter to be used in a search, at the leg level.

Sample Value:

{
	"OriginDestinationInformation": {
		"@RPH": 1,
		"DepartureDateTime": "2018-10-10T00:00:00",
		"OriginLocation": {
			"@LocationCode": "DFW"
		},
		"DestinationLocation": {
			"@LocationCode": "KRK"
		},
		"TPA_Extensions": {
			"SegmentType": {
				"@Code": "O"
			},
			"BrandFilters": {
				"Brand": [
					{
						"@Code": "A2",
						"@PreferLevel": "Preferred"
					},
					{
						"@Code": "A3",
						"@PreferLevel": "Preferred"
					}
				]
			}
		}
	}
}
Note: If brand filters are used in either single brand mode or multiple brand mode both cheapest and upsells fares will be considered for filtering. If “preferred” brands are given then only branded fares matching the brand codes will be returned. If “unacceptable” brands are given then branded fares matching this brand codes will be excluded (non-branded will stay in processing).

Relase note ID: 13864


  • Revalidate Itinerary has been enhanced with the following new optional search parameters:
  • Revalidate Itinerary – To control the availability validation for a given itinerary.
  • Branded Fares Optimization – To control the brand parity logic preference (leg or itinerary parity, number of up-sells, allow brand-less legs and fallback modes).
  • Additionally, the following information will be returned in the Revalidate Itinerary response:
  • Forced Stopover Indicator – New indicator at the segment level to denote stopover point.
  • Revalidate Itinerary – Renamed element from "repriced" to "revalidated".

API Information

Response Format
JSON
Method/Endpoint
RevalidateItinRQPOST v4.2.0/shop/flights/revalidate
Current Version
4.2.0
Target Audience
TN
Environment
Production

What's New

  • Revalidate Itinerary has been enhanced with the following new optional search parameters:
  • Revalidate Itinerary – To control the availability validation for a given itinerary.
  • Branded Fares Optimization – To control the brand parity logic preference (leg or itinerary parity, number of up-sells, allow brand-less legs and fallback modes).
  • Additionally, the following information will be returned in the Revalidate Itinerary response:
  • Forced Stopover Indicator – New indicator at the segment level to denote stopover point.
  • Revalidate Itinerary – Renamed element from "repriced" to "revalidated".

Business Value

  • Each of these new parameters power new ways to market, shop and convert lookers to bookers.

New Features

In the Request

Optional

Parameter: AlwaysCheckAvailability

Type: Boolean

Description: This parameter allows customers to control the availability validation for a given itinerary.

Sample Value:

{
	"TravelPreferences": {
		"VendorPref": {
			"PreferLevel": "Preferred",
			"Code": "EK"
		},
		"TPA_Extensions": {
			"VerificationItinCallLogic": {
				"Value": "M",
				"AlwaysCheckAvailability": "true"
			}
		}
	}
}
Note: Applicable only to Revalidate Itinerary functionality.
Parameter: UpsellLimit

Type: Integer

Description: New parameter to limit the number of branded fare upsell solutions to be returned.

Sample Value:

{
	"PriceRequestInformation": {
		"AccountCode": {
			"Code": "BD001"
		},
		"TPA_Extensions": {
			"BrandedFareIndicators": {
				"MultipleBrandedFares": "true",
				"SingleBrandedFare": "true",
				"ParityMode": "Leg",
				"UpsellLimit": 2
			}
		}
	}
}
Note:
Parameter: ItinParityBrandlessLeg

Type: Boolean

Description: New parameter to allow for brand-less leg solutions when itinerary parity is requested.

Sample Value:

{
       "TPA_Extensions": {
              "BrandedFareIndicators": {
                     "MultipleBrandedFares": "true",
                     "ItinParityBrandlessLeg": "true",
                     "ParityMode": "Itin"
              }
       }
}
 
}
Note:
Parameter: ParityMode

Type: String

Description: New parameter to control the brand parity logic preference (Leg Parity or Itinerary Parity).

Sample Value:

{
	"TPA_Extensions": {
		"Priority": {
			"Price": {
				"Priority": 2
			},
			"DirectFlights": {
				"Priority": 1
			},
			"Time": {
				"Priority": 3
			},
			"Vendor": {
				"Priority": 4
			}
		},
		"BrandedFareIndicators": {
			"MultipleBrandedFares": "true",
			"SingleBrandedFare": "true",
			"ParityMode": "Itin",
			"ItinParityFallbackMode": "LowestSingle"
		}
	}
}
Note: ParityMode and ItinParityFallbackMode parameters are optional. When specifying the ParityMode=”Itin” at the request level without specifying the ItinParityFallbackMode, then the default fallback mode in the “BFM rule” level will be applied. Possible fallback modes: LowestSingle (no upsell options only lowest single possible branded solutions) or Leg (upsells generated using leg parity mode).
Parameter: ItinParityFallbackMode

Type: String

Description: New parameter to control the fall back mode logic when brand itinerary parity cannot be met (lowest single brand or leg parity).

Sample Value:

{
	"TPA_Extensions": {
		"Priority": {
			"Price": {
				"Priority": 2
			},
			"DirectFlights": {
				"Priority": 1
			},
			"Time": {
				"Priority": 3
			},
			"Vendor": {
				"Priority": 4
			}
		},
		"BrandedFareIndicators": {
			"MultipleBrandedFares": "true",
			"SingleBrandedFare": "true",
			"ParityMode": "Itin",
			"ItinParityFallbackMode": "LowestSingle"
		}
	}
}
Note: Possible FallBack modes to be used are: LowestSingle (no upsell options only lowest single possible branded solutions) or Leg (upsells generated using leg parity mode).

In the Response

Optional

Parameter: RequestedStopover Ind

Type: Boolean

Description: Indicator to identify which segment is the one departing from the stopover point in the Revalidate Itinerary response (within one leg).

Sample Value:

{
	"FlightSegment": {
		"DepartureDateTime": "2018-08-12T16:50:00",
		"ArrivalDateTime": "2018-08-12T20:20:00",
		"StopQuantity": 0,
		"FlightNumber": 872,
		"ResBookDesigCode": "V",
		"ElapsedTime": 150,
		"DepartureAirport": {
			"LocationCode": "LHR",
			"TerminalID": 5
		},
		"ArrivalAirport": {
			"LocationCode": "KRK"
		},
		"OperatingAirline": {
			"Code": "YY",
			"FlightNumber": 872
		},
		"Equipment": {
			"AirEquipType": 320
		},
		"MarketingAirline": {
			"Code": "YY"
		},
		"MarriageGrp": "O",
		"DepartureTimeZone": {
			"GMTOffset": 1
		},
		"ArrivalTimeZone": {
			"GMTOffset": 2
		},
		"TPA_Extensions": {
			"eTicket": {
				"Ind": "true"
			},
			"Mileage": {
				"Amount": 889
			},
			"RequestedStopover": {
				"Ind": "true"
			}
		}
	}
}
Note:

Functional Updates And Enhancements

In the Response

Optional

Parameter: Revalidated

Type: Boolean

Description: Indicator to identify the itinerary offer that was validated.

Sample Value:

{
	"AirItineraryPricingInfo": {
		"PricingSource": "WPNI1_ITIN",
		"PricingSubSource": "MIP",
		"Revalidated": "true",
		"FareReturned": "true",
		"ItinTotalFare": {
			"BaseFare": {
				"Amount": 9254.00,
				"CurrencyCode": "EUR",
				"DecimalPlaces": 2
			},
			"FareConstruction": {
				"Amount": 11364.48,
				"CurrencyCode": "NUC",
				"DecimalPlaces": 2
			},
			"EquivFare": {
				"Amount": 11070.00,
				"CurrencyCode": "USD",
				"DecimalPlaces": 2
			},
			"Taxes": {
				"Tax": {
					"TaxCode": "TOTALTAX",
					"Amount": 1256.40,
					"CurrencyCode": "USD",
					"DecimalPlaces": 2
				}
			},
			"TotalFare": {
				"Amount": 12326.40,
				"CurrencyCode": "USD",
				"DecimalPlaces": 2
			}
		}
	}
}
Note: When the @Revalidated parameter is included with the ‘true’ value in the response this means the system revalidated the given itinerary with the specified flight schedule, RBD, date of travel and city-pair.

Relase note ID: 12928


  • Revalidate Itinerary has been enhanced to enable more flexibility within the request and return additional information in the response as follows:
  • Return only options with at least one free bag.
  • Exclude codeshare flights.
  • Also, the following information will be returned in the response:
  • More details in the Selling Fare Data applicable to Agency Retailer.
  • Extended Ancillary Fee Groups with ancillary subcode(s), type(s) and hints for up to 10 standard bags.

API Information

Response Format
JSON
Method/Endpoint
RevalidateItinRQv4.1.0/shop/flights/revalidate
Current Version
4.1.0
Target Audience
TN
Environment
Production

What's New

  • Revalidate Itinerary has been enhanced to enable more flexibility within the request and return additional information in the response as follows:
  • Return only options with at least one free bag.
  • Exclude codeshare flights.
  • Also, the following information will be returned in the response:
  • More details in the Selling Fare Data applicable to Agency Retailer.
  • Extended Ancillary Fee Groups with ancillary subcode(s), type(s) and hints for up to 10 standard bags.

Business Value

  • These enhancements drive greater transparency for baggage allowance and charges and a better schedule filtering options with the exclude codeshares parameter.

New Features

In the Request

Optional

Parameter: FreePieceRequired

Type: Boolean

Description: Indicator to specify only fare options that include a bag in the fare filed to be returned. Exclude any fares that do not include at least one free bag. The parameter to be used in a search, at the leg level.

Sample Value:

{
	"TravelPreferences": {
		"TPA_Extensions": "",
		"Baggage": {
			"FreePieceRequired": "false",
			"RequestType": "A"
		}
	}
}
Note: Only options with free pieces will be returned. It is required to specify the baggage Request type “A” - Allowance or “C” - Charges in the request, to shop for a free bag.
Parameter: FreePieceRequired

Type: Boolean

Description: Indicator to specify whether only fare options that include a bag in the fare filed should be returned. Exclude any fares that do not include at least one free bag. The parameter to be used in a search for the whole journey.

Sample Value:

{
	"TravelPreferences": {
		"TPA_Extensions": {
			"Baggage": {
				"RequestType": "A",
				"FreePieceRequired": "true"
			}
		}
	}
}
Note: Only options with free pieces will be returned. It is required to specify the baggage Request type “A” - Allowance or “C” - Charges in the request, to shop for a bag.
Parameter: CodeShareIndicator

Type: CodeShareIndicator

Description: Ability to filter out codeshare flights. This new option is available with two attributes: “ExcludeCodeshare” removes codeshare flights. The same Marketing/Operating (base flights), can be combined with “KeepOnlines” to also return the online flights that are codeshare, for more diversity.

Sample Value:

{
	"TravelPreferences": {
		"TPA_Extensions": {
			"CodeShareIndicator": {
				"ExcludeCodeshare": "true",
				"KeepOnlines": "false"
			}
		}
	}
}
Note:

In the Response

Required

Parameter: BaggageID

Type: BaggageIDType

Description: Baggage ID number for the applicable baggage hints.

Sample Value:

{
	"OrderStandardBag": {
		"PassengerBags": {
			"Code": "ADT",
			"BaggageSequenceOrder": [
				{
					"BaggageID": 1,
					"StandardBag": 1
				},
				{
					"BaggageID": 2,
					"StandardBag": 2
				},
				{
					"BaggageID": 3,
					"StandardBag": 3
				}
			]
		}
	}
}
Note:
Parameter: StandardBag

Type: Short

Description: Standard baggage hint: for example, “1” is the first standard baggage, “2” is the second standard baggage.

Sample Value:

{
	"OrderStandardBag": {
		"PassengerBags": {
			"Code": "ADT",
			"BaggageSequenceOrder": [
				{
					"BaggageID": 1,
					"StandardBag": 1
				},
				{
					"BaggageID": 2,
					"StandardBag": 2
				},
				{
					"BaggageID": 3,
					"StandardBag": 3
				}
			]
		}
	}
}
Note:

Optional

Parameter: NoMarkupBaseFare

Type: Boolean

Description: Applicable to Agency Retailer subscribers. Indicates the original base selling fare, which can include any Fare Retailer Net fare Mark ups plus any Fare Retailer Handling Fees. Excludes all Fare Retailer Selling rule adjustments.

Sample Value:

{
	"NoMarkupBaseFare": {
		"Amount": 161.00,
		"CurrencyCode": "USD"
	}
}
Note:
Parameter: HiddenHandlingFee

Type: Boolean

Description: Applicable to Agency Retailer subscribers. Indicates whether a Fare Retailer hidden Handling fee rule was applied.

Sample Value:

{
	"SellingFareData": {
		"LayerTypeName": "ART",
		"HiddenHandlingFee": "true",
		"HandlingMarkupSummary": [
			{
				"TypeCode": "A",
				"Description": "3PCT",
				"ExtendedDescription": "HAND BSE",
				"MonetaryAmountValue": 0.56,
				"HiddenHandlingFee": "true"
			},
			{
				"TypeCode": "C",
				"Description": "HAND PTK",
				"ExtendedDescription": "HAND PTK",
				"MonetaryAmountValue": 15.00,
				"HiddenHandlingFee": "true"
			},
			{
				"TypeCode": "E",
				"Description": "2PCT",
				"ExtendedDescription": "HAND TTL",
				"MonetaryAmountValue": 0.97,
				"HiddenHandlingFee": "true"
			}
		]
	}
}
Note:
Parameter: NonHiddenHandlingFee

Type: Boolean

Description: Applicable to Agency Retailer subscribers. Indicates whether a Fare Retailer non-hidden Handling Fee rule was applied.

Sample Value:

{
	"SellingFareData": {
		"LayerTypeName": "ART",
		"NonHiddenHandlingFee": "true",
		"HandlingMarkupSummary": {
			"TypeCode": "B",
			"Description": "5PCT",
			"ExtendedDescription": "HAND BSE",
			"MonetaryAmountValue": 1.00,
			"NonHiddenHandlingFee": "true"
		}
	}
}
Note:
Parameter: FareRetailerRule

Type: Boolean

Description: Applicable to Agency Retailer subscribers. Indicates whether a Fare Retailer-Selling level rule was applied.

Sample Value:

{
	"HandlingMarkupSummary": {
		"TypeCode": "J",
		"Description": "ADJT AMT",
		"ExtendedDescription": "ADJT AMT",
		"MonetaryAmountValue": 6.04,
		"FareRetailerRule": "true"
	}
}
Note:
Parameter: AncillaryTypeCode

Type: String

Description: AncillaryTypeCode that corresponds to a type of ancillary, type F or P (treated as F) and is being displayed for all ancillary groups.

Sample Value:

{
	"AncillaryFeeGroup": {
		"Code": "BG",
		"Name": "BAGGAGE",
		"AncillaryFeeItem": [
			{
				"Amount": 25.00,
				"Description": "1ST ADDITIONAL BAG",
				"OriginAirport": "AMS",
				"DestinationAirport": "LHR",
				"Carrier": "K0",
				"PassengerCode": "ADT",
				"Date": "2018-04-10",
				"StartSegment": 1,
				"EndSegment": 1,
				"AncillaryTypeCode": "F",
				"Subcode": "0CC",
				"BaggageID": 1
			},
			{
				"Amount": 45.00,
				"Description": "2ND ADDITIONAL BAG",
				"OriginAirport": "AMS",
				"DestinationAirport": "LHR",
				"Carrier": "K0",
				"PassengerCode": "ADT",
				"Date": "2018-04-10",
				"StartSegment": 1,
				"EndSegment": 1,
				"AncillaryTypeCode": "F",
				"Subcode": "0CD",
				"BaggageID": 2
			},
			{
				"Amount": 45.00,
				"Description": "3RD OR MORE ADDITIONAL BAG",
				"OriginAirport": "AMS",
				"DestinationAirport": "LHR",
				"Carrier": "K0",
				"PassengerCode": "ADT",
				"Date": "2018-04-10",
				"StartSegment": 1,
				"EndSegment": 1,
				"AncillaryTypeCode": "F",
				"Subcode": "0CE",
				"BaggageID": 3
			},
			{
				"Amount": 30.80,
				"Description": "RUCKSACK OR KNAPSACK",
				"OriginAirport": "AMS",
				"DestinationAirport": "LHR",
				"Carrier": "K0",
				"PassengerCode": "ADT",
				"Date": "2018-04-10",
				"StartSegment": 1,
				"EndSegment": 1,
				"AncillaryTypeCode": "F",
				"Subcode": "0EB",
				"BaggageID": 4
			}
		]
	}
}
Note: If one of the records is F type and another P (treated as F) and both have the same subcode, P type will take precedence.
Parameter: Subcode

Type: String

Description: Optional service industry subcodes that are being displayed for all ancillary groups.

Sample Value:

{
	"AncillaryFeeGroup": {
		"Code": "BG",
		"Name": "BAGGAGE",
		"AncillaryFeeItem": [
			{
				"Amount": 25.00,
				"Description": "1ST ADDITIONAL BAG",
				"OriginAirport": "AMS",
				"DestinationAirport": "LHR",
				"Carrier": "KL",
				"PassengerCode": "ADT",
				"Date": "2018-04-10",
				"StartSegment": 1,
				"EndSegment": 1,
				"AncillaryTypeCode": "F",
				"Subcode": "0CC",
				"BaggageID": 1
			},
			{
				"Amount": 45.00,
				"Description": "2ND ADDITIONAL BAG",
				"OriginAirport": "AMS",
				"DestinationAirport": "LHR",
				"Carrier": "KL",
				"PassengerCode": "ADT",
				"Date": "2018-04-10",
				"StartSegment": 1,
				"EndSegment": 1,
				"AncillaryTypeCode": "F",
				"Subcode": "0CD",
				"BaggageID": 2
			},
			{
				"Amount": 45.00,
				"Description": "3RD OR MORE ADDITIONAL BAG",
				"OriginAirport": "AMS",
				"DestinationAirport": "LHR",
				"Carrier": "KL",
				"PassengerCode": "ADT",
				"Date": "2018-04-10",
				"StartSegment": 1,
				"EndSegment": 1,
				"AncillaryTypeCode": "F",
				"Subcode": "0CE",
				"BaggageID": 3
			},
			{
				"Amount": 30.80,
				"Description": "RUCKSACK OR KNAPSACK",
				"OriginAirport": "AMS",
				"DestinationAirport": "LHR",
				"Carrier": "KL",
				"PassengerCode": "ADT",
				"Date": "2018-04-10",
				"StartSegment": 1,
				"EndSegment": 1,
				"AncillaryTypeCode": "F",
				"Subcode": "0EB",
				"BaggageID": 4
			}
		]
	}
}
Note: List of standard ATPCO subcodes: 0CC, 0CD, 0CE, 0CF, 0CG, 0CH, 0CI, 0CJ, 0CK, 0EN.
Parameter: BaggageID

Type: BaggageIDType

Description: Baggage ID number that follows the current hierarchy in sorting Air Extras.

Sample Value:

{
	"AncillaryFeeGroup": {
		"Code": "BG",
		"Name": "BAGGAGE",
		"AncillaryFeeItem": [
			{
				"Amount": 25.00,
				"Description": "1ST ADDITIONAL BAG",
				"OriginAirport": "AMS",
				"DestinationAirport": "LHR",
				"Carrier": "KL",
				"PassengerCode": "ADT",
				"Date": "2018-04-10",
				"StartSegment": 1,
				"EndSegment": 1,
				"AncillaryTypeCode": "F",
				"Subcode": "0CC",
				"BaggageID": 1
			},
			{
				"Amount": 45.00,
				"Description": "2ND ADDITIONAL BAG",
				"OriginAirport": "AMS",
				"DestinationAirport": "LHR",
				"Carrier": "KL",
				"PassengerCode": "ADT",
				"Date": "2018-04-10",
				"StartSegment": 1,
				"EndSegment": 1,
				"AncillaryTypeCode": "F",
				"Subcode": "0CD",
				"BaggageID": 2
			},
			{
				"Amount": 45.00,
				"Description": "3RD OR MORE ADDITIONAL BAG",
				"OriginAirport": "AMS",
				"DestinationAirport": "LHR",
				"Carrier": "KL",
				"PassengerCode": "ADT",
				"Date": "2018-04-10",
				"StartSegment": 1,
				"EndSegment": 1,
				"AncillaryTypeCode": "F",
				"Subcode": "0CE",
				"BaggageID": 3
			},
			{
				"Amount": 30.80,
				"Description": "RUCKSACK OR KNAPSACK",
				"OriginAirport": "AMS",
				"DestinationAirport": "LHR",
				"Carrier": "KL",
				"PassengerCode": "ADT",
				"Date": "2018-04-10",
				"StartSegment": 1,
				"EndSegment": 1,
				"AncillaryTypeCode": "F",
				"Subcode": "0EB",
				"BaggageID": 4
			}
		]
	}
}
Note:
Parameter: Code

Type: PassengerCodeType

Description: Passenger type code related to a specific baggage sequence order with applicable hints.

Sample Value:

{
	"OrderStandardBag": {
		"PassengerBags": {
			"Code": "ADT",
			"BaggageSequenceOrder": [
				{
					"BaggageID": 1,
					"StandardBag": 1
				},
				{
					"BaggageID": 2,
					"StandardBag": 2
				},
				{
					"BaggageID": 3,
					"StandardBag": 3
				}
			]
		}
	}
}
Note:

Relase note ID: 12914


  • Ability to recheck availability and price for a specific itinerary option without booking the itinerary, so the up-to-date content can be presented.
  • A wide range of user-specified criteria can be applied. For the complete list, please consult the request and response design documentation.

API Information

Response Format
JSON
Method/Endpoint
/v3.3.0/shop/flights/revalidate
Current Version
3.3.0
Target Audience
TN
Environment
Production

What's New

  • Ability to recheck availability and price for a specific itinerary option without booking the itinerary, so the up-to-date content can be presented.
  • A wide range of user-specified criteria can be applied. For the complete list, please consult the request and response design documentation.

Relase note ID: 12982