Royal Caribbean Scraper - Complete Cruise Data Extractor

Royal Caribbean Scraper This scraper extracts cruise data from Royal Caribbean's GraphQL API and outputs structured cruise information. ### Platform Compatibility - Output Format: Structured cruise data with pricing and itinerary information - Database Schema: Uses standard cruise database tables (cruises, cruise_price_history, scraper_runs) - Locale Format: Supports multiple regional markets: - royal-caribbean-en_US (USA market) - royal-caribbean-en_GB (UK market) - royal-caribbean-en_AU (Australia market) - royal-caribbean-it_IT (Italian market) - Webhook Handler: Compatible with standard webhook processing ### Configuration Region Parameter: region is a required parameter that must be specified in every actor run. #### Supported Regions - USA - United States market (en_US locale, USD currency) - GBR - United Kingdom market (en_GB locale, GBP currency) - AU - Australia market (en_AU locale, AUD currency) - ITA - Italian market (it_IT locale, EUR currency) Each region uses the appropriate domain, currency, language headers, and office codes that match Royal Caribbean's actual API requirements. ### Regional API Compatibility The scraper automatically configures headers to match Royal Caribbean's regional APIs: USA: royalcaribbean.com with English headers GBR: royalcaribbean.com with language: en-gb, country: GBR Australia: royalcaribbean.com.au with English headers Italy: royalcaribbean.com with language: it, country: ITA, currency: EUR ### Features #### Standard Cruise Data Output - Complete cruise information including itineraries, pricing, and ship details - Dynamic pricing fields for different cabin categories (price_USD_I, classification_USD_I, etc.) - Service charges and port charges in standardized format #### Royal Caribbean-Specific Enhancements Additional optional fields prefixed with rc: - rcStateroomClasses - Detailed cabin information - rcHighlights - Visual highlights/badges - rcPortsDetailedInfo - Enhanced port info with arrival/departure times - rcProductViewLink, rcBookingLink - Direct booking URLs - rcItineraryImages - Additional imagery ### Database Storage Data is stored with company separation: - company: royal-caribbean - locale: en_US, en_GB, en_AU, it_IT - platform: royal-caribbean-en_US, royal-caribbean-en_GB, etc. This maintains clear separation of data by cruise line and regional market. ### Example Usage Single destination (Mediterranean cruises from Italy): json { "region": "ITA", "maxRows": 100, "destinations": ["EUROP"], "useApifyProxy": true } Multiple destinations (Caribbean and Europe from UK): json { "region": "GBR", "maxRows": 100, "destinations": ["CARIB", "EUROP"], "useApifyProxy": true } All major destinations (global cruises 12+ nights): json { "region": "ITA", "maxRows": 50, "destinations": ["ALCAN", "AUSTL", "CARIB", "EUROP", "FAR.E", "HAWAI", "ISLAN", "T.ATL", "T.PAN", "TPACI"], "useApifyProxy": true } Popular USA destinations (matching Royal Caribbean's search patterns): json { "region": "USA", "maxRows": 20, "destinations": ["BAHAM", "BERMU", "CARIB", "EUROP", "HAWAI", "MEXCO", "T.PAN"], "useApifyProxy": true }