Cruise inventory data

Cruise data for every line and sailing

Q: What formats is the cruise data available in?

CSV, JSON or a REST API. Managed plans can push scheduled exports straight to Amazon S3, Snowflake or PostgreSQL.

Clean, normalized cruise data from 60+ cruise lines — itineraries, dates, ports and lead prices, plus full ship specs. One record per sailing, deduped and refreshed up to daily, as CSV, JSON or API.

Get a free sample See the schema

60+ cruise lines CSV, JSON & API Deduped records Refreshed up to daily

sailing.json — one record

{
  "cruise_line": "MSC Cruises",
  "ship_name": "MSC World Europa",
  "title": "7-Night W. Mediterranean",
  "departure_date": "2026-09-12",
  "return_date": "2026-09-19",
  "nights": 7,
  "embark_port": "Barcelona",
  "region": "Western Mediterranean",
  "price_amount": 799,
  "price_currency": "USD",
  "ship": { "gross_tonnage": 215863, "decks": 22, "cabins": 2626 },
  "scraped_at": "2026-06-28T04:12:00Z"
}

The schema

What's in the cruise data

One predictable, flat record per sailing — the same fields on all 60+ lines, ready to drop into a database or search index.

Field	Type	Example
cruise_line	string	"MSC Cruises"
ship_name	string	"MSC World Europa"
title	string	"7-Night W. Med"
departure_date	date	"2026-09-12"
return_date	date	"2026-09-19"
nights	number	7
embark_port	string	"Barcelona"
itinerary	object[]	[{day, port, country}]
price_amount	number	799
price_currency	string	"USD"
ship	object	{ tonnage, decks, cabins, … }
scraped_at	datetime	"2026-06-28T…"

Built to drop straight in

The same field names, types and units on every one of the 60+ cruise lines.
Flat, normalized records — no nested per-line quirks to flatten yourself.
De-duplicated across sources, with consistent IDs so joins and diffs stay clean.
Every record carries a last_updated timestamp.

Get a free sample Explore the cruise API

Formats & delivery

Get the data however your stack wants it

Pull from the REST API or receive files on a schedule. Managed plans push straight to your warehouse.

REST API

JSON

CSV

Amazon S3

Snowflake

PostgreSQL

Who uses cruise data

From booking sites to pricing models

Teams that need the whole cruise market as one reliable dataset, without building scrapers.

OTAs & travel agencies

Populate search and listing pages with live itineraries, dates and lead prices across every line.

Analysts & BI teams

Track capacity, itineraries and competitor pricing over time in your warehouse and dashboards.

Data & ML teams

Train pricing and demand models on a clean, consistent history instead of brittle raw scrapes.

Cruise data FAQ

Questions about the cruise data

What is included in the cruise data?

One record per sailing with cruise line, ship, departure and return dates, itinerary, ports, lead price and currency — plus ship specs (capacity, decks, cabins) — across 60+ cruise lines.

What formats is the cruise data available in?

CSV, JSON or a REST cruise API. Managed plans can push scheduled exports straight to Amazon S3, Snowflake or PostgreSQL.

How current is the cruise data?

Refreshed up to daily. Every sailing carries a last_updated timestamp so you always know how fresh a record is.

Is the cruise data normalized across lines?

Yes. Every cruise line uses the same field names, types and units, and records are de-duplicated with consistent IDs so the data drops straight into your database.

Can I get a free sample of the cruise data?

Yes. Tell us which cruise lines and regions you need and we'll send a free sample so you can see the exact schema before you pay.

Get clean cruise data this week

Start with a free sample of your cruise lines and region, see the exact schema, then connect once and build on data that's already clean and deduped.

Get a free sample See pricing