498 results found

1. Add SourceId support to reservations/add (Connector API)

   Current behaviour:

   When a reservation is created through the Connector API (reservations/add), no Source is assigned. The reservation only carries Origin = "Mews Open API". The endpoint does not support a SourceId field, so there is no way to tag the reservation with the channel or source it actually came from.

   By contrast, the Channel Manager API accepts a sources array in the reservation payload, and Mews assigns the source automatically. That capability simply doesn't exist on the Connector API side.

   Why this is a problem:

   We run our own booking engine built on the Connector API. Source codes are how we understand our business mix when pulling reservation data via the API, and right now those reservations are indistinguishable from any other Connector API traffic.

   Our current workaround is to infer booking engine reservations from the Origin field. This does not scale: as soon as we add a second integration through the Connector API (additional channels, partner systems, corporate booking tools), every one of them reports the same Origin = "Mews Open API" and we lose the ability to tell them apart entirely. There is no fallback, because sourceAssignments in the Connector API is read-only.

   The practical consequence is that direct and API-driven business cannot be segmented or reported on accurately, which undermines revenue analysis, channel cost comparisons, and any decision that depends on knowing where bookings originate.

   Requested change:

   Allow a source to be assigned to reservations created via the Connector API, ideally by supporting a SourceId (or a sources array, matching the Channel Manager API pattern) on reservations/add.

   As an alternative or complement, a writable sourceAssignments/add operation would also solve it, letting us assign the source in a second call after reservation creation.

   Business impact:

   Any Mews customer running a custom booking engine or multiple Connector API integrations has the same blind spot. For us it currently blocks accurate business mix reporting across the chain, and it becomes a hard blocker as we onboard further channels through the Connector API.

   Current behaviour:

   When a reservation is created through the Connector API (reservations/add), no Source is assigned. The reservation only carries Origin = "Mews Open API". The endpoint does not support a SourceId field, so there is no way to tag the reservation with the channel or source it actually came from.

   By contrast, the Channel Manager API accepts a sources array in the reservation payload, and Mews assigns the source automatically. That capability simply doesn't exist on the Connector API side.

   Why this is a problem:

   We run our own booking engine built on the Connector API. Source codes are… more

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   idea to upvote  ·  0 comments  ·  Connector API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Expose Occupancy Override Adjustments via Connector API (rates/getPricing)

   Problem

   When using the rates/getPricing endpoint, the API currently returns pricing information such as EmptyUnitAdjustment and ExtraUnitAdjustment, but it does not expose the actual per-day occupancy override values configured in the
   Mews Pricing screen.

   In Mews Operations, revenue managers can override occupancy adjustments for specific dates (for example, changing the negative adjustment applied for single occupancy on selected days). These overrides are visible in the UI but cannot currently be retrieved through the API.

   This creates a gap between what is visible in Mews and what external systems can access.

   Use case

   We use the Mews API to feed pricing and revenue-management processes across multiple properties.
   To accurately reproduce and analyze rates, we need access to the effective occupancy adjustments applied on each date, including any overrides configured by the revenue management team.

   Without these values:

   • API consumers cannot fully replicate the pricing displayed in Mews.
   • Reporting and BI systems may show discrepancies.
   • Custom booking engines and pricing integrations cannot calculate rates exactly as Mews does.
   • Revenue-management audits become more difficult.

   Requested enhancement

   Please expose the occupancy override values as part of the Connector API, ideally through:

   • rates/getPricing
   • or a dedicated endpoint exposing occupancy adjustments and overrides

   Example fields:
   JSON{ "Date": "2026-08-15", "SpaceCategoryId": "...", "OccupancyOverride": { "NegativeAdjustment": -25, "PositiveAdjustment": 15 }}Afficher plus de lignes

   or any equivalent structure providing the effective occupancy adjustment applied for a specific date.

   Business value

   This enhancement would allow partners, BI platforms, RMS solutions, custom booking engines and enterprise integrations to obtain the exact pricing logic configured in Mews and eliminate discrepancies between API data and the Mews user interface.

   Thank you for considering this feature request.

   Problem

   When using the rates/getPricing endpoint, the API currently returns pricing information such as EmptyUnitAdjustment and ExtraUnitAdjustment, but it does not expose the actual per-day occupancy override values configured in the
   Mews Pricing screen.

   In Mews Operations, revenue managers can override occupancy adjustments for specific dates (for example, changing the negative adjustment applied for single occupancy on selected days). These overrides are visible in the UI but cannot currently be retrieved through the API.

   This creates a gap between what is visible in Mews and what external systems can access.

   Use case

   We use the Mews API to feed pricing… more

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   idea to upvote  ·  0 comments  ·  Connector API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Add Currencies array to Enterprises endpoint.

   Currently, the Enterprises endpoint provides nearly all of the required data for retrieving information about properties within a portfolio using portfolio tokens. However, one important piece of information is missing: the Currencies array, which is currently available via the Configuration endpoint.

   At present, retrieving property currency information from the Configuration endpoint requires specifying the EnterpriseId in the request. This means that for a portfolio containing, for example, 100 properties, a client would need to make 100 separate requests to the Configuration endpoint instead of a single request to the Enterprises endpoint. This significantly increases implementation complexity and the number of API calls required.

   Adding the Currencies array to the Enterprises endpoint would bring the following benefits:

   Simplify client-side implementation by eliminating the need for multiple per-property Configuration requests.

   Reduce the overall number of API calls, thereby lowering load on the Mews API infrastructure.

   Improve efficiency and performance for integrators working with larger portfolios.

   Currently, the Enterprises endpoint provides nearly all of the required data for retrieving information about properties within a portfolio using portfolio tokens. However, one important piece of information is missing: the Currencies array, which is currently available via the Configuration endpoint.

   At present, retrieving property currency information from the Configuration endpoint requires specifying the EnterpriseId in the request. This means that for a portfolio containing, for example, 100 properties, a client would need to make 100 separate requests to the Configuration endpoint instead of a single request to the Enterprises endpoint. This significantly increases implementation complexity and the number of… more

   10 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   idea to upvote  ·  0 comments  ·  Connector API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. native Schlage Encode integrations to allow for automated code delivery for keypad locks

   We operate self-check-in properties using keypad locks and would like Mews to support native access code management and delivery for PIN-based locks.

   Our ideal workflow would be:

   Reservation is created in Mews
   Mews automatically generates a unique guest access code
   Code is assigned to the room and active only for the guest's stay dates
   Mews automatically sends the code through Guest Journey messaging (SMS and email)
   Code automatically expires at checkout
   Guests do not need to download an app or use their phone as the key

   Many independent hotels, motels, vacation rentals, cabins, RV resorts, and self-check-in properties utilize keypad locks rather than mobile keys. Today, we rely on third-party systems to generate and deliver access codes, adding cost and complexity to the tech stack.

   Native PIN-code management and delivery would allow operators to reduce software costs, simplify operations, and provide a seamless self-check-in experience directly through Mews.

   While Schlage Encode is our current lock platform, we would support a broader solution that works with common keypad lock providers and access-management platforms.

   We operate self-check-in properties using keypad locks and would like Mews to support native access code management and delivery for PIN-based locks.

   Our ideal workflow would be:

   Reservation is created in Mews
   Mews automatically generates a unique guest access code
   Code is assigned to the room and active only for the guest's stay dates
   Mews automatically sends the code through Guest Journey messaging (SMS and email)
   Code automatically expires at checkout
   Guests do not need to download an app or use their phone as the key

   Many independent hotels, motels, vacation rentals, cabins, RV resorts, and self-check-in properties utilize keypad… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   idea to upvote  ·  0 comments  ·  Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Erreur dans la prise en compte des produits d'une réservation

   Actuellement les réservations qui transitent par un channel manager qui n'est pas Mews (d-edge dans notre cas) remontent avec des informations erronées. Les prix des produits et des nuitées ne sont pas affectés correctement et certaines nuitées ont des montants négatifs... Même si le montant total de la réservation est a priori (cela n'est pas certain de notre côté) correct, il est très chronophage et source d'erreurs de devoir modifier quasiment toutes les réservations pour avoir une répartition correcte des prix. Sans compter que cela engendre de nombreuses erreurs potentielles de CA, de statistiques, de rapports et empêche une bonne gestion tarifaire. C'est donc un point URGENT et ESSENTIEL au bon fonctionnement du logiciel. Mews a reconnu que le problème était identifié et venait de leur côté mais ne le considère pas comme une urgence... Merci de votre action rapide sur ce sujet.

   Actuellement les réservations qui transitent par un channel manager qui n'est pas Mews (d-edge dans notre cas) remontent avec des informations erronées. Les prix des produits et des nuitées ne sont pas affectés correctement et certaines nuitées ont des montants négatifs... Même si le montant total de la réservation est a priori (cela n'est pas certain de notre côté) correct, il est très chronophage et source d'erreurs de devoir modifier quasiment toutes les réservations pour avoir une répartition correcte des prix. Sans compter que cela engendre de nombreuses erreurs potentielles de CA, de statistiques, de rapports et empêche une bonne… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   idea to upvote  ·  0 comments  ·  Channel manager API  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Intégration comptable et dématérialisation des factures : export des rapports Mews ou bien API ?

   Au regard de l’arrivée de la réforme de la facture électronique, la responsabilité de l’émission du flux d’écritures depuis l’ERP relève de la compétence exclusive de l’éditeur. Quelle est l'approche préconisée pour l'intégration comptable dans le contexte de la dématérialisation des factures à partir du 1/9/2026 : export d'un rapport Mews ou bien accés aux données de facturation via l'API ?

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   idea to upvote  ·  0 comments  ·  Integrations  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Gutschein Interface

   Wir melden uns im Namen unseres gemeinsamen Kundes Hotel Grossarler Hof:

   Wir möchten das ADDITIVE Gutschein Tool vollständig an Mews anbinden und die darüber erstellten Gutscheine direkt im PMS verwalten und einlösen können.

   Dafür wäre ein Interface in Mews erforderlich, in dem die aus dem ADDITIVE System übertragenen Gutscheine zentral angezeigt werden. Sichtbar sein sollten insbesondere der Gutscheincode, der ursprüngliche Gutscheinwert, das verfügbare Restguthaben, die Gültigkeit sowie der aktuelle Status.

   Zusätzlich sollte es möglich sein, einen Gutschein einer Reservierung oder Rechnung zuzuordnen und vollständig oder teilweise einzulösen. Das verbleibende Guthaben und der Status des Gutscheins sollten dabei automatisch aktualisiert werden.

   Damit die Anbindung technisch umgesetzt werden kann, müssten diese Funktionen auch über die Mews API verfügbar sein. So könnten Gutscheindaten, Einlösungen, Restwerte und Statusänderungen zuverlässig zwischen dem ADDITIVE Gutschein Tool und Mews synchronisiert werden.

   Eine solche Funktion würde die operative Verarbeitung der über ADDITIVE verkauften Gutscheine deutlich vereinfachen und eine manuelle Verwaltung in mehreren Systemen vermeiden.

   Wir melden uns im Namen unseres gemeinsamen Kundes Hotel Grossarler Hof:

   Wir möchten das ADDITIVE Gutschein Tool vollständig an Mews anbinden und die darüber erstellten Gutscheine direkt im PMS verwalten und einlösen können.

   Dafür wäre ein Interface in Mews erforderlich, in dem die aus dem ADDITIVE System übertragenen Gutscheine zentral angezeigt werden. Sichtbar sein sollten insbesondere der Gutscheincode, der ursprüngliche Gutscheinwert, das verfügbare Restguthaben, die Gültigkeit sowie der aktuelle Status.

   Zusätzlich sollte es möglich sein, einen Gutschein einer Reservierung oder Rechnung zuzuordnen und vollständig oder teilweise einzulösen. Das verbleibende Guthaben und der Status des Gutscheins sollten dabei automatisch aktualisiert werden.

   … more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   idea to upvote  ·  0 comments  ·  Connector API  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Buchungsbestätigung nach Annahme des Angebots

   Wir versenden täglich Angebote über Mews an unsere Gäste. Sollten sie das Angebot nicht annehmen oder nicht darauf reagieren, erhalten wir die Benachrichtigung „Angebot abgelaufen“ bzw. „Optionsende erreicht“. Anschließend können wir dem Gast eine Erinnerung senden oder weitere Schritte einleiten.
   Wenn der Gast das Angebot storniert, wird die optionale Buchung automatisch aus dem System entfernt. Doch was passiert, wenn der Gast das Angebot annimmt? Die Buchung wird zwar im System fixiert, wir erhalten darüber jedoch keine Benachrichtigung. Dadurch kann es passieren, dass bestätigte Buchungen im System übersehen werden.
   Wir möchten die Gäste nach der Annahme kontaktieren, uns für die Buchung bedanken und ihnen die nächsten Informationen und Schritte sowie gegebenenfalls die Zahlungsdetails zukommen lassen. Dafür benötigen wir unbedingt eine Benachrichtigung, sobald ein Gast ein Angebot angenommen hat.

   Wir versenden täglich Angebote über Mews an unsere Gäste. Sollten sie das Angebot nicht annehmen oder nicht darauf reagieren, erhalten wir die Benachrichtigung „Angebot abgelaufen“ bzw. „Optionsende erreicht“. Anschließend können wir dem Gast eine Erinnerung senden oder weitere Schritte einleiten.
   Wenn der Gast das Angebot storniert, wird die optionale Buchung automatisch aus dem System entfernt. Doch was passiert, wenn der Gast das Angebot annimmt? Die Buchung wird zwar im System fixiert, wir erhalten darüber jedoch keine Benachrichtigung. Dadurch kann es passieren, dass bestätigte Buchungen im System übersehen werden.
   Wir möchten die Gäste nach der Annahme kontaktieren, uns für die Buchung… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   idea to upvote  ·  0 comments  ·  Booking engine API  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Expose Issuer of Bills via Connector API (bills/getAll)

   Expose the Issuer when you fetch Bills.
   Then you can use that information to find out who created/issued the Bill.
   This is also useful if you export Bills as Invoices so that it is possible to add 'Our Reference' on created Invocies in other systems.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   idea to upvote  ·  0 comments  ·  Connector API  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Telephone number make the field mandatory and block unsupported formatting before saving

    We have trouble with synchronization between Best Western CRS and MEWS.

    If you write certain phone number formats in the guest profile, including hyphens, which are not supported and this will prevent the reservation from syncing correctly to Best Western CRS.

    If the reservation do not sync, Best Western can not see the reservation and can overbook the hotel.

    We are having overbooking problems because of this.

    Can we make the phone number field mandatory and block unsupported formatting before saving?

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    idea to upvote  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. enhance get channel manager to work similar to get all reservations returning data for all reservations.

    At the moment, the Get reservation channel manager details endpoint is designed with a couple of limitations:
    • It supports a maximum of 100 reservations per request
    • It requires a reservation ID array to be provided
    it is practically impossible to use in for our dwh integration as we need to fetch this information for all reservations in MEWS.
    
    So i suggest to make it same as get all reservationss endpoint returning all data for all reservations
    1. The ability to make the reservation ID array optional, so the endpoint could behave similarly to Get reservations while returning only Channel Manager–specific attributes

    At the moment, the Get reservation channel manager details endpoint is designed with a couple of limitations:
    • It supports a maximum of 100 reservations per request
    • It requires a reservation ID array to be provided
    it is practically impossible to use in for our dwh integration as we need to fetch this information for all reservations in MEWS.
    
    So i suggest to make it same as get all reservationss endpoint returning all data for all reservations
    1. The ability to make the reservation ID array optional, so the endpoint could behave similarly to Get reservations while returning only… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    idea to upvote  ·  1 comment  ·  Channel manager API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Webhook for closed bills

    To retrieve new bills, we currently poll the getAll bill endpoint every minute — even when no new bills are available. As the number of integrated properties increases, this generates a significant and unnecessary volume of traffic on the Mews API.

    We'd like to propose a solution: implementing a webhook that notifies the integration whenever a bill is closed, including the corresponding billId. This would allow us to retrieve and process only the relevant bill, rather than repeatedly polling the full list.

    We believe this change would meaningfully reduce API load on both sides while improving the efficiency and reliability of our integration.

    To retrieve new bills, we currently poll the getAll bill endpoint every minute — even when no new bills are available. As the number of integrated properties increases, this generates a significant and unnecessary volume of traffic on the Mews API.

    We'd like to propose a solution: implementing a webhook that notifies the integration whenever a bill is closed, including the corresponding billId. This would allow us to retrieve and process only the relevant bill, rather than repeatedly polling the full list.

    We believe this change would meaningfully reduce API load on both sides while improving the efficiency and reliability… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    idea to upvote  ·  0 comments  ·  Webhooks  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Allow customers to access Mews audit/security logs for SIEM integration

    Posted on behalf of JnCQUOI Beach Club: the property would like access to Mews audit/security logs for SIEM integration, so their security team can monitor suspicious activity and investigate incidents more effectively.

    0 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    idea to upvote  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Es wäre schön ein Bankingmodul ähnlich dem in HS 3 zu integrieren

    Es wäre schön ein Bankingmodul ähnlich dem in HS 3 zu integrieren, welches offene Rechnungen gleich bei evtl. Zahlungseingängen automatisch verbucht und als bezahlt anzeigt. Das lief sehr gut bei HS 3 und erleichterte die Arbeit ungemein.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    idea to upvote  ·  0 comments  ·  Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Support guest-to-guest relationship types via Connector API

    Currently, guest-to-guest relationship types (such as parent/child or other underage-related relationships) are available in the Mews UI, but they cannot be created or updated through the Connector API.

    For integrations operating in countries where local regulations require declaring relationships between adults and underage guests, this limitation prevents full legal compliance through automated check-in flows.

    We would like to request support for creating and managing guest relationship types via the Connector API, including underage-related relationships already supported in the UI.

    This enhancement would help partners maintain regulatory compliance while keeping the guest registration process fully automated.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    idea to upvote  ·  0 comments  ·  Connector API  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Automatic closing of same-day availability at a fixed time every day across all our Mews accounts

    Every day, at the end of the afternoon, our reception teams manually close same-day availability on each of our Mews accounts in order to avoid receiving late bookings that we would not be able to accommodate.

    This process is quite time-consuming and remains prone to errors since it is carried out manually.

    That would be great to have a way to automate this action every day at 5:30 PM across all of our Mews accounts.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    idea to upvote  ·  0 comments  ·  Integrations  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Per-channel control for “Send confirmation email to channel reservations” (enable for Amadeus/GDS only, exclude OTAs)

    Hello all, I am raising this request on behalf of the property "Knickerbocker On The Lake".
    The property needs to automatically send Mews confirmation emails only for GDS/Amadeus reservations, while not sending Mews confirmations for OTA reservations.
    Today, the “Send confirmation email to channel reservations” setting in the bookable service is all‑or‑nothing for all Channel Manager reservations. If we turn it on, Mews sends confirmations for all channels (GDS + OTAs). If we leave it off, Mews does not send confirmations for any channel reservation.
    The desired behavior is more granular control over which channel reservations get automatic confirmations, for example:
    Per‑channel toggle for confirmations: extend the “Send confirmation email to channel reservations” logic so it can be configured at channel level, not just service level.
    Example configuration:
    Amadeus: ON
    GDS X: ON
    Booking.com: OFF
    Expedia: OFF

    Hello all, I am raising this request on behalf of the property "Knickerbocker On The Lake".
    The property needs to automatically send Mews confirmation emails only for GDS/Amadeus reservations, while not sending Mews confirmations for OTA reservations.
    Today, the “Send confirmation email to channel reservations” setting in the bookable service is all‑or‑nothing for all Channel Manager reservations. If we turn it on, Mews sends confirmations for all channels (GDS + OTAs). If we leave it off, Mews does not send confirmations for any channel reservation.
    The desired behavior is more granular control over which channel reservations get automatic confirmations, for… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    idea to upvote  ·  0 comments  ·  Channel manager API  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. iCal export option

    Hi,
    there are some new OTA-s which would be able to get Mews's availibility if an ical export could be taken out from Mews.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    idea to upvote  ·  0 comments  ·  Channel manager API  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Lock reservation after online check-in time change

    When a reservation is locked in Mews (to ensure the guest keeps the specific room they have been assigned), the reservation currently becomes unlocked if the guest updates their check-in time during online check-in (e.g. via Duve).

    This creates a risk that the room assignment can be changed afterwards without us noticing, since we do not receive any notification that the reservation was modified and unlocked.

    Proposed improvement:
    If a reservation is locked, changes made during online check-in (such as check-in time updates) should not automatically unlock the reservation. Alternatively, Mews could keep the reservation locked or automatically re-lock it after the change.

    When a reservation is locked in Mews (to ensure the guest keeps the specific room they have been assigned), the reservation currently becomes unlocked if the guest updates their check-in time during online check-in (e.g. via Duve).

    This creates a risk that the room assignment can be changed afterwards without us noticing, since we do not receive any notification that the reservation was modified and unlocked.

    Proposed improvement:
    If a reservation is locked, changes made during online check-in (such as check-in time updates) should not automatically unlock the reservation. Alternatively, Mews could keep the reservation locked or automatically re-lock it… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    idea to upvote  ·  0 comments  ·  Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Add HMAC payload signing for General Webhooks

    General Webhooks authenticate via a token in the URL works, but URL tokens can leak through server logs and proxies.

    this is usually solved with HMAC-SHA256 signing. A signature header computed from the request body using a shared secret. The receiver verifies the hash, the URL stays non-sensitive.

    We're building on the Connector API and had to add workarounds to compensate.

    Would be great to have this natively.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    idea to upvote  ·  0 comments  ·  Webhooks  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating