Get cruise details for a known ship ID and SEO name

View all Tripadvisor Hotel, Rental & Travel Data endpoints →

Retrieve cruise detail data using the required shipId and seoName strings, with optional currencyCode. The documentation identifies cruise search results and cruise quick links as sources of the shipId and seoName values. Preserve the supplied seoName rather than assuming it must be converted into a URL slug; the documented example is MSC Magnifica with shipId 15691635. USD is the documented currency example. No saved live probe covers this operation. The truncated documentation response shows data.itineraries.list: entries contain cruiseLine, destination, id, itinerary.results with day and port objects, length, lowestPricedSailing, portDeparture, sailings, ship, and title. Sailing records show departureDate, id, and priceId, and sailings has totalResults. These are unverified example fields, not a complete or guaranteed live schema. A priceId is a reference rather than a documented monetary amount, and a listed departure is not proof of current availability. The supplied evidence does not establish deck plans, cabin details, reservation actions, or a complete ship-profile response.

API Features

Paired ship reference lookup Use the required shipId and seoName together for a known cruise ship. The supplied contract points to cruise search or quick-link records as their source.
Day-by-day itinerary field preview The unverified documentation example contains itinerary.results entries with day and port objects inside data.itineraries.list.
Sailing identifiers without price assumptions Documented sailing examples include departureDate, id, and priceId, plus sailings.totalResults. These references do not establish fares or current bookable departures.
Cruise-line and destination context The example associates itinerary entries with cruiseLine, destination, portDeparture, ship, and title fields for a potential editorial content layout, subject to response verification.

Live API Demo

GET /api/project/tripadvisor-data/get-cruises-details

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/get-cruises-details?key=<API_KEY>&seoName=<seoName>&shipId=<shipId>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What values are required to request cruise details?

Both shipId and seoName are required strings. The documentation identifies cruise search and cruise quick-link records as sources for these values. currencyCode is optional and can be selected from currency lookup results.

Does seoName have to be a hyphenated URL slug?

The supplied documentation does not require slug normalization. Its example uses MSC Magnifica as seoName and 15691635 as shipId. Preserve the value associated with the selected ship reference rather than inventing a normalized form.

Which cruise response fields are documented?

A truncated, unverified example contains data.itineraries.list with cruise-line, destination, ship, departure-port, title, length, and itinerary fields. itinerary.results includes day and port objects; sailing records include departureDate, id, and priceId, with sailings.totalResults. This is not a verified complete schema.

Is priceId a fare, and do sailing records confirm availability?

No monetary fare is established by the documented priceId field; treat it as a reference. Likewise, a listed departure or a lowestPricedSailing object does not prove current inventory, a valid quote, or that a sailing can be booked.

Are deck plans, cabins, or the live response verified?

No saved live probe covers this endpoint, and the supplied documentation example is truncated. It does not establish deck plans or cabin details. Verify the actual returned structure before publishing a full ship profile; this GET lookup does not create a reservation.

Related operations

Guides

View Subscription Plans →