Airbnb Experiences Search API

Use placeId exactly as returned by common-auto-complete. Optional fromDate and toDate use future YYYY-MM-DD dates; guests, currencyCode, languageCode, activityType, languageOffered, priceRange, timeOfDay and map bounds refine discovery. The live Paris body returned status:true, message, pagination meta and data with filters, paginationInfo and searchResults. Observed activity records included id, title, coordinates, host information, photos and ratings; their shape differed from stay search cards. Follow nextPageCursor through pageCursor. Filter IDs should come from this experience response, not the separate query-based property filter catalog.

API Features

Destination-linked activity discovery The same observed autocomplete placeId was accepted for Paris experience search.

Experience-specific result cards Live activity results exposed their own IDs, titles, photos, location and rating information.

Activity language and time filters Documented languageOffered and timeOfDay inputs describe the activity rather than response-localization settings.

Experience cursor continuation Use returned paginationInfo cursors for further activity results instead of inventing a page input.

Live API Demo

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

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/airbnb-search/experiences-search?key=<API_KEY>&placeId=eyJwIjoiQ2hJSkQ3ZmlCaDl1NWtjUllKU01hTU9DQ3dRIiwicSI6IlBhcmlzLCBGcmFuY2UifQ%3D%3D&adults=2&currencyCode=USD&languageCode=en-US&limit=3'

curl -X GET 'https://api.opendata-api.com/api/project/airbnb-search/experiences-search?key=<API_KEY>&placeId=eyJwIjoiQ2hJSkQ3ZmlCaDl1NWtjUllKU01hTU9DQ3dRIiwicSI6IlBhcmlzLCBGcmFuY2UifQ%3D%3D&adults=2&currencyCode=USD&languageCode=en-US&limit=3'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Build a destination itinerary shortlist that combines nearby activities with accommodation research.
Find tours offered in a traveler's preferred language while keeping the response language independently configured.
Compare local activities within a map rectangle using returned display prices and review ratings.
Offer activity-type and time-of-day refinements from the experience search's own returned filters.

Frequently asked questions

Can I use property amenity or category IDs as experience filters?

Use the filters returned by experiences-search for activityType, accessibilityFeatures, languageOffered and timeOfDay. Property filter catalogs belong to a different endpoint family and should not be treated as interchangeable.

Are experience search records shaped like stays-search listings?

No. The live experience results used activity records with their own id and content fields, while stays-search included listing.id and structuredDisplayPrice stay cards. Inspect the actual experience item and reuse its activity ID for downstream experience endpoints.

Related operations

Guides

View Subscription Plans →

Search Airbnb Experiences Around a Destination