XML Tags
Updates and continuous integration
This interface ensures backwards compatibility in general. Existing fields will not be changed or removed. Under very rare and special circumstances such change will performed, we will state out such a change in particular through this interface specification. New request, fields, blocks can be added anytime. Each third party interface, which connects to this interface, needs to ensure that such enhancement does not affect the function of the interface in a negative way.
Recurrent XML Tags
Variable | Description | Data type |
---|---|---|
TN | Transaction number | Unsigned long |
ID | Id of the property in SIHOT.WEB | String |
RC | State of the message, 0 = OK, otherwise errors. | Short |
OC | Id of the protocol, e. g. RES = reservation | String |
MSG | Message/error message | String |
VER | Version of protocol, current 2.1 | Decimal |
MATCHCODE | String | |
CENTRALGUEST-ID | Unsigned long | |
CONTACT-ID | Unique contact ID within SIHOT | Unsigned long |
PWD | Password for user | String |
ALLOTMENT-ID | Unique ID to identify an allotment within SIHOT | Unsigned long |
SCOPE | Certain requests contain a scope for the request. In usual those are:ALL COMMISSION AVAILABLE RESTRICTIONS |
String |
GDSNO | String | |
RESERVATION-ID | Unsigned long | |
CENTRAL-RESERVATION-ID | Unsigned long | |
CURRENCY | The currency used for transmitted rates. If empty, the hotel currency will be used. | String |