Room is stop sold

^{<RestrictionStatus Status="Close" />}

Room is opened for sale

^{<RestrictionStatus Status="Open" />}

Room is set as closed to arrival

^{<RestrictionStatus Status="Close" Restriction="Arrival" />}

Room is set as open to arrival

^{<RestrictionStatus Status="Open" Restriction="Arrival" />}

Room is set as closed to departure

^{<RestrictionStatus Status="Close" Restriction="Departure" />}

Room is set as open to departure

^{<RestrictionStatus Status="Open" Restriction="Departure" />}

OTA_HotelAvailNotifRQ

1

Root node

@EchoToken

1

Globally unique identifier for the request, the value will be returned in the response EchoToken.

@TimeStamp

1

Time of the transaction in xml schema dateTime format. Format like yyyy-MM-dd'T'HH:mm:ssZZ, (i.e '2021-03-09T20:05:52+08:00')

@Version

1

Always 1

OTA_HotelAvailNotifRQ / POS / Source / RequestorID

1

This identifies the system which is sending the update for Restrictions. This element must appear in the first Source element.

@Type

1

Fixed at 22 (ESRP)

@ID

1

The ID used will be agreed by the trading partners and remain the same throughout the messages.

OTA_HotelAvailNotifRQ / AvailStatusMessages

1

Contains the restrictions messages

@HotelCode

1

The code for the property whose restrictions is being updated

AvailStatusMessages / AvailStatusMessage

1..n

Contains the restrictions messages. If there is more than one room type to update, there should be one AvailStatusMessage per room type.

AvailStatusMessage / StatusApplicationControl

1

Contains specific info about the room restrictions

@Start

1

The start date for which the restrictions update is being set

@End

1

The end date for which the restrictions update is being set. The end date is inclusive.
End date cannot be more than 750 days in the future. 

@RatePlanCode

0..1

This is the rate plan whose restrictions is being updated. Must enter RatePlanCode and/or InvTypeCode to identify room

@InvTypeCode

0..1

Identifies the room type for which the restrictions is being updated. Must enter RatePlanCode and/or InvTypeCode to identify room

@Mon, Tue, Weds, Thur, Fri, Sat, Sun

0..1

"0" or "1". Optional, if not set all are assumed to be set to true
The day of the week indicators are used to communicate which days of the week the update pertains to. For example, if mon, tue and weds are set to "1", and the other days are set to "0", the restriction will only be updated for Mondays, Tuesdays and Wednesdays.
If one is sent they must all be sent.

LengthsOfStay

0..1

Optional. Used to update minimum and maximum stays.

LengthsOfStay / LengthOfStay

1..2

Mandatory if LengthsOfStay present. One LengthOfStay can be included for each of "SetMinLOS" and "SetMaxLOS".

@MinMaxMessageType

1

Mandatory if LengthsOfStay present. Possible values are "SetMinLOS" or "SetMaxLOS".

@Time

1

Mandatory if LengthsOfStay present. Sets the minimum or maximum number of days allowed for a stay. Time must be a value above 0.

Set Time to 1 to indicate that there is no MinStay requirement, or 999 to indicate no MaxStay requirement.

AvailStatusMessage / RestrictionStatus

0..1

Defines restrictions like Stop Sell, Close To Arrival (CTA), Close To Departure (CTD)

@Status

1

"Open" OR "Close"

@Restriction

0..1

"Arrival" OR "Departure". If not present the Stop Sell value if updated

OTA_HotelAvailNotifRQ

1

Root element

@EchoToken

1

Return the EchoToken from the request message.

@Version

1

Current version is 1.0

@TimeStamp

1

Time of the transaction.

OTA_HotelAvailNotifRQ / Success

0..1

Will only be present if the request processed successfully. The Errors node will not be present if the Success node is present

OTA_HotelAvailNotifRQ / Errors

0..1

Contains a list of errors if the request failed to process.

Errors / Error

1..n

Will be at least one node if there is an Errors Node.

@Type

1

Mandatory if Error present.
Any type from the OTA code table for 'Error Warning Type (EWT)' can be used. In particular, the following types are used

3: Biz rule (The business rules for the request message were not met)
4: Authentication error (If username and password are not authenticated)
6: Authorisation error (If authenticated username is not authorized to alter hotel data)
10: Required field missing (If xml does not meet the schema, i.e missing request fields or invalid data types.)

@Code

0..1