Cruise Itinerary API
Overview
Cruise sailings, day-by-day itineraries, weekly fare history, port traffic and a cruise price index
Cruise Itinerary is a transportation API. Requests are authenticated with an API key. It is served over HTTPS and allows browser requests (CORS).
At a glance
- Authentication
- API key
- HTTPS
- Yes
- CORS
- Yes
- Category
- Transportation
Questions
Does the Cruise Itinerary API need an API key?
Yes. The Cruise Itinerary API uses API key authentication; the documentation explains how to get credentials.
Can I call the Cruise Itinerary API from the browser?
Yes. The Cruise Itinerary API sends CORS headers, so a web page can call it directly with fetch().
Does the Cruise Itinerary API support HTTPS?
Yes, the Cruise Itinerary API is served over HTTPS.
What are alternatives to the Cruise Itinerary API?
Other Transportation APIs include airportsapi, Transport for London, England, Uber, Transport for Spain, Amadeus for Developers.
Similar transportation APIs
Compare alternatives →
airportsapi
TransportationGet name and website-URL for airports by ICAO code
Transport for London, England
TransportationDiscover TFL APIs
Uber
TransportationUber ride requests and price estimation
Transport for Spain
TransportationPublic trains of Spain
Amadeus for Developers
TransportationTravel Search - Limited usage
Boston MBTA Transit
TransportationStations and predicted arrivals for MBTA
Listed from public-apis (MIT).