Availability blocks
Process availability block
[async
] This operation is used by Mews to push availability blocks to the Channel Manager. It is also used to push availability block modifications and cancellations.
Request
[ChannelManagerApiAddress]/processAvailabilityBlock
connectionToken
string
required
Token of a concrete connection.
messageId
string
required
Unique identification of the message. This is used for asynchronous confirmations.
responseUrl
string
required (always)
URL which should be used for asynchronous confirmation.
availabilityBlock
required
Availablity block data.
Availability block
code
string
optional
Unique reference code from external system for the block. Will be returned after confirmation containing this code.
confirmationNumber
string
required
Mews confirmation number for the block.
status
required
State of the block.
name
string
required
Name of the block.
dates
required
Dates of the block.
spaceCategories
required
Allocated categories of the block.
booker
required
The main booker. This does not mean that the person has arrived at the property.
company
optional
The company associated with the block.
notes
string
optional
Notes for the block.
pickupType
required
PickupType of the block.
releaseStrategy
required
Release strategy of the availability block.
Dates
start
string
required
Inclusive start date of the block, in format yyyy-mm-dd
, e.g. 2021-12-24
; this is the first day of the block and so can be booked for stay.
end
string
required
Exclusive end date of the block, in format yyyy-mm-dd
, e.g. 2021-12-31
; this day is not included in the block and so cannot be booked for stay (it is analogous to reservation departure).
releasedDate
string
required
End date in format "yyyy-MM-dd" (e.g., "2021-12-24"). Deprecated!
Dates: Interval for e.g. 1 night for 2021-12-24/25 is represented as
"start": "2021-12-24", "end": "2021-12-24"
.
Space category allocation
start
string
required
Start date in format "yyyy-MM-dd"
(e.g. "2021-12-24"
).
end
string
required
End date (excluded) in format "yyyy-MM-dd"
(e.g., "2021-12-31"
).
spaceTypeCode
string
required
Space type code of the reservation.
allocatedSpaces
required
The number of spaces allocated in the time interval.
occupiedSpaces
required
The number of occupied spaces in the time interval.
rates
required
Prices for the current space category.
Dates: Interval for e.g. 1 night for 2021-12-24/25 is represented as
"start": "2021-12-24", "end": "2021-12-24"
.
Space count
start
string
required
Start date in format "yyyy-MM-dd"
(e.g. "2021-12-24"
).
end
string
required
End date (excluded) in format "yyyy-MM-dd"
(e.g., "2021-12-31"
).
count
int
required
Number of spaces (base of usage either occupied or allocated.)
Dates: Interval for e.g. 1 night for 2021-12-24/25 is represented as
"start": "2021-12-24", "end": "2021-12-24"
.
Rate
start
string
required
Start date in format "yyyy-MM-dd"
(e.g. "2021-12-24"
).
end
string
required
End date (excluded) in format "yyyy-MM-dd"
(e.g., "2021-12-31"
).
currencyCode
string
required
prices
required
Collection of prices for each person count, for the specified rate plan - space type - date combination.
Dates: Interval for 1 night (e.g. is represented 2021-12-24/25 is represented as
"start": "2021-12-24", "end": "2021-12-24"
).
Status
Create
Update
Cancel
PickupType
AllInOneGroup
IndividualGroups
Response
Synchronous simple response is expected to determine whether the update was accepted or not.
Async availability block confirmation is expected to determine whether the update was processed afterwards or not.
Last updated