/airbnb/listings

POST /api/airbnb/listings

Price: 5 credits

Get full Airbnb listing details by room id (or listing URL): title, property and room type, location with coordinates, capacity (guests, bedrooms, beds, bathrooms), overall and category ratings, review count, guest-favorite and superhost flags, description, highlights, full amenity list, photos, cancellation policy, check-in/checkout times, house rules and the host (name, photo, tenure, rating, reviews, verification, response rate, co-hosts).

How to use it

Fetch a single Airbnb listing by numeric room id or a /rooms/ URL. Returns one item with id, url, title, property_type, room_type, location, latitude, longitude, person_capacity, bedroom_count, bed_count, bathroom_count, bathroom_label, rating, review_count, rating_accuracy, rating_checkin, rating_cleanliness, rating_communication, rating_location, rating_value, is_guest_favorite, is_superhost, description, highlights (title, subtitle), amenities (name, category, available), images, cancellation_policy, check_in_time, check_out_time, house_rules and host (id, name, image, is_superhost, is_verified, rating, review_count, years_hosting, about, response_rate, response_time, cohosts).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• listing string required — Airbnb listing (room) id or a listing URL containing it (examples: "1316083847530954363", "https://www.airbnb.com/rooms/1316083847530954363"; minLength: 1)

Response

• @type string (default: "AirbnbListing")
• id string required
• url string nullable
• property_type string nullable
• room_type string nullable
• location string nullable
• latitude number nullable
• longitude number nullable
• person_capacity integer nullable
• bedroom_count integer nullable
• bed_count integer nullable
• bathroom_count number nullable
• bathroom_label string nullable
• rating number nullable
• review_count integer nullable
• rating_accuracy number nullable
• rating_checkin number nullable
• rating_cleanliness number nullable
• rating_communication number nullable
• rating_location number nullable
• rating_value number nullable
• is_guest_favorite boolean nullable
• is_superhost boolean nullable
• description string nullable
• highlights array (default: [])
  • @type string (default: "AirbnbHighlight")
  • subtitle string nullable
• amenities array (default: [])
  • @type string (default: "AirbnbAmenity")
  • name string required
  • category string nullable
  • available boolean nullable
• images array (default: [])
• cancellation_policy string nullable
• check_in_time string nullable
• check_out_time string nullable
• house_rules array (default: [])
• host object nullable
  • @type string (default: "AirbnbHost")
  • id string nullable
  • name string nullable
  • image string nullable
  • is_superhost boolean nullable
  • is_verified boolean nullable
  • rating number nullable
  • review_count integer nullable
  • years_hosting integer nullable
  • about string nullable
  • response_rate string nullable
  • response_time string nullable
  • cohosts 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 — Listing not found, unlisted or removed (well-formed but nonexistent/withdrawn room id) 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.