Hotel Explorer
One REST API over 8+ luxury suppliers — Four Seasons, Mandarin Oriental, Expedia, Accor and more. Reverse-engineered undocumented provider APIs and built resumable crawlers: 900+ properties, 50,000+ records across 25 tables.
Eight suppliers, eight dialects
Luxury hotel suppliers like Four Seasons, Mandarin Oriental, Expedia and Accor each expose availability differently, and several don't document their APIs at all. The product needed one consistent way to ask every one of them the same question.
One contract over all of them
I reverse-engineered the undocumented provider endpoints and wrapped every supplier behind a single REST API: search, resolve a reference, fetch rates. The rest of the product only ever talks to that contract.
- Per-provider adapters on the fastest available path
- Normalised currencies and room data
- Clear errors when a supplier is down instead of silent gaps
Crawling without starting over
Static hotel data is pulled by resumable crawlers, so a failure halfway through resumes where it stopped. That harvest now covers 900+ properties and 50,000+ records across 25 tables.
A voice that remembers you
On the same platform I built a real-time voice personalization engine on OpenAI Realtime. Moving preference extraction to a single end-of-call pass cut LLM calls per conversation from 30 to 1 and captured 47% more data points.
Results
Questions people ask
Is Hotel Explorer public?
No. It's an internal VARA5 product, so this page covers the engineering rather than screenshots.
What does reverse engineering mean here?
Watching how supplier websites talk to their own back ends, then calling those same endpoints directly and reliably instead of scraping rendered pages.
