We need a more detailed descriptions in action log and in origin for those integrations that use the connector API.

We currently have multiple integrations (room checking, IReckoU, Omniboost, Zapier, Pxier, etc.), it's is impossible to understand in our analytics (POWER BI) through which channel a booking came if it just says connector for all.

Same applies for action log. If something went wrong. How do we know which integration made the change if all indicated system?

We are working with Wihp to display our rates on Google. Actually Mews is not able to provide the cancellation deadline for each rates, other OTAs are able to provide rates per room category and with cancelation deadline. We need to be able as well to show to our customers our cancelation policy per rate category.

Currently we have:
…
distributor.setLanguageCode(languageCode);
distributor.setCurrencyCode(currencyCode);
distributor.setStartDate(date);
distributor.setEndDate(date);
…

Can we please have:
distributor.setAdults(5);

API POST parameters:

• Reservation ID


• Client Token


• Access token

Returns link to auto-login for reservation online check-in

Use Cases:

• Send scheduled transactional emails for costumers to fill the check-in online.




• Ops team doesn't have to trigger the email manually via Commander.




• Push more relevant information inside the email.




• Don't get emails from a different domain for the online Check-in.




• Get ownership of the tone in the communications with our clients.

The new Payment Requests feature is great, would be useful to have the functionality added to the API so you can generate payment requests from integrations.

1- Add the option to make mandatory that the user (guest) fills in information before they can add the product to their stay. Example: offer airport transfer but then make it mandatory for the user to input the time and airport of arrival.
2- Add conditions to products so that they can only be chosen if such conditions are met. Example: minimum of 4 people must book in order to book a ski lesson

Make possible to show a breakdown of the bill on the Rates and Checkout views of distributor, in cases where a particular product is not optional for the customer, like a cleaning fee tied to a particular space or a membership fee tied to a particular rate. Right now, the price guests actually pay is higher to the one they are told to pay at checkout (in cases when a mandatory product is added inside the system).

For Non Refundable Bookings or bookings with a payment at confirmation, refuse bookings for which payment has failed.

Currently, bookings are accepted with failed payments and only a settlement task in created. This leads to excess admin for bookings that provide no income.

In Belgium we have OGM numbering, partners could handle this via the api if there would be an UpdateBill request available in which only the notes can be updated of an open bill.

(see also https://mews.myjetbrains.com/youtrack/issue/RND-33807?p=COM-225)

In the request of bills/getAll have the possibility to enter companyID's, that way we can present the user with all bills of a specific company

For the connector API it is necessary to retrieve all rooms each time an API Call is made to pull the space feature, this is quite a heavy call for TSH as some hotels have 700 rooms.

Could Mews consider to introduce a filter by room name ideally?

This way Ireckonu or another integrating partner does not need to pull all rooms each time.

Enable adding links (like dinner menu, or a link to a hotel landing page) to the descriptions of rates and products

Connector API: to be able to access the reason for OOO rooms through Mews API

Users in Mews can choose from a pre-defined list of reasons when manually cancelling reservations in the reservations module in Mews PMS.

However, when a reservation is cancelled via API, the cancellation reason defaults to "Other".

It would be great to be able to also specify cancellation reason via the API (drawing from the pre-defined list available in Mews) so that integration partners can help keep the reservations reporting as accurate as possible.

Hardcoded city tax should be visible over connector API

DISTRIBUTOR landing page should be able to recognize language of operating system of guest trying to make a reservation

Making it possible for contracted companies, which have a voucher code, to make a booking without credit card guarantee. Such companies can usually pay on invoice or upon arrival.
To do so, Mews would need to allow mapping rates (and not only room categories) in Distributor.

I guess this is a bug in the API.
The call never returns any CompanionIds within a reservation. The companions have been added both, by API Call and via the MEWS frontend