Inspect Hotel Review Feature Metadata
View all Booking.com Hotel & Travel Data endpoints →Inspect the sparsely documented review-feature endpoint for hotel_id with optional language_code and currency_code. No live response or detailed feature schema was supplied for this route. Treat its output as exploratory review metadata until actual fields are validated; the operation name alone does not establish sentiment analysis, extracted themes, summaries, or any particular rating structure.
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/booking/get-hotel-review-feature API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/get-hotel-review-feature?key=<API_KEY>&hotel_id=180769'
Query Result
Use Cases
- Explore whether returned review metadata supports an internal overview panel.
- Record actual feature-field coverage before choosing a review data model.
- Compare exploratory feature responses across a small hotel test set.
- Reject unsupported sentiment claims during a travel-product integration review.
Frequently asked questions
Does this endpoint analyze review sentiment or extract themes?
That was not established. The documentation is sparse and no live response was validated. Name and expose only capabilities supported by the actual returned fields.
How should I model the response initially?
Keep it exploratory and associated with hotel_id until field types and semantics are inspected. Do not borrow the schema from review scores or review pages.