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?

being able to store a pin code received from the door lock and send it to guest

In the API make all external payment types available for adding a payment, not only cash or credit card. Also add a possibility to add an external id through the API that will end up in the payment report.

Be able to pull information about product rules that are set up in the system.

This will give an overview of the products that are getting attached to the certain rate, segment, rate group, space category or space type in Mews

Within Mews, staff are able to close bills. This is currently not possible via the Connector API for integrators.

With this extensions to our Connector API, it will be possible for integrators to support this functionality.

Add the possibility to define the consumption date for stay products

Integrators are able to create reservations and modify some aspects of the reservation with various endpoints. With this development, the following features would be possible via the Connector API

• [ ] Update reservation with a new custom price.

Currently there's no way to retrieve all reservations in a reservation group.

Our use case: we fetch recently changed reservations from Mews but need to push all reservations in the reservation group as a whole. But we don't know what additional reservations are in that group.

I suggest to use as model the way Booking.com extranet manages restrictions, directly from the calendar.
This will still allow the creation of restrictions for a period, but it will also make it simple and quick to modify a restriction for single dates or spaces or fare; for example setting up a different min stay for 2 consecutive Saturdays.
It will also avoid having to check if in a certain period, or date, there are too many restrictions overlapping that could create confusion.

Via the Connector API, you're not currently able to add a company or update a company. With this addition, an integrator could manage these aspects.

With the reservation response from the Connector API, the total price of a cancelled reservation is not returned. With this extension, it would be possible.

Adding these extensions would allow for retrieval of data on which employee from which property added the company profile and when it was last added or updated via the API.

Booker for Distributor: The email address should not be a mandatory field as the assistants do not know each single email address of all employees they are doing reservations for. At the moment they are using the same email address for different guests. So the guest profiles are overwritten anytime. If we are creating reservations manually, the email address is also not a mandatory field. It should be enough to have the email address of the booker. That is the only way to use the distributor valueable for corporate guests.

I'd like to have access to the accounting items unit counts and amounts.

My use case is providing statistics on the number of breakfasts for a day. I can filter the accounting items that are 'breakfasts' but some line items are grouped. e.g. 3 x €15 is one total line of €45. But I need to provide the statistic that 3 breakfasts are served. Not just one.

In Mews, you're able to see all tasks which have been created. Via the Connector API, you're not able to retrieve these. With this extension an integrator could retrieve these!

Mews uses a variety of credit card platforms which have an PCI secure iFrame where when a card is entered, a token is returned. This is how the Distributor API currently works, with this feature approved integrators would be able to send through a tokenised card to Mews which can be attached to the customers profile.

Update customer endpoint exists and allows for updating of personal information of the customer.

This would allow integrators to add reservation with a custom price into Mews using the API.

Integrators would like to receive reservations which are connected to a companion. Adding an endpoint to retrieve reservations by companions would solve this!