NCL (Norwegian Cruise Line) Scraper

Apify actor for scraping NCL itineraries with locale-aware endpoints, aligned with existing Costa and Royal Caribbean dataset formats.

• Supported markets (region): it_IT, en_US, en_GB

Usage

npm i
npm run start:dev

Input (key-value store INPUT.json):

Apify Proxy (recommended):

{
  "region": "it_IT",
  "maxRows": 500,
  "useApifyProxy": true,
  "useSessionPool": true,
  "apifyProxyCountryCode": "IT",
  "apifyProxyGroups": "RESIDENTIAL",
  "maxRequestRetries": 3,
  "requestHandlerTimeoutSecs": 30,
  "destinations": ["ALASKA", "caribbean", "mediterranean"]
}

Custom proxy:

{
  "region": "it_IT",
  "maxRows": 500,
  "useApifyProxy": false,
  "proxyUrl": "http://USER:PASS@host:port",
  "useSessionPool": true,
  "maxRequestRetries": 3,
  "requestHandlerTimeoutSecs": 30,
  "destinations": ["ALASKA"]
}

## Destination filtering

- Provide an optional `destinations` array to filter cruises by destination. If omitted or empty, all itineraries are processed.
- Accepted values:
  - NCL destination codes (uppercase), e.g., `"ALASKA"`, `"CARIBBEAN"`, `"MEDITERRANEAN"`.
  - Slug forms (lowercase with hyphens) where applicable, e.g., `"alaska"`, `"caribbean"`, `"mediterranean"`, `"australia-and-new-zealand"`.
- Filtering is applied post-fetch on itinerary items using their `destinationCodes`. Detail requests are only made for itineraries that passed the filter.

Common NCL destination codes:

- AFRICA — Africa
- ALASKA — Alaska
- ASIA — Asia
- AUSTRALIA — Australia & New Zealand
- BAHAMAS — Bahamas
- BERMUDA — Bermuda
- CANADA_NEW_ENGL — Canada & New England
- CARIBBEAN — Caribbean
- EXTRAORDINARY_JOURNEYS — Extraordinary Journeys
- GREEK_ISLES — Greek Isles
- HAWAII — Hawaii
- MEDITERRANEAN — Mediterranean
- MEXICAN_RIVIERA — Mexico
- NORTHERN_EUROPE — Northern Europe
- PACIFIC_COASTAL — Pacific Coastal
- PANAMA_CANAL — Panama Canal
- SOUTH_AMERICA — South America
- SOUTH_PACIFIC — South Pacific
- TRANSATLANTIC — Transatlantic
- WEEKEND — Weekend

Region & Proxy behavior

• Supported regions: it_IT, en_US, en_GB.
• Proxy is required: enable Apify Proxy (RESIDENTIAL, pinned to country derived from region) or provide a geo-matched proxyUrl. Without a proxy, the actor fails early to prevent incorrect market data.
• Session-style rotation: When useSessionPool is true, the actor rotates Apify proxy URLs on HTTP 429/403, and reattempts requests (including detail fetches). For custom proxies, a single provided proxy is reused.

Notes

• Output schema matches existing scrapers (Costa/Royal) for downstream compatibility.
• Cabin categories are mapped into dynamic fields like price_EUR_INSIDE, price_EUR_BALCONY, etc.
• Dates are normalized to ISO using UTC.
• Detail enrichment: when enabled, itinerary details are prefetched with limited concurrency and share the same proxy handling and rotation rules.