Skip to content
Request a demo

Menu

Data & Services · The API channel

One API for content, search, pricing and booking

Sailings, cabins and prices from each cruise line in one normalized model, on the agreements and rates your customers already have, behind the front end you already run.

Request API access
A developer console for the API channel in a sandbox: a search request for balcony cabins on Western Mediterranean sailings as JSON, and the JSON response listing matching sailings with ship, ports, cabin category, from price and availability.
An order confirmed event delivered to the partner's webhook endpoint, as JSON.

What you get

Cruise in your product without one integration per cruise line

  • One integration instead of one per cruise line

    The problem today

    • Every cruise line has its own interface, fare codes, cabin categories and booking rules.

    What changes

    • One schema for every cruise line with fares, cabins and booking rules in the same shape.

  • Content included in 20+ languages

    The problem today

    • Cruise content is a project of its own, with ship photos, cabin descriptions and itineraries often bought from a separate provider.

    What changes

    • Ship and cabin images, deck plans, itineraries and destination texts come with every cruise line in 20+ languages.

  • Take only what you need

    The problem today

    • Not every platform needs booking and payments on day one.

    What changes

    • Start small and add services and functionality at your own pace.
    • Your front end and design stay yours.

Why Dreamlake

Built for cruise, not adapted to it

  1. One shape for every cruise line

    Fares, cabin categories and booking rules arrive normalized. A new cruise line changes your coverage, not your code.

  2. Rates your customers negotiated

    We connect with the cruise line credentials your customers already have, so the fares they negotiated come through.

  3. Content in local languages

    Images, deck plans and texts in 20+ languages, maintained by our content team.

  4. Your product stays yours

    Call only what you need. You keep the customer relationship, the front end and the booking session.

Cruise lines
50+
Sailings available
45K+
Destinations
4K+
Travelers served
20M+

Dreamlake Commerce

When you want a ready-made front end

Want a ready cruise site or advisor portal as well? Traveler Storefront and Travel Advisor run on the same catalog and orders as the API.

  • A partner-branded cruise storefront: a search for Western Mediterranean sailings in May and June for two adults, filters for port, cabin type, price and cruise line, and results with the balcony price per person and an installment option.

    Traveler Storefront

    Search, cabin selection and checkout branded for your customers.

  • An advisor's quote screen: client details, the sailing and cabin, flight, hotel and transfer lines with live prices, a price breakdown with the package price and the advisor's margin, a cabin hold timer, and buttons to hold the cabin, send the quote or convert it to a booking.

    Travel Advisor

    Quotes, packages and bookings for office and home-based agents, with margin in view.

  • A developer console for the API channel in a sandbox: a search request for balcony cabins on Western Mediterranean sailings as JSON, and the JSON response listing matching sailings with ship, ports, cabin category, from price and availability.

    Data & Services

    Cruise content, search, pricing and booking as APIs.

Build on cruise content you never have to maintain.

Integrate once. We maintain the cruise line connections and the content and add new cruise lines behind the same API.

Tell us what you are building. Our integration team will reply and, once we have talked, set up API access.

We use your email only to reply and to follow up about Dreamlake. Read our privacy notice.