1.3. COMMON REQUEST HANDLING
- Yana Brilevskaya
Analytics
Every message in GP Travel HUB system requires the following elements:
1.3.1. soap:Envelope
A SOAP message is an ordinary XML document containing the following elements:
Envelope* − Defines the start and the end of the message.
Header − Contains any optional attributes of the message used in processing the message, either at an intermediary point or at the ultimate end-point.
Body* − Contains the XML data comprising the message being sent.
*mandatory
Because of GP Travel HUB works with SOAP each XML request should be wrapped by
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ota="http://www.opentravel.org/OTA/2003/05">
<soap:Header/>
<soap:Body>
<GP_SessionID>2330.109699424758</GP_SessionID>
...
XML REQUEST
...
</soap:Body>
</soap:Envelope>1.3.2. GP_SessionID
The GP_SessionID is the identifier that can be used by client for its internal purposes. GP Travel HUB does not use or change it. GP_SessionID can be empty or can be set as fake value.
1.3.3. POS
POS element contains parameters for correct client authentication.
<POS>
<Source>
<RequestorID ID="ClientLogin" MessagePassword="ClientPassword" Type="22"/>
<BookingChannel Type="7"/>
</Source>
</POS>1.3.4. VERSION
Element | Attribute | Type | Description | Min…Max occurs |
|---|---|---|---|---|
| Version* | decimal (2) | Should always has value = 2. | 1..1 |
1.3.5. ECHO TOKEN
The EchoToken is the identifier that can be used by client for its internal purposes. GP Travel HUB does not use or change it.