Cruise Travel & Booking Scraper

Extracts cruise itineraries and deals from cruise.com and writes them to the dataset as structured JSON.

Use cases

• Compare itineraries, ships and prices across dates
• Track cruise deals and price changes over time
• Feed travel-planning and booking-research pipelines

What it does

The actor downloads each page, parses the cruises, and stores one record per cruise. Each record contains title, price, ship, departure_port, itinerary, dates, description.

• Extraction runs over plain HTTP, so runs are fast
• JSON-LD and embedded page-state data are used when present; otherwise the actor falls back to DOM parsing
• Duplicate records are removed before the dataset is written
• Pagination is followed automatically up to the configured page limit

Output

Sample output

Three example records from a real run:

[
  {
    "title": "5 Day Caribbean-Western",
    "ship": "Radiance of the Seas",
    "departure_port": "Tampa",
    "itinerary": "Roundtrip Tampa",
    "dates": "Aug 15 - Oct 19, 2026",
    "price": "$1700",
    "description": "Radiance of the Seas Roundtrip Tampa Aug 15 - Oct 19, 2026"
  },
  {
    "title": "5 Day Caribbean-Western",
    "ship": "MSC Poesia",
    "departure_port": "Miami",
    "itinerary": "Roundtrip Miami",
    "dates": "Oct 17, 2026 & Oct 16, 2027",
    "price": "$500",
    "description": "MSC Poesia Roundtrip Miami Oct 17, 2026 & Oct 16, 2027"
  },
  {
    "title": "5 Day Caribbean-Western",
    "ship": "Disney Magic",
    "departure_port": "Galveston",
    "itinerary": "Roundtrip Galveston",
    "dates": "Nov 29, 2026 - Mar 12, 2027",
    "price": "$2,800",
    "description": "Disney Magic Roundtrip Galveston Nov 29, 2026 - Mar 12, 2027"
  }
]

Export the dataset as JSON, CSV or Excel from the Dataset tab after the run.

Output schema

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "title": {
      "type": "string"
    },
    "price": {
      "type": "string"
    },
    "ship": {
      "type": "string"
    },
    "departure_port": {
      "type": "string"
    },
    "itinerary": {
      "type": "string"
    },
    "dates": {
      "type": "string"
    },
    "description": {
      "type": "string"
    }
  }
}

Input

Field	Type	Description
startUrls	array	Pages to scrape (defaults to https://www.cruise.com/cruise-destinations/caribbean-cruises/) (default: ["https://www.cruise.com/cruise-destinations/caribbean-cruises/"])
maxPages	integer	Maximum number of pages to crawl before stopping. (default: 10)
maxItems	integer	Maximum number of records to return. Leave empty for no limit.

Pricing

• Pay-per-result: $5.6 per 1,000 results

• Billed per result — you only pay for the records that land in your dataset.

• Volume discounts apply automatically as monthly usage climbs; the "from" price on the store page is the discounted rate.

• Run start: $5e-05 per GB of memory (a 1 GB run starts for a fraction of a cent); results are billed separately.

• There is no subscription or minimum spend. A run is charged only for the records that land in your dataset.

Integrations

The actor runs on the Apify platform: call it from the API or the Python and Node.js SDKs, trigger it on a schedule, send results to webhooks, and pipe the dataset into Zapier, Make, Slack or Google Sheets. The dataset is also LLM-ready -- point any tool that reads JSON at it.

FAQ

How much does a run cost? Pay-per-result only. You are charged for the records that land in your dataset ($5.6 per 1,000 results), with no subscription or minimum. Volume discounts apply automatically on higher monthly usage.

What fields do I get? Each record contains title, price, ship, departure_port, itinerary, dates, description. Fields the source page does not display are omitted -- nothing is fabricated.

How fresh is the data? Extraction reads the live pages at run time. Schedule recurring runs from the platform to keep a monitoring dataset current.

Can I scrape pages other than the default URL? Yes. Pass any URL that matches the site's page structure in startUrls; the actor crawls and extracts from it the same way.

How many records can one run return? Control it with maxPages (crawling depth) and maxItems (a hard cap on returned records).

Is it legal to scrape this data? The actor collects publicly available data only. Check the site's Terms of Service and applicable law (for example GDPR) before bulk collection, and review the platform's own data-collection policy.

How do I export the results? JSON, CSV or Excel from the Dataset tab after the run, or pull the dataset programmatically via the API/SDKs.

What happens if a run fails? The run reports per-record errors instead of failing silently. Retry the run, and open an issue on the Issues tab if a target site keeps blocking extraction.

Limitations

• The actor extracts what the public pages expose. Fields the site does not display are omitted; nothing is fabricated.
• Some sites render content client-side. Extraction follows the live markup, so results can change if the site is redesigned.
• The actor collects publicly available data only. Check the site's Terms of Service and applicable law (for example GDPR) before bulk collection.

Found a problem or want a field added? Open an issue on the Issues tab -- the maintainer responds.