Visit Logo
platform / hospitality / galaxy api

Expand your world with
one powerful connection

The Galaxy API is your single, powerful connection to the entire VISIT ecosystem. Built for openness and flexibility, our API-first platform empowers you to build, extend, and integrate on your own terms. Distribute your products, create unique packages, and design custom booking experiences without limits.

Feature overview

Extensive Product & Content Support

Access, distribute, and package accommodation, activities, transport, and other tourism products available within the ecosystem. Content is also supported, with CBIS under the hood, giving you a powerful way to work with rich product information alongside live inventory.

Real-Time Availability & Booking

Perform live searches for availability and pricing, and manage the full booking flow through the API for connected, up-to-date guest experiences.

Dynamic Packaging Engine

Combine hotels, activities, ferry tickets, and other products into flexible packages that increase guest value and support more relevant, sellable offers.

Robust Developer Resources

Get started quickly with comprehensive documentation, a dedicated test environment, and guaranteed backward compatibility for stable, long-term integrations .

Hybrid Checkout for Seamless Guest Flows

Build the guest experience your way, while we handle the complex parts of checkout and payment. This helps bookings flow seamlessly into the wider ecosystem, including back office processes and My Page.

Build your business, your way

Build your business, your way

Our API-first philosophy puts you in control. Instead of forcing your business to fit our system, we provide the tools for you to shape our system around your business. Use the Galaxy API to build a custom booking engine, integrate with your existing e-commerce platform, or distribute your travel products to a global network of third-party sellers. The result is a seamless, one-of-a-kind travel experience for your customers, powered by you.

Key points:

  • Drive Innovation: Create custom solutions and unique guest experiences.
  • Expand Your Reach: Connect to a network of OTAs, tour operators, and travel agents.
  • Increase Efficiency: Automate data synchronization and reduce manual work.

FAQ

Something unclear? You’ll find answers to some of the most common questions here. And if you’d rather talk it through, we’re always here to help.

CONTACT US

What is the Galaxy API?

The Galaxy API is a REST API for searching, booking and managing travel products in the VISIT ecosystem – accommodation, activities and transport including ferries and flights. It is the distribution-side API: rather than managing one property's operations, it lets an external seller search and book across the inventory VISIT connects, which is what a tour operator or reseller needs.

Who is the Galaxy API for?

Travel businesses, tour operators and third-party sellers who want to sell VISIT-connected inventory through their own channels – integrating accommodation, activities and transport into their own site or booking system. The commercial point is that you sell a broader product range without contracting each supplier individually or holding any inventory yourself, which is what makes a small operator able to offer a full itinerary.

Which products can be booked through the Galaxy API?

Hotels, cabins and apartments, activities, and transport including ferries and flights. Easy Access activity products are not supported. That exclusion is worth checking against your own product mix early, because discovering a gap after building an integration is expensive – and an API that publishes its limitations is easier to plan against than one that does not.

How do we get access to the Galaxy API?

Access requires a signed agreement and an API key. Once those are in place you get technical documentation and a test environment, so the integration can be built and validated before it touches live bookings. Ask about rate limits, versioning policy and how breaking changes are communicated at the same time – those three determine the long-term maintenance cost of the integration rather than the build cost.