...
| Table of Contents |
|---|
| minLevel | 1 |
|---|
| maxLevel | 1 |
|---|
| outline | false |
|---|
| type | list |
|---|
| printable | false |
|---|
|
| Insert excerpt |
|---|
| NDCDOCStage:Copy of API Messages with ExamplesNDCDOCStage:Copy of |
|---|
| API Messages with Examples |
|---|
| name | Legend |
|---|
| nopanel | true |
|---|
|
Fare Preferences
...
...
NAME
...
DESCRIPTION
...
FORMAT
...
ALLOWED/POSSIBLE VALUES
...
<Preference>
...
FarePreferences / TicketDesigs / TicketDesig
...
Special Discount code
...
Alphanumeric
...
Resident & Large Family Discount
FarePreferences / Types
| Info |
|---|
AttributeType@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:
| Code Block |
|---|
|
<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.
...
...
...
...
<Preference>
<FarePreferences>
<Types>
<Type PreferencesContext="SPORT">758</Type>
</Types>
</FarePreferences>
<FlightPreferences>
<...>
</Preference>
Parameters
| Excerpt |
|---|
|
NAME | DESCRIPTION | FORMAT | ALLOWED/POSSIBLE VALUES | MANDATORY FOR | <Parameters> | Parameters | Parameters@refs | Reference for parameters, currently only used to get Upsell offers and used in conjunction with | PricedMetadata PriceMetadata. Upselling | Alphabetical | Presently the only accepted value is: “IncludeUpsellOffers” | Mandatory for schema if 'Parameters' tag is indicated. |
|
OfferPriceRQ Parameters example
| Expand |
|---|
| title | ExampleOfferPriceRQ Parameters example |
|---|
|
| Code Block |
|---|
| <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
| Excerpt |
|---|
|
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). |
OfferPriceRQ Qualifier example
| Expand |
|---|
| title | ExampleOfferPriceRQ Qualifier example |
|---|
|
| Code Block |
|---|
| <Qualifier>
<SpecialNeedQualifiers>
<Code>DISA</Code>
</SpecialNeedQualifiers>
</Qualifier> |
|
...