/airbnb/listings/search

POST /api/airbnb/listings/search

Price: 1 credit

Search Airbnb stay listings by location with optional dates, guest counts and nightly-price filters. Returns listings with id, url, listing title, card category, coordinates, overall rating and review count, guest-favorite flag, badges, displayed price (with original price when discounted) and its qualifier, capacity (bedrooms, beds, bathrooms) and photos.

How to use it

Search Airbnb homes by free-text place (city, region, address or landmark). Optional check_in/check_out (YYYY-MM-DD), adults/children/infants/pets and min_price/max_price filters. Returns up to count listings, each with id, url, title (listing name), category (card heading like 'Condo in Rome'), latitude, longitude, rating, review_count, is_guest_favorite, badges, price, original_price, price_qualifier, bedroom_count, bed_count, bathroom_count, bathroom_label and images. Use airbnb/listings (by id) for full listing detail.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• place string required — Location to search (city, region, address or landmark) (examples: "Paris, France"; minLength: 1)
• count integer required — Max number of listings to return (min: 1)
• check_in string nullable — Check-in date (YYYY-MM-DD) (examples: "2026-08-09")
• check_out string nullable — Check-out date (YYYY-MM-DD) (examples: "2026-08-14")
• adults integer — Number of adult guests (default: 1; min: 1; max: 16)
• children integer — Number of children (default: 0; min: 0; max: 15)
• infants integer — Number of infants (default: 0; min: 0; max: 5)
• pets integer — Number of pets (default: 0; min: 0; max: 5)
• min_price integer nullable — Minimum nightly price filter (min: 0)
• max_price integer nullable — Maximum nightly price filter (min: 0)

Response

• @type string (default: "AirbnbSearchListing")
• id string required
• url string nullable
• category string nullable
• latitude number nullable
• longitude number nullable
• rating number nullable
• review_count integer nullable
• is_guest_favorite boolean nullable
• badges array (default: [])
• price string nullable
• original_price string nullable
• price_qualifier string nullable
• bedroom_count integer nullable
• bed_count integer nullable
• bathroom_count number nullable
• bathroom_label string nullable
• images array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.