Get cruise-line and ship quick-link reference data
View all Tripadvisor Hotel, Rental & Travel Data endpoints →Retrieve cruise quick-link reference data with a GET request and no endpoint-specific path, query, or body parameters. The supplied, truncated HTTP 200 source example shows a top-level data array of cruise-line records. Each visible line record contains a numeric locationId, name and seoName strings, and a ships array; visible ship records contain name and seoName strings plus a numeric shipId. These are documented example fields, not observed probe results: this operation has no saved probe call, and the snippet is incomplete, so the complete response envelope, field requiredness, and current catalog coverage remain unverified. No URL field is visible in the snippet; do not interpret seoName as a ready-to-open link. This is reference data, not sailing schedules, availability, fares, or a booking response.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/tripadvisor-data/get-cruises-quick-links No parameters required. Click Query to call the API.
API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/get-cruises-quick-links?key=<API_KEY>'
Query Result
Use Cases
- Prototype a cruise-line navigation module from returned names, adding navigation targets only when an actual destination URL has been independently verified.
- Build a line-to-ship reference selector that preserves the documented ships nesting instead of flattening vessels into an unlabeled list.
- Audit cruise-reference imports for repeated locationId or shipId values before using them as application keys.
- Review which cruise lines and vessels appear in a retrieved catalog for editorial coverage without presenting the list as bookable sailing inventory.
Frequently asked questions
Which inputs does the cruise quick-links request need?
None are declared for this operation: it is a GET request with no endpoint-specific path, query, or body parameters. Do not add an undocumented date, location, or pagination input.
What cruise-line and ship fields are documented?
The truncated source example shows data as an array of records with locationId, name, seoName, and ships. Each visible ship has name, seoName, and shipId. IDs are numeric in the snippet and names are strings; the full schema and field requiredness have not been verified.
Does a quick-link record include a URL I can open?
No URL field is visible in the supplied snippet. The seoName field is documented as text here, not as a complete navigation URL. Only expose a destination link after confirming its actual target; do not construct one by assuming seoName is a URL.
Has this quick-links response been observed in a saved probe?
No saved probe call is attached to this operation. The listed fields come only from an incomplete source example, so consumers should validate the complete response before depending on its shape or catalog coverage.
Can this endpoint confirm sailing availability or prices?
No such fields are documented in the supplied evidence. Treat this operation as a cruise-line and vessel reference list, not a sailing search, fare quote, reservation, or booking confirmation.