The supplier sends this message about the closures for check-in (closures on arrival) which are applied by the structures. The query type (type) is set to getclousuretoarrival.

This call returns only closures on arrival, whether they were set through the channel manager (setclousure with checkinonly Y, or the deprecated setclousuretoarrival) or through the extranet. It is the only call that returns them: getclousure returns normal closures and closures on departure only.

Below you can see the fields you can find in the message body and their meanings.

Request

• startdate

  first check-in day of the period requested

• days

  number of days. (You can add this number to the start date to get the end of the period. If these two dates correspond this value is set to 0).

Let’s see an example of message the client could send.

<?xml version="1.0" encoding="UTF-8"?>
<envelope>
    <header>
        <actor>...</actor>
        <user>...</user>
        <password>...</password>
        <version>0.1b</version>
        <timestamp>20210427</timestamp>
        <transaction>160125</transaction>
    </header>
    <query type="getclousuretoarrival" product="hotel" agrement="1299">
        <startdate>2022-01-01</startdate>
        <days>30</days>
    </query>
</envelope>

Response

The reply message contains, after tag response, one date element for each period of consecutive days with the same closure terms, limited to the period requested.

date

• startdate

  first closed check-in day

• days

  number of days. (You can add this number to the start date to get the end of the period. If these two dates correspond this value is set to 0)

• roomtype

  check-in closure terms for each room type (Y check-in closed, N check-in open). Room types not enabled on the agreement are always returned as N

• • SGL single room
• • TWN twin room
• • DBL double room
• • TRP triple room
• • QUD quadruple room
• • STR big accommodations
• • onrequest Y: the closure will not remove the contract from availability but will change its status to "on request" thus allowing the hotel to consider confirming the reservation. Closures set through the channel manager are always N
• • freesale Y: the closure is applied only on allotments pushed via CM; N: the closure is applied on all allotments. The value depends on the closure configuration of the agreement
• • checkinonly always Y in this call
• • checkoutonly always N in this call

onrequest and freesale are read-only: they are not accepted by setclousure.

Let’s see an example of message the client could receive.

<?xml version="1.0" encoding="UTF-8"?>
<envelope>
    <header>
        <actor>...</actor>
        <user>...</user>
        <version>0.1b</version>
        <timestamp>20210219164156</timestamp>
        <transaction>160125</transaction>
    </header>
    <response type="getclousuretoarrival"/>
    <date>
        <startdate>2022-12-25</startdate>
        <days>1</days>
        <roomtype>
            <SGL>Y</SGL>
            <TWN>Y</TWN>
            <DBL>Y</DBL>
            <TRP>Y</TRP>
            <QUD>Y</QUD>
            <STR>Y</STR>
            <onrequest>N</onrequest>
            <freesale>Y</freesale>
            <checkinonly>Y</checkinonly>
            <checkoutonly>N</checkoutonly>
        </roomtype>
    </date>
</envelope>

In case of error the reply message contains, within tag response, the string "error code XX (description)", where XX represents an error code. The exceptions are described in the exceptions page.