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?

For actions taken in Mews that appear on the Action Log, allow the employee GUID of who made the change (such as rates) to be shown in the response.

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 are unable to adjust the Inquired status to Optional status via the Connector API. So the connection with Thynk is not working, Optional groups in Thynk are not pushed through to Mews under Inquired status.....this causes imbalance between the systems

Extend the timefilter to have a UPDATED timefilter, so that you can retrieve all accounting items that have been created/modified within a certain timeframe.
This way you can easily fetch for example "give me all items that were changed since yesterday".
Advantage: If you would like to know if there were new accounting items modified/created since the last time you checked, you do not need to get all items for the entire future. That would save a lot of bandwidth and processing (on both server/client side)

Being able to use Mews terminals with any POS provider, rather than having a second payment provider enabled.

When getting historic reservation data, such as reservations/getAll it would be great if we could get all states of reservation.

For instance, reservation was created on 10th of July for 10th of August for 30 rooms. It was changed from 30 to 50 rooms on 15 of July. Currently we can only access last state, however getting older state (state of 30 rooms in this example), would be great. This would allow us to recreate historic booking correctly. We can use this booking for creating different machine learning algorithms.

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.

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.

You can not gather some historic information about accounting items:
- When was it created?
- When was it last modified?
- When was it cancelled (/closed)?

The reservation event messages in the websocket channel are actually not representing events, but state changes. To be able to separate a checkin (state change from Confirmed to Started) from undoing a checkout (state change Processed to Started) I would like to have included the previous state in the event messages, since both of the examples will send only an event with status Started.

Currently unable to attach the company to a bill via Connector API. Having this enables possibility to fully automate bill management for corporate/event bookings.

One way could be to allow integration partners to specify CompanyId in the bills/add endpoint.

Currently, an integration partner that uses inventory data (such as Revenue Management systems, Event Management, etc) needs to poll resourceBlocks/getAll and are not able to sync space avilability in real time.

There is already a WebSocket notification when a room/space/resource is make as Out of Service (OOS). Would be great to expand that to cover Out of Order (OOO) and House Use blocks to reduce the need for calling the API regularly to check for created/updated resource blocks.

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)

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.

Add property "Type" to the request body of the Get all Bills endpoint, allowing to filter on only 'Invoice' for example.

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