Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

 New or modified element

To be removed/deprecated

Unique to v2 - Branded Fares

Unique to V1 - Fare Families

Fare Preferences

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

<Preference>

FarePreferences / TicketDesigs / TicketDesig

Special Discount code

Alphanumeric

Resident & Large Family Discount

FarePreferences / Types

Attribute

Type@PreferencesContext

Mandatory for schema if 'Preference' tag is indicated and don't have other preference inside.

Type of product selected, as in the example below: 

<Type PreferencesContext="TO">758</Type>

“TO“ the attribute for the Tour Operator private fare type and ‘758’ as the Code from PADIS 9910

Alphanumeric

For the Products currently available through our NDC channel, and the codes required to request them please see the information in Private Leisure Fares.

 Example
<Preference>
	<FarePreferences>
		<Types>
			<Type PreferencesContext="SPORT">758</Type>
		</Types>
	</FarePreferences>
	<FlightPreferences>
		<...>
</Preference>

Parameters

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

MANDATORY FOR

<Parameters>

 

Attribute

Parameters@refs

Reference for parameters, currently only used to get Upsell offers and used in conjunction with PricedMetadata.

Alphabetical

Presently the only accepted value is:

“IncludeUpsellOffers”

Mandatory for schema if 'Parameters' tag is indicated.

 Example
<Parameters refs="IncludeUpsellOffers"/>
<Query>
	<Offer OfferID="IBe8421b7ef3524ca9ac921fde5c9dd646OC" Owner="IB" ResponseID="Qm9va2luZ0BHVy0xNjk4NjcwMTQ4MzUxLURLd0d3">
		<OfferItem OfferItemID="IBe8421b7ef3524ca9ac921fde5c9dd646OC_01">
			<PassengerRefs>ADULT_01</PassengerRefs>
		</OfferItem>
		<OfferItem OfferItemID="IBe8421b7ef3524ca9ac921fde5c9dd646OC_02">
			<PassengerRefs>INFANT_01</PassengerRefs>
		</OfferItem>
	</Offer>
</Query>
...
<DataLists>
	<PassengerList>
		<Passenger PassengerID="ADULT_01">
			<PTC>ADT</PTC>
		</Passenger>
		<Passenger PassengerID="INFANT_01">
			<PTC>INF</PTC>
		</Passenger>
	</PassengerList>
</DataLists>
<Metadata>
	<Other>
		<OtherMetadata>
			<PriceMetadatas>
				<PriceMetadata MetadataKey="IncludeUpsellOffers"/>
			</PriceMetadatas>
		</OtherMetadata>
	</Other>
</Metadata>

Qualifier

NAME

DESCRIPTION

FORMAT

ALLOWED/POSSIBLE VALUES

<Qualifier>

SpecialNeedQualifiers / Code

Code of the special need qualifiers.

Mandatory for schema if 'Qualifier' tag is indicated.

4 Alphabetical

Special Services

Note: Formerly, the only way to request SSRs was through OfferPriceRQ message, which is still possible to maintain backward compatibility. However, we recommend that from now on the ServiceList is used.

It should be noted that if SSRs are requested in both the OfferPriceRQ and the ServiceListRQ, then an error will be returned (please, see an example of this scenario in our Special Services Error Messages page).

 Example
<Qualifier>
	<SpecialNeedQualifiers>
		<Code>DISA</Code>
	</SpecialNeedQualifiers>
</Qualifier>
  • No labels