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.

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.

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.

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

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

Could the Connector API documentation please give the maximum possible lengths of all string values? It's hard to store responses from the API in a database without knowing how big to make the fields!

In the Connector API documentation it states that Reservation Origin can be one of “Distributor”, “ChannelManager”, “Commander”, “Import”, “Connector” or “Navigator”. But in fact it can have at least one other value "CommanderInPerson". Could the documentation please be updated to list all possible values?

'Create rate plan via Connector API - Rateplan/Add. This to enable contract management from one platform (e.g. a CRM)

There's currently no way to change a reservation's status to "Optional" using the API. There are individual endpoints for confirming and canceling a reservation, but no endpoint for making one optional. A specific endpoint, or an extension to the [PlatformAddress]/api/connector/v1/reservations/update that allows for modifying the reservation state would be great!

Why? We allow our users to create "Enquired" reservations but they now have no way to make those reservations "Optional" (from our system)

Thanks!

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

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)

Now you always need to enter a period when you are looking for a bill (bills/getall). And the period cannot exceed 3 months. If we do not know when an invoice was issued, we just have the number, it is not easy to find.

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.

There is a possibility to click "Create keys" in the Mews Admin to create keys by the Salto key cutter system. However we want to automize this through the API, so that keys can be automatically generated for guests, e.g. an hour before check-in.