Unanswered questions

Hi!  We’re currently building a WordPress extension that integrates with the Mews Distributor API, and we’ve run into recurring issues that I’d like to check if anyone else has solved.Current situation: We work with multiple bookable services (several ConfigurationIds) under one Mews enterprise. Our goal is to aggregate all services into a single unified search flow (cabins, apartments, hotels, across locations). We fetch metadata via configuration/get (list of Ids) and then call hotels/getAvailability for each ConfigurationId + HotelId + CategoryIds. Problems: Endpoint mismatch: Some documentation and support replies referencehttps://app.mews.com/api/distributor/v1/... while others usehttps://api.mews.com/api/distributor/v1/.... In production, we sometimes get 404 (Cloudflare HTML) on configuration/get if we don’t use the api.mews.com/api/... form. Availability errors: hotels/getAvailability often returns 400 Invalid CategoryIds even when the CategoryIds were retriev

We received a request at our hotel from a guest who would like to put together a gift package for his staff members.It concerns a certain number of staff members to whom he would like to give credit for two overnight stays + breakfast + 1 dinner + welcome drink. How would you recommend setting this up? 

Moin ​@Mews Community Team ,die Familienbeziehungen in den Profilen ist eine wunderbare Entwicklung. Damit können wir die Profile deutlich sinnvoller verwalten.Ist denn angedacht, dass diese Verknüpfungen in Zukunft auch in der Reservierungsmaske als Mitreisende per Auswahl hinzugefügt werden können? Aktuell müssen wir noch jeden Reisenden mühsam über den Namen manuell hinzufügen. Das wäre ja der logisch nächste Schritt.Viele GrüßeLeif 

Hello everyone,I am having a problem with automatic reminder emails for optional reservations in MEWS. Here is the context:An agency made an optional reservation for a customer.The customer received the automatic optional reservation reminder email, which allowed them to see the price of their reservation and cancel it themselves via the Mews Guest Portal link, which is something we definitely do not want.According to MEWS documentation:The recipient of the email is always the owner of the reservation (the main guest), and if the main guest's email address is not provided, the email is sent to the organizer (the agency).In our case, our policy is to record all customer emails as soon as we receive them, so the problem occurs systematically for agency customers and certain groups.The automatic reminder email is very useful for tracking reservations, but we would like to limit its sending to certain types of customers, for example:-Travel agency customers-Group reservationsTo date, there