List cruise destination reference locations
View all Tripadvisor Hotel, Rental & Travel Data endpoints →Request the cruise-location reference list with a GET call and no endpoint-specific parameters. The supplied HTTP 200 source example contains a data array whose items have numeric destinationId and locationId fields and a name string. Its envelope also includes a boolean status, a message string, and a numeric timestamp; the example shows status true and message Success, but does not document the timestamp unit. Labels such as Caribbean and Bahamas illustrate the kind of destination reference returned, not guaranteed coverage. This operation has no saved probe call, so these are source-example fields rather than observed execution results, and field requiredness is unverified. Preserve destinationId and locationId separately; their interchangeability or use with other endpoints is not established. The list does not document sailings, departure ports, coordinates, fares, or booking availability.
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-location 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-location?key=<API_KEY>'
Query Result
Use Cases
- Populate a cruise-region chooser with returned name values after confirming the response shape, retaining both identifier fields behind each label.
- Maintain a dated, reviewed snapshot of cruise destination labels for travel-content editors without claiming sailing availability.
- Compare successive location-list snapshots to flag added, removed, or renamed destination references for manual catalog review.
- Export a cruise-region lookup table containing destinationId, locationId, and name while keeping it separate from port and departure databases.
Frequently asked questions
Can I search cruise locations by a typed destination name?
No destination-text parameter is declared for this operation. It retrieves a reference list with no endpoint-specific inputs. A client may inspect returned names, but a server-side text search is not documented here.
Which fields describe each cruise destination?
The source example places destination records in data. Each item has a numeric destinationId, a numeric locationId, and a name string. These fields are documented by the example only; they have not been observed in a saved probe for this operation.
Are destinationId and locationId interchangeable?
The example exposes them as separate fields and provides no rule equating them. Preserve each under its original name, and check the receiving endpoint contract before using either identifier in another request.
What do status, message, and timestamp mean in this list?
The source example has a boolean status set to true, a message string set to Success, and a numeric timestamp alongside data. It does not establish a timestamp unit or freshness guarantee. This is documented example behavior, not a saved probe result.
Does a listed region mean cruises are available there now?
No. The supplied evidence describes destination reference records only. It does not show departures, port coordinates, sailing dates, inventory, or fares, and the sample labels do not guarantee complete or current coverage.