Unofficial Celebrity Cruises Itineraries

Collect public Celebrity Cruises sailing data from the cruise-search experience. The Actor returns one dataset item per visible sailing date, including itinerary name, ship, sailing dates, ports of call, public detail link, and the visible public starting price.

This Actor is useful for cruise inventory tracking, itinerary research, travel-market monitoring, price snapshots, and importing Celebrity Cruises sailings into your own database or BI workflow.

This Actor is unofficial and is not affiliated with, endorsed by, sponsored by, or otherwise connected to Celebrity Cruises.

Related Actors

Looking for Virgin Voyages data too? Use the Unofficial Virgin Voyages Itineraries scraper.

What It Scrapes

• Public Celebrity Cruises cruise-search result cards
• Itinerary or package name
• Ship name and cruise duration
• Sailing start and end dates when exposed on the public result card
• Public ports of call
• Visible public starting price, currency label, and price basis
• Celebrity package, group, destination, and ship identifiers when exposed
• Source URLs and scrape timestamp

The Actor intentionally stays on public search and itinerary pages. It does not automate checkout, cabin selection, account login, booking, payment, reservation management, or any other non-public purchase flow.

Typical Use Cases

• Track upcoming Celebrity Cruises sailings by date, ship, home port, destination, or duration
• Build a searchable itinerary catalog
• Monitor visible starting prices over time
• Compare sailings across ships, regions, or departure ports
• Feed cruise data into spreadsheets, dashboards, CRMs, or travel-planning tools
• Keep an internal destination or package database up to date

Input

You can run the Actor with no input to scrape the default Celebrity Cruises search page for the USA market. Use filters when you want a smaller, more targeted dataset.

{
  "dateFrom": "2026-08-01",
  "dateTo": "2026-08-31",
  "ships": ["BY"],
  "homePorts": ["MIA"],
  "durations": ["6~8"],
  "destinations": ["CARIB"],
  "maxItems": 50,
  "maxCards": 50,
  "currency": "USD",
  "country": "USA",
  "waitForResultsMillis": 15000,
  "requestDelayMillis": 750
}

Input Fields

Field	Type	Description
startUrls	array	Optional Celebrity Cruises /cruises URLs. Existing query parameters are preserved, and the filters below are added or overwritten.
dateFrom	string	Earliest sailing date to include, in YYYY-MM-DD format. Converted into Celebrity's startDate search filter.
dateTo	string	Latest sailing date to include, in YYYY-MM-DD format. Converted into Celebrity's startDate search filter.
ships	array	Ship codes to include, such as BY Celebrity Beyond, EG Celebrity Edge, SM Celebrity Summit, or XC Celebrity Xcel.
homePorts	array	Departure port codes to include, such as MIA, FLL, SEA, SJU, BCN, ATH, ROM, SYD, TPA, or YVR.
durations	array	Cruise lengths to include: 2~5, 6~8, 9~11, 12~14, or 15~18.
destinations	array	Destination codes to include, such as ALCAN, BAHAM, CARIB, EUROP, GALAP, HAWAI, T.PAN, T.ATL, or TPACI.
voyageType	string	Optional cruise type filter when available, such as OCEAN or RIVER.
maxItems	integer	Maximum number of sailing-date rows to return. The Actor caps this at 250.
maxCards	integer	Maximum number of visible Celebrity result cards to parse from each search page.
currency	string	Currency label attached to parsed public prices. The default is USD.
country	string	Celebrity country query parameter. The default is USA.
waitForResultsMillis	integer	How long to wait for browser-rendered Celebrity result cards.
requestDelayMillis	integer	Delay between Celebrity Cruises search pages. Increase this for gentler, slower runs.

Output

The Actor saves results to the default Apify dataset. Each item represents one visible sailing date from a public Celebrity Cruises search card.

{
  "schema_version": "1.0",
  "cruise_line": "Celebrity Cruises",
  "cruise_line_slug": "celebrity-cruises",
  "itinerary_name": "Grand Cayman, Mexico & Perfect Day",
  "sailing_id": "BY07MIA-2177944375",
  "voyage_id": "BY07MIA-2177944375",
  "package_code": "BY07W680",
  "ship_name": "Celebrity Beyond",
  "duration_nights": 7,
  "sailing_start_date": "2026-08-23",
  "sailing_end_date": "2026-08-30",
  "starting_price": 852,
  "starting_original_price": null,
  "currency": "USD",
  "price_basis": "per person",
  "ports_of_call": [
    "Miami, Florida",
    "Perfect Day CocoCay, Bahamas",
    "Cozumel, Mexico",
    "George Town, Grand Cayman",
    "Nassau, Bahamas",
    "Miami, Florida"
  ],
  "itinerary": [
    {
      "day": 1,
      "port_name": "Miami, Florida",
      "is_sea_day": false,
      "arrival_time": null,
      "departure_time": null,
      "schedule_text": null
    }
  ],
  "cabin_pricing": [
    {
      "cabin_type": null,
      "price": 852,
      "original_price": null,
      "currency": "USD",
      "basis": "per person",
      "source": "public_search_card"
    }
  ],
  "source": {
    "website": "celebritycruises.com",
    "search_url": "https://www.celebritycruises.com/cruises?country=USA",
    "detail_url": "https://www.celebritycruises.com/itinerary/7-nt-grand-cayman-mexico-perfect-day-from-miami-on-celebrity-BY07W680"
  },
  "scraped_at": "2026-06-16T12:33:20.982Z"
}

The dataset also includes compatibility aliases such as cruise_date, cruise_end_date, cruise_price, detail_url, source_url, and flat itinerary fields like stop_1_port, stop_1_arrival_time, and stop_1_departure_time for importers that prefer wide rows.

Public Price Notes

Celebrity currently exposes a visible starting price on public search result cards. The Actor records that visible public price and does not enter checkout or cabin-selection pages, so it should not be treated as a complete live cabin inventory feed.

For trend analysis, schedule repeated runs and compare rows by sailing_id, package_code, starting_price, and scraped_at.

Tips For Better Results

• Use date filters to keep runs focused and easier to review.
• Start with a small maxItems value while testing a new configuration.
• Use maxCards to limit how many browser-rendered result cards are parsed from each search page.
• Increase waitForResultsMillis if the Celebrity site is slow to render result cards.
• Increase requestDelayMillis for larger runs or when you want to reduce request intensity.
• Use ships, homePorts, destinations, and durations together to create clean segments for dashboards.
• Store historical datasets instead of overwriting them if you want price-change reporting.

Limitations

• Results depend on what Celebrity Cruises makes visible on public pages at scrape time.
• Public prices can change, disappear, or differ from prices shown later in the booking process.
• Day-by-day arrival and departure times are not always visible on Celebrity search cards.
• The Actor does not verify availability beyond the public search-card result.
• Website layout changes may require parser updates.

Exporting Results

After a run finishes, open the Actor dataset in Apify to preview, filter, download, or connect the results. Common export formats include JSON, CSV, Excel, XML, RSS, and HTML table. For downstream systems, use sailing_id as the sailing-level identifier and package_code as the itinerary/package-level identifier.

Public-Page Compliance

This Actor is designed for public itinerary research. It avoids automated access to checkout and choose-a-cabin routes and does not collect account, payment, passenger, or booking data.