Get one hotel’s photos and amenity collections
View all Tripadvisor Hotel, Rental & Travel Data endpoints →Retrieve hotel content for a required hotel id and stay dates checkIn and checkOut in YYYY-MM-DD format. Obtain the hotel identifier through hotel search and verify the selected result identifier before passing it as id. Optional adults, rooms, childrenAges and currency keep the request aligned with the intended party and stay. The documented childrenAges input is an array of ages from 0 to 17, using 0 for a child under one year. A saved successful HTTP 200 probe returned a JSON object with status=true, a message string, an integer timestamp and a data object containing photos and amenitiesScreen arrays. The probe metadata establishes these collections, not their item-level schemas or completeness. A separate, truncated documentation example also shows data.about with title, tags and content, amenitiesScreen sections with title and content, and data.attractionsNearby.content; those additional fields were not confirmed by the supplied probe metadata. Handle empty or absent collections explicitly rather than treating missing content as proof that an amenity is unavailable. This is a content lookup, not a booking confirmation or a guarantee of room inventory, prices, reviews or complete property coverage.
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-hotel-details API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/get-hotel-details?key=<API_KEY>&checkIn=<checkIn>&checkOut=<checkOut>&id=<id>'
Query Result
Use Cases
- Enrich a deliberately chosen hotel shortlist with photo collections, inspecting each photo item before rendering it.
- Add an amenity-content panel to a selected property page without presenting an incomplete collection as an exhaustive facility list.
- Audit hotel-content coverage by recording populated, empty and absent photos or amenitiesScreen collections separately from request failures.
- Attach property content to a saved trip selection while preserving that selection’s dates, party, rooms and currency context.
Frequently asked questions
Which identifiers and dates do I need for a hotel-content request?
The required inputs are id, checkIn and checkOut. The dates use YYYY-MM-DD. The documentation directs you to hotel search for the hotel identifier; verify the selected search result identifier before sending it as id.
Which hotel detail fields were actually observed?
The saved successful probe returned status=true, a message string, an integer timestamp and a data object with photos and amenitiesScreen arrays. Their item-level fields were not established by the supplied probe metadata.
How do I describe children and the rest of the travel party?
Optional adults is the number of guests aged 18 or over, and rooms is the requested room count. childrenAges is an array of ages from 0 to 17; the documented example [0,10] represents a child under one year and a ten-year-old. No default party size is documented.
Can I rely on about and nearby-attraction fields in every detail response?
No. A truncated documentation example includes data.about and data.attractionsNearby.content, but the supplied probe metadata did not confirm these fields. Treat them as optional, unverified example content until you inspect actual responses.
Does an empty amenity collection mean the hotel lacks those facilities?
No. Empty or absent content establishes only what was returned for that request. It is not evidence that a facility is absent, nor does this content lookup confirm room availability or a booking.