Event synchronization
The external system can directly transmit a new or changed event reservation to the upstream system. A change will overwrite completely the reservation. Cancellations of reservations have to be executed manually in SIHOT.PMS. Event-reservations may be defined as ‘not possible to modify’.
Operationcode: EVENT
EVENT
Direction
SIHOT.PMS ← SIHOT.WEB
Message
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-DOCUMENT>
<OC>EVENT</OC>
<ID>1</ID>
<TN>1</TN>
<FLAGS>EXTCOMMENTS-TEXT|MODIFYEVENTONLY</FLAGS>
<EVENT>
<MATCHCODE/>
<MATCHCODE-SM/>
<DOB/>
<CITY/>
<STREET/>
<ZIP/>
<GT/>
<PHONE1/>
<FAX1/>
<ARR>2005-08-19</ARR>
<ARR-TIME>14:00</ARR-TIME>
<DEP>2005-08-21</DEP>
<DEP-TIME>20:00</DEP-TIME>
<GDSNO>200508101310305</GDSNO>
<NAME>GUBSE AG</NAME>
<NAME2/>
<NOPAX>10</NOPAX>
<TYPE>KG</TYPE>
<CONTACT>
<Name>Meyer</Name>
<Name2>Klaus</Name2>
<STREET>Hauptstrasse</STREET>
<ZIP>12345</ZIP>
<CITY>Munich</CITY>
<EMAIL1>r.meyer@abc.de</EMAIL1>
<EMAIL2>r.meyer2@abc.de</EMAIL2>
<PHONE1>004981234567</PHONE1>
<PHONE2>004981234562</PHONE2>
<FAX1>004981234568</FAX1>
<FAX2>004981234522</FAX2>
<PERS-TYPE>1A</PERS-TYPE>
<MATCHCODE/>
</CONTACT>
<COMMENT>Kommentar</COMMENT>
<EXTCOMMENT1>Kommentar1</EXTCOMMENT1>
<EXTCOMMENT2>Kommentar2</EXTCOMMENT2>
<EXTCOMMENT3>Kommentar3</EXTCOMMENT3>
<LABEL/>
<STATUS/>
<OPTION-DATE/>
<MARKETCODE-NO>FA</MARKETCODE-NO>
<CAT>DZ</CAT>
<EXT-REFERENCE>345</EXT-REFERENCE>
<DEPOSIT-DATE>2005-08-19</DEPOSIT-DATE>
<DEPOSIT-AMOUNT>500.00</DEPOSIT-AMOUNT>
<PCAT>CAT</PCAT>
<WANT-HOTEL-ROOMS>Y</WANT-HOTEL-ROOMS>
<GUEST-SELF-PAY>N</GUEST-SELF-PAY>
<SESSION-SPEAKER-1/>
<SESSION-SPEAKER-2/>
<SESSION-SPEAKER-3/>
<SESSION-SPEAKER-4/>
<SESSION-SPEAKER-5/>
<SESSION-NAME-1/>
<SESSION-NAME-2/>
<SESSION-NAME-3/>
<SESSION-NAME-4/>
<SESSION-NAME-5/>
<EVENTID/>
<ORGANISER>
<MATCHCODE/>
<MATCHCODE-SM/>
<NAME/>
<NAME2/>
<DOB/>
<STREET/>
<CITY/>
<ZIP/>
<GT/>
<PHONE1/>
<FAX1/>
<CONTACT>
<Name>Meyer</Name>
<Name2>Klaus</Name2>
<STREET>Hauptstrasse</STREET>
<ZIP>12345</ZIP>
<CITY>Munich</CITY>
<EMAIL1>r.meyer@abc.de</EMAIL1>
<EMAIL2>r.meyer2@abc.de</EMAIL2>
<PHONE1>004981234567</PHONE1>
<PHONE2>004981234562</PHONE2>
<FAX1>004981234568</FAX1>
<FAX2>004981234522</FAX2>
<PERS-TYPE>1A</PERS-TYPE>
<MATCHCODE/>
<MATCHCODE-SM/>
</CONTACT>
</ORGANISER>
<INVOICEHOLDER>
<MATCHCODE/>
<NAME/>
<NAME2/>
<DOB/>
<STREET/>
<CITY/>
<ZIP/>
<GT/>
<PHONE1/>
<FAX1/>
<CONTACT>
<Name>Meyer</Name>
<Name2>Klaus</Name2>
<STREET>Hauptstrasse</STREET>
<ZIP>12345</ZIP>
<CITY>Munich</CITY>
<EMAIL1>r.meyer@abc.de</EMAIL1>
<EMAIL2>r.meyer2@abc.de</EMAIL2>
<PHONE1>004981234567</PHONE1>
<PHONE2>004981234562</PHONE2>
<FAX1>004981234568</FAX1>
<FAX2>004981234522</FAX2>
<PERS-TYPE>1A</PERS-TYPE>
<MATCHCODE/>
<MATCHCODE-SM/>
</CONTACT>
</INVOICEHOLDER>
<AROOMLIST>
<ROOM>
<ROOMID/>
<ARR>2005-08-19</ARR>
<ARR-TIME>14:00</ARR-TIME>
<DEP>2005-08-21</DEP>
<DEP-TIME>20:00</DEP-TIME>
<TABLE-SETUP/>
<NOPAX/>
<MAXPAX/>
<ROOM-RENTAL/>
<CHARGING/>
<PACKAGE/>
<ROOM-DECORATION/>
<TABLE-DECORATION/>
<CLOAKROOM/>
<GUARANTEED-REVENUE/>
<PREPARATION-COST/>
<PURPOSE/>
<COMMENT/>
<AEQUIPMENTLIST>
<EQUIPMENT>
<EQUIPMENTID>FC01</EQUIPMENTID>
<ARR>2005-08-19</ARR>
<DEP>2005-08-21</DEP>
<ARR-TIME>14:00</ARR-TIME>
<DEP-TIME>12:00</DEP-TIME>
<COST>2</COST>
</EQUIPMENT>
</AEQUIPMENTLIST>
<ASERVICELIST>
<SERVICE>
<SERVICEID>002</SERVICEID>
<ARR>2005-08-19</ARR>
<DEP>2005-08-21</DEP>
<TIME>14:00</TIME>
<ENDTIME>19:00</ENDTIME>
<NOSERVICES>2</NOSERVICES>
<PPU>5</PPU>
<GROUP>1</GROUP>
<POSTING>A</POSTING>
</SERVICE>
</ASERVICELIST>
</ROOM>
</AROOMLIST>
<ASERVICELIST>
<SERVICE>
<SERVICEID>BLU</SERVICEID>
<ARR>2005-08-19</ARR>
<DEP>2005-08-21</DEP>
<TIME>14:00</TIME>
<ENDTIME>12:00</ENDTIME>
<NOSERVICES>2</NOSERVICES>
<PPU>5</PPU>
<GROUP>0</GROUP>
<POSTING>A</POSTING>
</SERVICE>
</ASERVICELIST>
</EVENT>
<ARESLIST>
<!-- Same as in OC: RES -->
</ARESLIST>
</SIHOT-DOCUMENT>
Attributes Message
Attribute | Description | Data type | Usage |
---|---|---|---|
OC | EVENT | String | Mandatory |
ID | Hotel ID | String | Mandatory |
TN | Transaction number | Unsigned Long | Optional |
FLAGS | See table below, values are pipe(|)-separated | String | Optional |
Flag | Description |
---|---|
EXTCOMMENTS-DOC | Extended comments will be sent (received) as a base 64 encoded string. This is a complete file in the format of Microsoft DOC. |
EXTCOMMENTS-TEXT | Extended comments as pure text (= Default) |
MODIFYPARTICIPANTONLY | Only the participent list will be modified. Works only with the participents matchcode |
MODIFYRESONLY* | Only reservation(s) will be modified |
MODIFYEVENTONLY* | Only the event reservation will be modified |
> |
*If none of these elements is given, both front office reservation and event reservation are modified.
EVENT
Attribute | Description | Data tye | Usage |
---|---|---|---|
GDSNO | GDS number for the event reservation | String | Mandatory, if no EVENTID is given |
MATCHCODE | Match code of the client | String | |
MATCHCODE-SM | Matchcode-SM | String | |
EVENTID | Internal ID of the EVENT in SIHOT.PMS. If an Event with the EVENTID is available in SIHOT, there will be an update of the record. If there is no record for the EVENTID, a new record will be created in the database. | String | Mandatory, if no GDSNO is given. |
NAME or NAME1 | First name of the client | String | Optional |
NAME2 | Last name of the client | String | Optional |
DOB | The client’s date of birth | Date | Optional |
CITY | Town | String | Optional |
STREET | Street | String | Optional |
ZIP | Postal code | String | Optional |
GT | Guest type | Char | Optional |
PHONE1 | Phone number | String | Optional |
FAX1 | Fax number | String | Optional |
NOPAX | Number of persons | Integer | Optional |
LABEL | Event label | String | Optional |
DEP | Departure/end date | Date | Optional |
DEP-TIME | Departure/start time | Time | Optional |
ARR | Arrival/start date | Date | Optional |
ARR-TIME | Arrival time | Time | Optional |
EXT-REFERENCE | External reference | String | Optional |
COMMENT | Short note | String | Optional |
EXTCOMMENT1 | Extended Comment | String | Optional |
EXTCOMMENT2 | Extended Comment 2 | String | Optional |
EXTCOMMENT3 | Extended Comment 3 | String | Optional |
STATUS | Reservation type of the event | String | Optional |
MARKETCODE-NO | Code for the market segment | String | Optional |
RATE-SEGMENT | Segment for the Rate | String | Optional |
OPTION-DATE | Option date | Date | Optional |
DEPOSIT-DATE | Deposit due | Date | Optional |
DEPOSIT-AMOUNT | Deposit amount | Decimal | Optional |
TYPE | Event type | String | Optional |
ALLOTMENT-NO | Optional | ||
SESSION-SPEAKER-(i) | Name of the speaker for the session (i). Up to 5 values possible (i=0..4) | String | Optional |
SESSION-NAME-(i) | Name of the session (i). | String | Optional |
VIRTUAL-ROOM | room number for the virtual for the event | String | Optional |
ORGANISER | Block with organizer-data | Optional | |
INVOICEHOLDER | Block with data for the invoice holder | Optional | |
AROOMLIST | Blok with rooms for the event | Optional | |
ASERVICELIST | Block with services for the event, see chapter 14.1.3.5 | Optional | |
CONTACT | Data for contact person, see table below | Optional |
ORGANISER
Element | Description | Data type |
---|---|---|
MATCHCODE | Matchcode | String |
MATCHCODE-SM | Matchcode-SM | String |
NAME or NAME1 | Last name | String |
NAME2 | First name | String |
DOB | Date of birth | Date |
CITY | Town | String |
STREET | Street | String |
ZIP | Postal code | String |
GT | Guest type | String |
PHONE1 | Phone number | String |
FAX1 | Fax number | String |
CONTACT | Block with contact data for the organizer, see chapter 14.1.3.6 for more details |
INVOICEHOLDER
Element | Description | Data type |
---|---|---|
MATCHCODE | Matchcode | String |
MATCHCODE-SM | Matchcode-SM | String |
NAME or NAME1 | Last name | String |
NAME2 | First name | String |
DOB | Date of birth | Date |
CITY | Town | String |
STREET | Street | String |
ZIP | Postal code | String |
GT | Guest type | String |
PHONE1 | Phone number | String |
FAX1 | Fax number | String |
CONTACT | Block with contact data for the organizer, see chapter 14.1.3.6 for more details |
AROOMLIST
In this Block, you could fill several ROOM Blocks, one for each room.
Element | Description | Data type |
---|---|---|
ROOMID | Id of the room | String |
ARR | Start day | Date |
ARR-TIME | Start time | Time |
DEP | Closing day | Date |
DEP-TIME | Closing time | Time |
TABLE-SETUP | Seating | String |
NOPAX | Number of participants | Integer |
MAXPAX | Maximum of participants | Integer |
ROOM-RENTAL | Room rental | Decimal |
CHARGING | Charging | short |
PACKAGE | Booked package | String |
ROOM-DECORATION | Art of room decoration | String |
TABLE-DECORATION | Art of table decoration | String |
CLOAKROOM | Has a cloakroom | Char |
GUARANTEED-REVENUE | Guaranteed revenue | Decimal |
REPARATION-COST | Reparation costs | Decimal |
PURPOSE | The purpose of the room | String |
COMMENT | A comment about the room | String |
AEQUIPMENTLIST | List with equipment for this room, see chapter 14.1.3.7 | |
ASERVICELIST | List with services for this room, see chapter 14.1.3.5 |
ASERVICELIST
In this <ASERVICELIST>
Block, you could fill several <SERVICE>
-Blocks with the following elements:
Element | Description | Data type | Usage |
---|---|---|---|
SERVICEID | Id of the service | String | Mandatory |
ARR | Start date | Date | Mandatory |
DEP | end date | Date | Mandatory |
TIME | Start time | Time | Mandatory |
ENDTIME | End time | Time | Mandatory |
NOSERVICES | Quantity | Long | Mandatory |
PPU | Rate per unit | Decimal | |
GROUP | Grouping of services | Char | |
POSTING | Kind of posting | String | |
COMMENT | notes | String |
CONTACT
Element | Description | Data type |
---|---|---|
NAME or NAME1 | Last name | String |
NAME2 | First name | String |
ADDRESS | Salutation | Char |
STREET | Street | String |
ZIP | Postal code | String |
CITY | Town | String |
EMAIL1 and EMAIL2 | Email and alternative Email | String |
INVOICE-EMAIL | The email address for invoices | String |
PHONE1 and PHONE2 | Phone number and alternative phone number | String |
FAX1 and FAX2 | Fax number and alternative fax number | String |
MOBIL1 and MOBIL2 | Cell phone number and alternative cell phone number | String |
PERS-TYPE | Person type | String |
MATCHCODE | Matchcode | String |
MATCHCODE-SM | Matchcode-SM | String |
VIP and VIP2 | VIP flag | String |
FLAGS | Flags for contact person, see table below | String |
Available flags are:
Flag | Description |
---|---|
UPDATE-CONTACT-PROFILE | The guest profile is updated with the current data |
AEQUIPMENTLIST
In this list, you could fill several <EQUIPMENT>
Blocks, one block for each equipment:
Element | Description | Data type |
---|---|---|
EQUIPMENTID | ID for the equipment | String |
ARR | Start date | Date |
DEP | End date | Date |
ARR-TIME | Start time | Time |
DEP-TIME | End time | Time |
COST | Rate | Decimal |
COMMENT | Note | String |
Response
Error messages are described in chapter <OC>RES</OC>
. If an error occurs during the request, an error message is sent to
SIHOT.PMS. An error code “0” means that no error occurred.
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-DOCUMENT>
<OC>EVENT</OC>
<ID>1</ID>
<TN>1</TN>
<RC>1</RC>
<MSG>error message</MSG>
</SIHOT-DOCUMENT>
Operationcode: EVR
EVR
Direction
SIHOT.PMS ← SIHOT.WEB
Message
The external System makes the following request (EVR) to SIHOT.WEB in order to receive all events for a period.
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-DOCUMENT>
<OC>EVR</OC>
<TN>1</TN>
<ID>1</ID>
<FROM>2024-08-22</FROM>
<TO>2024-08-23</TO>
<GDSNO></GDSNO>
<EVENTID>4711</EVENTID>
<FLAGS></FLAGS>
</SIHOT-DOCUMENT>
Attributes Message
Element | Description | Data type | Usage |
---|---|---|---|
TN | Transaction number | Long | Mandatory |
ID | Hotel number | Long | Mandatory |
FROM | Start date for the search | Date | Optional |
TO | End date for the search | Date | Optional |
GDSNO | Unique GDS number for the event | String | Optional |
EVENTID | Unique ID for the event | Long | Optional |
FLAGS | Flags for event answer, separated by pipe | | String | Optional |
If an <EVENTID>
(or GDSNO) is given, then only the event with this EVENTID (or GDSNO) will be returned and the tags
Flag | Description |
---|---|
EXTCOMMENTS-DOC | Extended comments will be sent (received) as a base 64 encoded string. This is a complete file in the format of Microsoft DOC. |
EXTCOMMENTS-TEXT | Extended comments as pure text |
NO-ROOMS | Suppress room information (including room-service and equipment information) |
NO-EQUIPMENT | Suppress equipment information |
NO-SERVICE | Suppress service information (for rooms and reservation) |
NO-CANCELLATIONS | Suppress cancelled events |
Response
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-DOCUMENT>
<OC>EVR</OC>
<ID>1</ID>
<TN>1</TN>
<RC>0</RC>
<MSG>OK</MSG>
<EVENTLIST>
<EVENT>
<!–same as in request <OC>EVENT</OC> ->
</EVENT>
…
</EVENTLIST>
</SIHOT-DOCUMENT>
Operationcode: ER
ER
Direction
SIHOT.PMS → SIHOT.WEB
Message
The external System makes the following request (ER) to SIHOT.WEB in order to receive a list of all rooms with certain criteria in a period.
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-DOCUMENT>
<OC>ER</OC>
<ARR>2020-12-17</ARR>
<ARR-TIME>1000</ARR-TIME>
<DEP>2020-12-19</DEP>
<DEP-TIME>1200</DEP-TIME>
<PAX-FROM></PAX-FROM>
<PAX-TO></PAX-TO>
<SETUP></SETUP>
<CAT></CAT>
<TYPE></TYPE>
</SIHOT-DOCUMENT>
Attributes Message
Element | Description | Data type |
---|---|---|
ARR | Start date | Date |
DEP | End date | Date |
HN | Hotel number | Long |
ARR-TIME | Start time | Time |
DEP-TIME | End time | Time |
PAX-FROM | Minimum number of pax | Short |
PAX-TO | Maximum number of pax | Short |
SETUP | Type of table setup | String |
CAT | Room type | String |
TYPE | 00 A List with all Rooms 01 A List only with available rooms during that period 02 A List only with occupied rooms (please analyse the Tags OCC-INFO, OCC-FROM and OCC-TO) |
String |
OVERBOOKING | 1= with overbooking data | Char |
Response
<?xml version="1.0" encoding="ISO-8859-1"?>
<SIHOT-DOCUMENT>
<VER>2.0</VER>
<OC>ER</OC>
<AROOMLIST>
<ROOM>
<LOCTION></LOCATION>
<CAT></CAT>
<ROOMID></ROOMID>
<ROOMNAME></ROOMNAME>
<POWER></POWER>
<LOCATION></LOCATION>
<OCC-FROM></OCC-FROM>
<OCC-FROMTIME></OCC-FROMTIME>
<OCC-TO></OCC-TO>
<OCC-TOTIME></OCC-TOTIME>
<OCC-INFO></OCC-INFO>
<SETUP-LIST>
<SETUP-CAT></SETUP-CAT>
<MAX-PAX></MAX-PAX>
</SETUP-LIST>
</ROOM>
<ROOM>
…
</ROOM>
</AROOMLIST>
<SIHOT-DOCUMENT>
Attributes Response
Attribute | Description | Data type |
---|---|---|
CAT | Category of the event room. These are different from the guest rooms. | String |
ROOMID | ID of the room | String |
ROOMNAME | Description/Long Name of the room | String |
POWER | Information the power. | String |
LOCATION | Location of the room | String |
MAINROOM | Flag, if this is a main room. 1=Yes, 0=No | Char |
SHAREDROOM | Flag, if this is a shared room. 1=Yes, 0=No | Char |
ELEMENTARYROOM | Flag, if this is an elementary room. 1=Yes, 0=No | Char |
COMBIROOM | Flag, if this is a composed room. 1=Yes, 0=No | Char |
CONTAINING-ROOM-LIST | List of rooms in this room, if this is a composed room | |
CNT-OVERBOOK | Number of overbooking | Short |
MAX-OVERBOOK | Maximum number of allowed overbooking | Short |
OCC-FROM | Start date of the occupation | Date |
OCC-FROMTIME | Start time of the occupation | Time |
OCC-TO | End date of the occupation | Date |
OCC-TOTIME | End time of the occupation | Time |
OCC-INFO | List of occupations | String |
SETUP-LIST | Block with setup information | |
SETUP-CAT | Type of setup | String |
MAX-PAX | Maximum number of pax | Short |
CRIT-LIST | List with available criteria |