Read and Search Reviews for an Airbnb Experience
View all Airbnb Search, Prices & Reviews endpoints →Pass the selected experience listingId with optional page, limit, query, currencyCode and languageCode. The documented defaults are page 1 and limit 20. The documented response places reviews in a data array with id, comments, createdAt, language, localizedDate and rating; comments can contain highlighted markup for a keyword match. No sortBy parameter is documented here. This experience-review endpoint was not included in the live verification set, and keyword behavior should be confirmed for the chosen activity and query.
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/airbnb-search/experiences-reviews API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/airbnb-search/experiences-reviews?key=<API_KEY>&listingId=<listingId>¤cyCode=USD&languageCode=en-US&page=1'
Query Result
Use Cases
- Research whether a selected activity suits children using documented review keyword searches.
- Compare recurring feedback about meeting-point clarity across shortlisted tours.
- Analyze guide communication themes in paginated activity reviews while retaining review dates.
- Normalize highlighted experience comments to plain text before storing a review research extract.
Frequently asked questions
Does experiences-reviews accept MOST_RECENT or rating sorting?
No sortBy input is documented for this endpoint. It supports listingId, page, limit and optional query with currencyCode and languageCode; do not copy stay-review sorting parameters into this request.
Can review comments include HTML-like markup?
The documented example includes mark tags around keyword matches. Treat comment content as untrusted text: safely escape it or remove markup for analysis rather than injecting it directly into a page. Current behavior still needs endpoint-specific verification.