Inventory
Update prices
This method is used when Mews updates prices of rate plans. Mews always pushes both gross
and net
prices, the channel manager chooses which of these to use.
Request
[ChannelManagerApiAddress]/updatePrices
Property | Type | Contract | Description |
---|---|---|---|
|
| required | Client token of the channel manager. |
|
| required | Connection token of a property connection. |
|
| required | Unique identification of the message. Used for asynchronous confirmations |
|
| required (always) | Url which should be used for asynchronous confirmation. |
|
| required | Collection of prices for all combinations of rate plan, space type, date and person count. |
Rate Price
Property | Type | Contract | Description |
---|---|---|---|
|
| required | Mapping code of the space type. |
|
| required | Mapping code of the rate plan. |
|
| required | Start date of the updated interval in |
|
| required | End date (included) of the updated interval in |
|
| required | Collection of prices for each person count for the specified rate plan - space type - date combination. |
|
| required | Collection of prices for each person count and age category for the specified rate plan - space type - date combination. |
Price
Property | Type | Contract | Description |
---|---|---|---|
|
| required | Price with taxes included. |
|
| required | Price with taxes excluded. |
|
| required | The three-letter code of the rate price currency. |
|
| required | The person count for the rate price. |
Age price
Property | Type | Contract | Description |
---|---|---|---|
|
|
|
|
|
| required | Price with taxes included. |
|
| required | Price with taxes excluded. |
|
| required | The three-letter code of the rate price currency. |
|
| required | The person count for the rate price. |
|
| required | Mapping code of the age category. |
Response
Synchronous simple response is expected to determine whether the update was accepted or not and whether will be synchronous or asynchronous.
Update availability
This method is used when Mews updates availability of space types.
Request
[ChannelManagerApiAddress]/updateAvailability
Property | Type | Contract | Description |
---|---|---|---|
|
| required | Client token of the channel manager. |
|
| required | Connection token of a property connection. |
|
| required | Unique identification of the message. Used for asynchronous confirmations |
|
| required (always) | Url which should be used for asynchronous confirmation. |
|
| required | Collection of availability of space types. |
Availability
Property | Type | Contract | Description |
---|---|---|---|
|
| required | Mapping code of the space type. |
|
| required | Start date of the updated interval in |
|
| required | End date (included) of the updated interval in |
|
| required | The availability of the space type in the updated interval. |
Response
Synchronous simple response is expected to determine whether the update was accepted or not and whether will be synchronous or asynchronous.
Update restrictions
This method is used when Mews updates restrictions.
Request
[ChannelManagerApiAddress]/updateRestrictions
Property | Type | Contract | Description |
---|---|---|---|
|
| required | Client token of the channel manager. |
|
| required | Connection token of a property connection. |
|
| required | Unique identification of the message. Used for asynchronous confirmations |
|
| required (always) | Url which should be used for asynchronous confirmation. |
|
| required | Collection of restrictions. |
Restriction
Property | Type | Contract | Description |
---|---|---|---|
|
| required | Mapping code of the space type. |
|
| required | Mapping code of the rate plan. |
|
| required | Start date of the restriction period in |
|
| required | End date (inclusive) of the restriction period in |
|
| optional | Minimum Length-Of-Stay applicable during the period. Must be at least |
|
| optional | Maximum Length-Of-Stay applicable during the period. Must be at least equal to |
|
| required |
Restriction State
Code | Description |
---|---|
| Open |
| Closed (used in conjunction with 6, 7 and 8) |
|
|
|
|
|
|
| Closed to arrival |
| Closed to departure |
| Closed to stay |
Note: State
2
is always sent in combination with states6
,7
and/or8
.
Restriction Examples
No Restriction (Open)
When all restrictions are removed, state 1
is sent. New restrictions always override old restrictions. State 1
is not sent to remove old restrictions, if they were modified.
Closed to Stay
State 2
is sent in combination with state 8
.
Closed to Stay with minLos and maxLos
State 1
is sent with specified minLos and/or maxLos. If minLos
and/or maxLos
is not met, then the restriction should be treated as Closed to stay.
Closed to Arrival
State 2
is sent in combination with state 6
.
Closed to Arrival with minLos and maxLos
State 1
is sent with specified minLos and/or maxLos. If minLos
and/or maxLos
is not met, then the restriction should be treated as Closed to arrival.
Closed to Departure
State 2
is sent in combination with state 7
.
Closed to Departure with minLos and maxLos
State 1
is sent with specified minLos and/or maxLos. If minLos
and/or maxLos
is not met, then the restriction should be treated as Closed to departure.
Closed to Stay and Closed to Arrival
Both states should be applied.
Closed to Stay and Closed to Departure
This combination should be treated as Closed to stay.
Closed to Stay with minLos/maxLos and Closed to Arrival
This should be applied as no arrivals are possible and reservation minLos is 3 nights and maxLos is 7 nights.
Closed to Stay and Closed to Arrival with minLos/maxLos
This combination should be treated as Closed to stay.
Closed to Departure and Closed to Arrival with minLos/maxLos
This combination should be treated as Closed to stay.
Closed to Departure and Closed to Stay with minLos/maxLos
This combination should be treated as Closed to departure. Reservations can be made if the length-of-stay requirements are met.
No minLos nor maxLos
When minLos
or maxLos
is not specified, null
value is sent.
Response
Synchronous simple response is expected to determine whether the update was accepted or not and whether will be synchronous or asynchronous.
Last updated