Mews API

Looking back at my time at Mews, we’ve grown our tech teams with a great mix of people with and without hospitality experience. What I’ve noticed (coming from a hospitality background) is that I’ve taken a lot of what I know about the industry for granted. What I may have thought as general knowledge is actually not. There are so many aspects of hospitality that have come as second nature to us that we don’t really think twice about. On the other hand, when building custom integrations, I would think that developers don’t necessarily have the full picture of what the final outcome should be. So that leads to my question: Are there any challenges that come up when working with developers that don’t have hospitality experience? How do you bridge those gaps? Or do you not experience these challenges at all?I’m really interested to hear your experiences!

Here are some misconceptions that could occur when a hotelier considers building a booking engine via open API within a PMS:  It’s quick and Easy: Building a booking engine integrated in a PMS might seem straightforward, especially if there are existing open API or frameworks available. However, integrating a booking engine involves considerations such as real-time availability updates, pricing synchronization, and seamless data flow between the booking engine and other modules of the PMS. It requires careful planning and development to ensure smooth functionality and guest experience.  One size don’t Fit All: Each integration is unique, depending on factors such as the PMS provider, the complexity of the booking engine, and specific business requirements. Assuming that a generic integration solution will work for all situations could lead to compatibility issues, data inconsistencies, and sub-optimal performance.  It’s just a technical task: Building an integration involves more t

Within the vibrant ecosystem of Mews, where innovation and progress are constants, developers often find themselves at the forefront of change. As we journey through this dynamic landscape, it's inevitable that we encounter pivotal questions that shape our approach to development within the Mews platform:  How do you keep up with Mews updates and deprecations? What are the costs associated with adapting to these updates? How long does it typically take for an update to be implemented? In what manner would you prefer Mews to release these updates?  Join the conversation and share your perspectives on these crucial topics in the comments below!

Study the certification process in order to prepare for what's to come.Allocate for sufficient time for API reviews, feedback and potential bug fixes to the integration until it passes certification successfully.Document the milestones listed above and share the document with the Mews Technical Partnership team. This will facilitate the API reviews and eventual creation of your integration.Have you found a process or step that helped you prepare for certification?