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

Activity-scoped guest feedback Request the documented review collection for one experience rather than an accommodation listing.
Experience review page sizing Use page and limit to retrieve activity feedback in manageable batches.
Highlighted comment handling Documented comments can contain mark tags, so render safely or normalize markup before analysis.
Keyword-focused activity reviews The optional query input supports documented text-focused review retrieval without implying a sort control.

Live API Demo

GET /api/project/airbnb-search/experiences-reviews

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/airbnb-search/experiences-reviews?key=<API_KEY>&listingId=<listingId>&currencyCode=USD&languageCode=en-US&page=1'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →