Senior Software Engineer

Contactless hotel check-in for Mews, Cloudbeds & Apaleo: how PMS integration actually works. See how LOXE's contactless check-in software integrates with Mews, Cloudbeds, and Apaleo - real-time API sync, smart lock key delivery, and 48-hour setup. How does contactless check-in integrate with your existing PMS? Contactless hotel check-in software connects to your property management system through a direct API integration - not a data export or manual sync. If you're running Mews, Cloudbeds, or Apaleo, LOXE pulls your reservation data in real time, matches each booking to a guest-facing check-in flow, and pushes status updates back to your PMS automatically. Guests complete ID verification, digital registration, and key delivery from their phone, while your PMS reflects every step as it happens. No double-entry. No front-desk bottleneck. This matters for independent hotels running 20-200 rooms because you probably don't have a dedicated IT team managing middleware or custom connections. A native PMS integration means LOXE reads your existing room types, rate plans, and reservation details, then builds the contactless check-in experience on top of what you already have. Your PMS stays your system of record. LOXE is the guest-facing layer. What data syncs between LOXE and your PMS? The integration is bidirectional. LOXE pulls reservation details from your PMS: guest name, email, stay dates, room type, rate code, and payment status. Once the guest completes their check-in flow, LOXE pushes back verified ID status, a signed digital registration card, room assignment confirmation, and key delivery timestamp. If a guest upgrades through LOXE's pre-arrival upsell engine - early check-in, room upgrade, late checkout, parking - that charge posts directly to the PMS folio. Changes in either system sync within seconds. Cancel a reservation in Mews? LOXE voids the pending check-in link. Reassign a room in Cloudbeds? LOXE updates the key code automatically. For properties using smart locks like Dormakaba Oracode, Salto, or TTLock, key delivery also triggers lock programming - the code or mobile key activates only during the guest's confirmed stay window. No manual lock management required. PMS integration compatibility: LOXE x Mews, Cloudbeds, and Apaleo. | Feature | LOXE x Mews | LOXE x Cloudbeds | LOXE x Apaleo | | Sync Type | Real-time bidirectional API | Real-time bidirectional API | Real-time bidirectional API | | Reservation Pull | Automatic - confirmed bookings in seconds | Automatic - confirmed bookings in seconds | Automatic - confirmed bookings in seconds | | ID Verification | Photo ID + selfie match, encrypted storage | Photo ID + selfie match, encrypted storage | Photo ID + selfie match, encrypted storage | | Key Delivery | Mobile key, digital code, or smart lock (Dormakaba, Salto, TTLock) | Mobile key, digital code, or smart lock (Dormakaba, Salto, TTLock) | Mobile key, digital code, or smart lock (Dormakaba, Salto, TTLock) | LOXE also integrates with Maestro, Opera, and Impala using the same bidirectional model. All integrations include automatic upsell folio posting and go live in under 48 hours with no hardware install. If your PMS isn't listed, the onboarding team maps your API during a pilot phase - most custom connections are production-ready within one week. What does PMS integration setup look like? Setup doesn't require an IT department or a PMS migration. Here's the typical process for a 50-room independent hotel. Step 1 - Connect: You provide API credentials from your PMS dashboard. Mews, Cloudbeds, and Apaleo all offer these in their settings panel. LOXE's onboarding team maps your room types, rate plans, and reservation sources. Step 2 - Configure: Choose your check-in flow - ID verification method, key delivery type (mobile key, digital code, or smart lock), upsell offers, and pre-arrival email timing. Step 3 - Test: LOXE runs a sync test with your live reservations in read-only mode. You'll see real bookings in the LOXE dashboard before anything goes guest-facing. Step 4 - Go live: Activate guest-facing check-in links. Your PMS continues operating exactly as before - LOXE layers on top, not in place of. Most properties complete all four steps in under 48 hours. No hardware ships. No PMS data leaves your existing stack. Frequently asked questions. How does the LOXE-PMS integration work? LOXE connects through a certified API. Reservation data flows automatically - no CSV imports, no manual entry. New bookings, modifications, and cancellations sync within seconds. How much setup effort is required? You provide API credentials and LOXE handles the mapping. No code, no IT contractor, no PMS migration. Most properties go live in under 48 hours. How reliable is the data sync? The bidirectional sync runs continuously. If a reservation changes in Mews, Cloudbeds, or Apaleo, LOXE reflects the update within seconds. If connectivity drops, the system queues changes and syncs once reconnected - no data loss. Do guests see the PMS or LOXE? Guests only see LOXE's branded check-in flow. Your PMS runs in the background as the system of record. The experience feels native, not like a third-party bolt-on. Is the integration compliant with PIPEDA and Quebec's Law 25? Yes. LOXE stores guest data in encrypted Canadian-hosted infrastructure. Data sharing with your PMS is limited to reservation needs - no third-party transfers, no cross-property tracking. Full PIPEDA and Loi 25 compliance is built in. See it with your own PMS. Book a LOXE demo with your actual PMS connected. You'll see your real rooms, real reservations, and real check-in flows on screen - not a generic slideshow. If you're running Mews, Cloudbeds, or Apaleo, the integration is pre-built and ready to demo on your live data. Maestro, Opera, and Impala properties can request a live API mapping during the same call. Most hotels go from first demo to live guest check-ins in under 48 hours. No long-term contract required for the pilot. Your PMS stays exactly where it is - LOXE just makes it guest-facing.

Otherwander Soho selects Apaleo to power fully digital pod hotel concept. Anna Fechner Otherwander Soho, the newly opened 566-pod hotel in central London, has selected Apaleo, the API-first property management platform, to power its fully digitised guest journey and highly streamlined operating model. Opened on 1 June 2026 at 92 Dean Street in the heart of Soho, Otherwander Soho has built its technology ecosystem around interoperability, automation and real-time data flow. Rather than placing the property management system (PMS) at the centre of operations, the hotel has adopted a middleware-led architecture in which systems connect through open APIs and data moves across the business in real time. Within that architecture, Apaleo's open platform provides the inventory and guest data layer, helping Otherwander centralise key operational data while giving the brand the flexibility and interoperability to build, adapt and scale its fully digital operating model over time. Using a fully digital guest journey, Otherwander Soho combines sleep-only single and double pods with premium shared facilities, creating a compact, design-led stay for modern urban travellers. Guests check in online and access both the building and their pod using a QR-enabled Wanderpass stored in their mobile wallet, removing the need for a traditional reception desk and creating a frictionless journey from arrival to departure. The decision to work with Apaleo resulted from a four-and-a-half-year technology evaluation process that included traditional hospitality platforms, all-in-one technology suites, and alternative architectural models. Otherwander Soho selected Apaleo because its API-first architecture is best aligned with the company's middleware-led strategy, providing full flexibility to support custom development, create a fully digital guest journey and continuously evolve the technology ecosystem over time. Apaleo's collaborative approach made it a true growth partner for Otherwander's innovation-led greenfield project. Inspired by airlines and e-commerce, Otherwander Soho has created a hospitality model built around how people travel today, prioritising efficiency, flexibility and convenience. Designed with future growth in mind, its unique architecture gives the brand the flexibility to evolve its technology ecosystem and scale the concept into new locations over time. The project also reflects a wider industry shift away from rigid legacy systems towards open, interoperable ecosystems that support continuous innovation. Ulrich Pillau, CEO and Founder of Apaleo, said: "What's particularly interesting about Otherwander Soho is that they evaluated technology through the lens of the operating model they wanted to create. They prioritised openness, interoperability and flexibility because they understood that innovation doesn't come from a single system. It comes from creating an ecosystem where data, applications and workflows can work together. As hospitality becomes increasingly automated and AI-driven, we're seeing more hospitality brands adopt this approach. I would also like to congratulate the entire Otherwander team on bringing such a fantastic concept to life." Sophie Hartley, Director of Technology & Digital Strategy at Otherwander Soho, said: "From the outset, Apaleo GmbH. knew Apaleo GmbH. wanted to create a fully digitised customer journey, but Apaleo GmbH. also wanted a middleware-led architecture where the PMS became part of the ecosystem rather than the centre of it. Apaleo's open APIs were critical because they allowed Apaleo GmbH. to connect systems, centralise data and build a technology ecosystem that can continue to evolve. Beyond the technology itself, Apaleo GmbH. found a true partner in Apaleo. Their openness, flexibility and willingness to listen and collaborate made it possible to build the architecture Apaleo GmbH. had envisioned from day one." Fredrik Korallus, CEO of Otherwander Soho, said: "From the beginning, our objective wasn't simply to do something different. It was to simplify. We wanted to remove friction from the guest journey and eliminate complexity from hotel operations. Too often, hospitality relies on disconnected systems, fragmented data and processes that create unnecessary work for teams and unnecessary frustration for guests. We needed technology partners that shared our vision for a more connected, intuitive way of operating, and Apaleo helped us turn that vision into reality."