Airbnb experiences search

GET https://api.api.sh/airbnb/v1/experiences
1 credit / call travel & events try it in the playground →

Airbnb Experiences in a place, 20 a page: title, summary, category, rating and review count, price per guest (with the struck-through original price), duration, ticketed or not, badges, booking messages, photos and link. Filter by dates, guests, price, duration, experience type, featured tags, who it suits, time of day, language and accessibility; filters lists every option with the value to pass back.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
locationrequired string A city or place, e.g. Paris, France. Example: Paris, France
checkin string From date, YYYY-MM-DD.
checkout string To date, YYYY-MM-DD (default: checkin).
adults integer Adults.
children integer Children.
infants integer Infants.
min_price integer Minimum price per guest.
max_price integer Maximum price per guest.
min_duration integer Minimum duration (as the site's duration filter takes it).
max_duration integer Maximum duration.
tags string Experience types, comma separated (value of the taxonomy options, e.g. Tag:9010 for architecture).
featured string Featured tags, comma separated (values from the experience_featured options).
traveler_types string Good for (values from the experience_traveler_type options, e.g. kids, big groups).
time_of_day string morning, afternoon or evening, comma separated.
languages string Language ids, comma separated (values from the host_language options, e.g. 1 for English).
accessibility string Accessibility tags, comma separated (values from the accessibility options).
tickets string Ticketed experiences only (the value from the experience_tickets_filter option).
cursor string next_cursor from the previous page.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/airbnb/v1/experiences?location=Paris%2C+France" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.