/airbnb/listings/availability

POST /api/airbnb/listings/availability

Price: 1 credit

Get an Airbnb listing's availability calendar by room id (or listing URL): for each day in the requested window — whether it is available, can be a check-in or check-out date, is bookable, and the minimum and maximum nights for a stay starting that day.

How to use it

Fetch an Airbnb listing's day-by-day availability calendar. Provide listing (numeric room id or /rooms/ URL), optional start_date (YYYY-MM-DD, defaults to today) and count (number of days). Returns one item per day with date, is_available, is_available_for_checkin, is_available_for_checkout, is_bookable, min_nights and max_nights. Per-night price is not part of this calendar.

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)
• start_date string nullable — First calendar day to return (YYYY-MM-DD). Defaults to today. (examples: "2026-07-01")
• count integer required — Number of consecutive days to return (min: 1; max: 366)

Response

• @type string (default: "AirbnbAvailabilityDay")
• date string required
• is_available boolean nullable
• is_available_for_checkin boolean nullable
• is_available_for_checkout boolean nullable
• is_bookable boolean nullable
• min_nights integer nullable
• max_nights integer nullable

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, or it exposes no availability calendar 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.