Royal Caribbean Cruise Intelligence & Fare Monitor avatar

Royal Caribbean Cruise Intelligence & Fare Monitor

Pricing

Pay per usage

Go to Apify Store
Royal Caribbean Cruise Intelligence & Fare Monitor

Royal Caribbean Cruise Intelligence & Fare Monitor

Pricing

Pay per usage

Rating

0.0

(0)

Developer

עמית נחום

עמית נחום

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Categories

Share

A direct, deterministic Royal Caribbean scraper for Apify. It reads Royal Caribbean's public cruise-search GraphQL response and emits one record per sailing.

What it returns

  • Stable cruise and sailing IDs
  • Departure and return dates, duration and availability
  • Ship, destination, embarkation port and ports of call
  • Interior, ocean-view, balcony and suite prices when available
  • Currency and lowest available price
  • Full day-by-day itinerary with arrival and departure times
  • Main itinerary image, ship image, route map and booking URL
  • UTC observation timestamp

The Actor refreshes Royal Caribbean's current destination, departure-port, ship and special-sailing codes at runtime. Empty filters are omitted. Results are expanded to individual sailings and deduplicated by sailing_id.

Fare monitoring

Every run stores its latest snapshot in the named royal-caribbean-price-history key-value store. PRICE_CHANGES in the run's default key-value store reports price increases, decreases, sold-out categories and categories that became available. Use an Apify schedule and run-finished webhook for alerts.

Input

Use the Apify form or JSON. Dates use YYYY-MM-DD. sailing_to must not precede sailing_from; night ranges and result limits are validated before any request.

The public cruise-search source currently returns USD in the verified flow. Other sales markets are intentionally not exposed until their locale/session flow can be verified.

Pricing

The Actor is prepared for Apify pay-per-event pricing at $0.25 per 1,000 sailing records ($0.00025 per record). A record is charged only when it is successfully written to the default dataset, and Apify's maximum-cost-per-run limit is respected. Private and free development runs remain compatible until pay-per-event monetization is enabled in Apify Console.