Cruise API data & coverage

What cruise data can you work with?

Itineraries

The voyage and its route provide the foundation for destination discovery. Use itinerary information to help travellers distinguish sailings with different ports and durations.

Ships and cruise lines

Ship and line information helps users narrow their search. A ship appearing in the catalogue does not imply that every departure for that ship is present.

Ports and departures

Ports and departure dates connect a traveller's destination interests with when and where a sailing begins. Coverage and field completeness should be checked against your intended routes.

Observed price changes

Price observations provide context about changes recorded over time. They are not a live quote, cabin-availability check or promise that a displayed fare can still be booked.

Historical sailing records

Retained sailing records help explain how collected information changed. Their scope depends on the observations collected; missing periods must not be represented as unchanged prices.

Archived expired cruises

Expired cruises can remain useful for historical research and route context. Archived sailings must be clearly separated from upcoming departures in customer-facing search results.

Six currently supported cruise lines

Drift currently supports Royal Caribbean, Celebrity, Norwegian, MSC, Virgin Voyages and Azamara. These are the supported data sources for the private preview.

Support does not mean complete inventory, every cabin fare or an official partnership with a cruise line. Before choosing an integration, evaluate the particular ships, regions, departure windows and fields your business needs. A catalogue-level count alone cannot establish that fit.

For example, a comparison website focused on Mediterranean departures needs relevant route and date coverage, while an app focused on a particular ship needs useful records for that ship. Both may use the same source but need different validation.

How to interpret price history

Treat an observed price as a record of what was collected, not as an offer guaranteed to remain available. A change between two observations tells you that the recorded price changed; it does not establish every price offered in between.

Keep currency and fare context visible when comparing records. Do not present an unknown price as zero, infer a per-person fare without evidence, or convert a historical observation into a current booking quote. Confirm the fields available for your use case during the preview discussion.

The Drift showcase demonstrates saved cruises and in-app alerts. These demonstrate an application built on the data; they are not a promise of email notifications or background push delivery for an API customer.

Freshness and missing data

No guaranteed refresh frequency is advertised for the private-preview plans. Discuss your freshness requirements before access is agreed, including how your product should behave when data is incomplete or an observation is older than expected.

Missing data is not proof that a sailing is sold out, cancelled or unavailable. The cruise line remains the authority for current availability and booking details. Applications should communicate those limits beside observed fares and historical records.

Evaluate coverage before integrating

• Identify the lines, ships and regions your product actually needs.
• Review a representative set of upcoming departures and historical records in a private demo.
• Check field completeness and how unknown values appear.
• Agree access, usage and data requirements before planning a launch.

Next: plan your cruise API integration, view the working Drift app showcase, or compare private-preview pricing.