AMADEUS WEB SERVICES SOAP HEADER 4 GUIDE¶
Attention
‘Draft Document’
The purpose of this guide is to assist application developers with the technical aspects of Amadeus Web Services SOAP Header version 4.
Based of the information in this guide you will be able to:
- Understand how Amadeus Web Services use the SOAP protocol to implement SOAP Header version 4
- Create and submit Amadeus Web Services test messages using the (Amadeus Web Services Portal) Testing tool
- Use your application’s WSDL (Web Services Definition Language) files
- Troubleshoot application errors that may occurr during the interaction with Amadeus Web Services
This guide does not cover the functional implementation (request / response structures and interpretation) of the messages. Functional information about Amadeus Web Services is available in the Functional Documentation section of the Amadeus Web Services Portal.
Information about previous versions of the Amadeus Web Services SOAP Headers (versions 1.0 to 3.0)
Overview¶
Note
Complete once the rest of the body or at least the outline has been defined
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 | <Fare_MasterPricerTravelBoardSearch>
<numberOfUnit>
<unitNumberDetail>
<numberOfUnits>1</numberOfUnits>
<typeOfUnit>PX</typeOfUnit>
</unitNumberDetail>
<unitNumberDetail>
<numberOfUnits>200</numberOfUnits>
<typeOfUnit>RC</typeOfUnit>
</unitNumberDetail>
</numberOfUnit>
<paxReference>
<ptc>ADT</ptc>
<traveller>
<ref>1</ref>
</traveller>
</paxReference>
<fareOptions>
<pricingTickInfo>
<pricingTicketing>
<priceType>RP</priceType>
<priceType>RU</priceType>
<priceType>TAC</priceType>
</pricingTicketing>
</pricingTickInfo>
</fareOptions>
<itinerary>
<requestedSegmentRef>
<segRef>1</segRef>
</requestedSegmentRef>
<departureLocalization>
<departurePoint>
<locationId>CDG</locationId>
</departurePoint>
</departureLocalization>
<arrivalLocalization>
<arrivalPointDetails>
<locationId>LHR</locationId>
</arrivalPointDetails>
</arrivalLocalization>
<timeDetails>
<firstDateTimeDetail>
<timeQualifier>TA</timeQualifier>
<date>231113</date>
<time>2200</time>
<timeWindow>4</timeWindow>
</firstDateTimeDetail>
<rangeOfDate>
<rangeQualifier>M</rangeQualifier>
<dayInterval>1</dayInterval>
</rangeOfDate>
</timeDetails>
</itinerary>
</Fare_MasterPricerTravelBoardSearch>
|