Airbnb listings with prices for your dates and guests, by place, URL or listing id. One row per listing: nightly rate, stay total, rating, bedrooms, coordinates, Superhost, photos. Optional: 24-month availability calendar with occupancy, reviews. Free: amenities, house rules, host, price breakdown.
What users of other Airbnb scrapers complain about, done here.
A listing URL is priced for its own stay./rooms/<id>?check_in=…&check_out=…&adults=… is priced for those dates and guests, and its row and status row carry them (1.14 priced it undated for 2 adults and billed it). Explicit checkIn/checkOut still win, as for search URLs. A link with dates is billed only when Airbnb prices that stay; past or broken dates are dropped with a note on the status row and the row is free.
Other scrapers' limits and money-saving switches are read, never dropped. A switch that turns a part off wins over the count beside it: kaix's and memo23's includeReviews: false with maxReviewsPerListing (20 or 100) bills no reviews, cirkit's includeCalendar: false with calendarMonths: 6 bills no calendar (1.14 billed both). Also read: kaix's location, listings, minPrice/maxPrice, propertyType, maxSearchPages, maxLocationDeviation (a distance filter before billing) and reviewsSortBy; memo23's monitoringMode and fullCoverage; cirkit's months; onidivo's location, minPrice/maxPrice, maxReviews and extraData; lergassy's onlyAvailableListings (a listing without a free night is never billed); codepoetry's snake_case names; integrative_tangent's location and boundingBox. All listed under aliased_fields.
Cancellation policy and check-in times. Rows with details carry the cancellation policy Airbnb states for the stay (empty since Airbnb moved it out of the listing page's answer, about 2026-11-17), its refund steps (cancellation_milestones) and id, and check_in_time, check_out_time and check_in_out, read signed out from the listing's "Things to know": one more small request per detailed listing, free. If that read fails the row ships as before and the run says so.
min_nights on every dated row with calendarMonths, also when the check-in lies past the months asked (its month is read, free; 1.14 left it empty).
A listing id sent as a JSON number above 2^53 arrives rounded and may name another listing: it is no longer fetched, and its free rounded_id status row says to send ids as strings (1.14 reported it as not shown publicly). Ids as strings, /rooms/ URLs and whole numbers sent as floats work.
The run says what was left out. A search stopped by maxListingsPerQuery says "40 of the 226 listings Airbnb counts for Moulins, France: maxListingsPerQuery 40 stopped there", a search whose filters matched none in the pages read says how many it read and that maxListingsPerQuery: 10000 scans the whole area, on the run card, in SUMMARY left_out and on the status row (left_out, left_out_reason, note). The README's 3–4.3 rating example now uses the whole area.
README: "Questions users ask about other scrapers", answering the rivals' most repeated complaints with run ids and tests.
1.14 — 2026-11-18
Monitoring new listings: onlyNew with a monitorKey makes each scheduled run deliver and bill only listings that earlier runs of that monitor did not deliver. The first run delivers the current listings and remembers them; later runs deliver what is newly listed or newly matches. The memory is the key-value store airbnb-prices-calendar-seen in your account (record seen-<monitorKey>; without a key, one named after the input's searches, listing ids and hosts). Only delivered listings join it, and a listing id or host listing delivered before is not fetched again. Status rows count skipped listings in already_seen, SUMMARY in only_new. Without onlyNew nothing changes. The README's "Where other scrapers fail" table now cites the 1.13 platform runs.
1.13 — 2026-11-18
One currency and one price basis in every run. Every price is checked against currency: Airbnb answers a currency it does not offer (GEL) in USD, which 1.12 delivered labelled GEL and billed. Such an answer is now asked again from other IPs and otherwise delivered without amounts, with currency_mismatch naming Airbnb's currency, and not charged (SUMMARY currency_mismatch; the run card says so). Prices are always the stay total before taxes, as Airbnb shows US visitors: exits in the EU and UK get totals with taxes (Lisbon's tourist tax, about 8%), and 19 of 178 earlier runs on the default proxy mixed both bases. A total with taxes is now turned back into the total before taxes from its own price lines, with price_taxes and price_total_with_taxes beside it when Airbnb itemized them; nights and the base nightly rate are read from the first price line in every language. An empty first search page that Airbnb did not count as empty is asked again from other IPs before a search is reported as no_results. New: maxRating (with minRating, a rating range, applied before billing) and, with calendarMonths, min_nights and min_nights_typical on every listing row: the calendar is read before its listing row goes out, still once per listing, and for listing ids at the same time as the listing page. The README no longer says house rules carry check-in and checkout times: Airbnb stopped sending them to signed-out visitors.
1.12 — 2026-11-17
README only: the speed figures are now ranges measured over repeated runs (a 300-listing whole-area run of Lisbon took 15–55 s over 15 runs, depending on the proxy IPs a run gets). Code, inputs, outputs and prices are unchanged.
1.11 — 2026-11-17
Every listing of a host: hostIds (numeric ids or profile URLs, also accepted in startUrls) reads the host's public listing list, 100 per request, and prices each listing for your stay like listingIds, billed as a listing row, up to maxListingsPerQuery per host; with includeHostDetails the host row carries the whole list (host_listings) free. Free on every row with details: the registration or licence number (registration_number), safety and property disclosures (safety), co-hosts, whether children and infants are allowed, and the host's response rate, response time, languages and Airbnb-managed flag. Searches with maxItems deliver page by page, so the first rows land after the first page instead of at the end. Inputs written for other scrapers start a run as they are: tri_angle's locales es-419 and zh-TW-US, openclawai's host_listings mode with hostId, curious_coder's host profile URLs, automation-lab's maxListings: 0 (no limit: the whole area), and a saved search URL whose dates are past (searched without dates, with a note on its status row); agenscrape's own example window, already past, prices nothing. README examples use dates that are still ahead. Fixes from two failed runs: a listing Airbnb does not show publicly (private, unlisted or removed; Airbnb answers "Permission denied") is a free not_public status row, the run's other listings are delivered as usual, and a run of only such listings ends green as an input problem with nothing charged instead of failing. When the configured proxy refuses 3 requests in a row (proxy errors, 403, 429; for example a proxy country where Apify's datacenter pool has no IPs, such as PT, which answers every request 407), the rest of the run goes through Apify residential proxies of that country (US without one) instead of failing every listing with net:ProxyError; the run delivers and bills what it read and fails only when nothing could be read, then with a hint to check proxyConfiguration. A country search such as "India" is no longer mistaken for an unknown place because its listings are far apart. No prices changed.
1.10 — 2026-11-17
Two add-ons, off by default and gated on the run's pricing: until an add-on's price is in effect a run that asks for it skips it entirely, charges nothing for it and says so in SUMMARY (addons_inactive) and its status. nightlyPriceDays (from 2026-12-02, $0.0015 per priced night with Store discount tiers): for each delivered listing a night_price row for every bookable check-in date in the next N days (from checkIn), with the price Airbnb quotes for the shortest stay it allows from that date — Airbnb's calendar no longer carries a price per day. includeHostDetails (from 2026-12-02, $0.002 per host with Store discount tiers): one host row per host of the delivered listings from the host's public profile (Superhost, verified, location, languages, years hosting, rating, reviews, number of listings and a sample of them), each host once per run; it also fills the free listing details. Only a quote for exactly the stay asked for is billed; booked or blocked dates, unquoted dates and hosts without a profile cost nothing; the spending limit caps both exactly. agenscrape's enrichWithPricing and tri_angle's enrichUserProfiles are read as these fields. The host-profile query is refreshed like the others when Airbnb rotates its hash. Inputs without the new fields run exactly as in 1.9. No existing price changed.
1.9 — 2026-11-17
Whole-area coverage: maxListingsPerQuery now goes up to 10,000. Up to 280 a search is one Airbnb search, as before; above 280 the run covers the whole area: it reads Airbnb's own count, splits the search into price bands along Airbnb's price slider (halving any band that still counts more than 270, then splitting by room type, and a map area into quadrants) until every slice is one Airbnb answers in full, reads the slices in parallel and delivers each listing once, in price-band order (each band sorted with sortBy). Rows bill on the existing listing event; maxItems and the spending limit cap the run exactly; calendars and reviews follow every delivered listing. Status rows now carry result_count (Airbnb's own count for the search), whole-area ones also slices, splits, truncated and slice_errors, and SUMMARY a coverage list. Inputs from automation-lab (maxListings) and openclawai (maxResults with its own fields), which split big searches themselves, get whole-area coverage up to their total; limitPerUrl (curious_coder) goes up to 10,000. maxItems alone still lifts the per-search default to 280 only, so runs without the new values behave as before. No prices changed.
1.8 — 2026-11-17
New filters that Airbnb itself applies, off by default: amenities (names such as "pool" or Airbnb ids; a listing must have all of them), propertyTypes (house, apartment, guesthouse, hotel), freeCancellation, instantBook, guestFavorite and a map area (swLat, swLng, neLat, neLng; alone it is a search of its own). They apply to place searches and override a pasted search URL's own value. Pasted search URLs now keep every filter of the site's panel (Instant Book, free cancellation, Guest favorite, property types, Luxe, host language, tags), which were dropped before. Weekday dates: checkIn "friday", "next saturday" or "weekend"; checkOut "sunday", "weekend" or "3 nights", counted from the check-in. Inputs written for other Airbnb scrapers (tri_angle, curious_coder, automation-lab, openclawai, agenscrape) run as they are: their field names are read as ours when ours is absent (SUMMARY aliased_fields), startUrls take {"url": …} objects, and every other unknown field is listed in SUMMARY ignored_fields and the status message instead of being dropped silently. Prices and minBathrooms take decimals, the currency lower case. Fixes: hotel cards no longer report the hotel's name as property_type (now "Hotel", with its area); titles in other languages ("Loft ⋅ Lisbonne", "Loft em Lisboa") are split into type and area; price_nightly above 1,000 keeps its thousands ("$1,137.72" was read as 1.137). When Airbnb retires or renames a query, the run now fails with a message naming it and the similar queries the site registers now, after delivering and billing every row that did not depend on it, instead of succeeding without calendars as on 2026-11-12..14; the reviews query, which the site loads on demand, is now refreshed like the others. The input form shows minRating, superhostOnly, sortBy, amenities and freeCancellation among its first 20 fields. Runs without the new fields are unchanged apart from these fixes. No prices changed.
1.7 — 2026-11-16
A search page that fails after earlier pages were read no longer loses those rows: with maxItems, a filter or a sort, the rows already read are delivered and charged once, and the search's status row reports the failure. A page refused by the run-timeout guard keeps its rows the same way, without an error. Results without failures, output fields, defaults and billing are unchanged. No prices changed.
1.6 — 2026-11-16
Never billed past maxTotalChargeUsd: each charge asks the platform only for the listings, calendar months and reviews that still fit under the spending limit, under one lock shared by every concurrent search and add-on, and exactly those are delivered; the run then ends — spending limit reached. Apify SDK 4.2 answers a request for more events than still fit by billing one event past the limit (a $0.30 limit was billed $0.302 on google-hotels-prices on 2026-11-16), and a limit below the price of one listing was billed one listing. A listing still delivered when its add-ons do not all fit keeps the calendar months and reviews that do. Runs without a spending limit, or whose limit is not reached, are unchanged: no prices, input fields, defaults or output fields changed.
1.5 — 2026-11-16
New inputs at the end of the form, whose defaults change nothing: minRating and superhostOnly filter listings before billing, so a filtered-out listing is never charged and the run reads further pages (at most 3x) to fill your count. Superhost uses Airbnb's own filter, then each host is checked on its listing page, because search cards often show Guest favorite instead of the Superhost badge. sortBy = relevance (default) / price_low_to_high / price_high_to_low: Airbnb has no price sort, so a sorted search reads up to 3x the listings asked for (at most 280), sorts them by stay total and delivers and charges the top ones in order. maxItems now gives every place, search URL and listing id an equal first share before any gets more (a 10-city call no longer spends it all on the first cities), and rows read but not yet delivered wait for the next turn instead of being read again. Near the run timeout the run starts no new page, listing or add-on and ends green with SUMMARY written. Client: a query-hash rotation mid-run is refreshed once for every request in flight, and throttled answers (429/403/5xx) back off before the next IP. No prices, output fields or defaults changed.
1.4 — 2026-11-16
maxItems (sent by AI agents) now caps the primary rows delivered and charged; add-ons follow the delivered rows. The primary row is the listing: maxItems is one total of listing rows across all places, search URLs and listing ids, and each search page asks for its listings before it is fetched, so a run stops fetching the moment the cap is reached. Calendars and reviews still come with every delivered listing, billed as before. With maxListingsPerQuery left at its default (40), maxItems also lifts it (up to 280 per search) so the run can deliver up to maxItems listings; an explicit maxListingsPerQuery is the stricter cap and wins. A search or listing id the cap never reached is not fetched and gets no status row (SUMMARY counts it as max_items_skipped). Without maxItems nothing changes. No prices, output fields, defaults or input fields changed.
2026-11-14 — 1.3 Restore calendars after Airbnb query retirement
Read availability calendars through Airbnb's new listing-node calendar query after the old calendar query was retired (HTTP 400). Preserve output fields, defaults and event prices.
2026-11-13 — Restore previous listing keywords
Restore title, description and SEO text to the November 5 baseline at the owner’s request. Preserve current runtime fixes, input/output contracts, billing, prices and defaults.
2026-11-12 — Restore Airbnb search after query rotation
Update the public search and listing query identifiers. Recognize Airbnb’s HTTP 400 deprecated-operation response and refresh once, rebuilding both the URL and request extensions before retrying. Read listing details from Airbnb’s new listing-node response as well as legacy sections. Preserve output fields and prices.
2026-11-07 — Agent result-contract clarification
Clarify result ordering, row relationships, cost limits and interpretation of the existing outputs for agents. Input descriptions and README only; field names/defaults, ranking metadata and event prices are unchanged.
2026-11-07 — Search URL stay and guest context
Fix Airbnb search URL results and optional detail requests to use the same effective dates and guest counts as the search. Global checkIn/checkOut still override URL dates; URL guest filters/defaults retain their existing precedence. Unpriced dated-URL results follow the existing free-unpriced-row rule. Preserve once-per-listing-per-run deduplication, input defaults, output fields and event prices.
2026-11-06 — MCP discovery metadata
Clarify supported search intents and output nouns in the Store listing. Runtime, input contract, output and prices are unchanged.
Changelog
2026-10-16 — Keyword Planner and locale documentation
Validated search terminology against Google Ads Keyword Planner and Store shelves. Added localized usage guidance and bounded examples; retained existing English phrases. Clarified locale limitations where measured. No runtime, output fields, defaults, or pricing changed.
1.2 — listing: blind-test fixes, 2026-10-12
No behaviour, output or price changed. Six Sonnet testers read the card and the input form for six real requests: 6 of 6 picked this actor and 6 of 6 wrote a valid first call. What they guessed at is now written down: the listing row keys (price_total, price_nightly, price_nightly_effective, price_breakdown, rating, is_superhost, url) in the form and the event text, that listings come in Airbnb's relevance order (for "the N cheapest" use priceMax or sort price_total), that the calendar carries availability only and no price per day, that relative dates count from the run day (weekday stays: a weekly schedule with multiples of 7), more currency examples (MXN, CHF, SGD, INR, THB), and that proxy and compute are included in the event price. Feature gaps the testers named, for a later release: Superhost and minimum-rating filters, a price sort.
1.2 — listing and input form reworded, 2026-10-11
No behaviour, output or price changed; the same inputs return the same rows.
Title: "Listings" added; "Prices, Availability Calendar" kept as one phrase (it ranks first for that phrase); "Occupancy" moved from the title into the description — the Airbnb Occupancy Rate Scraper is the answer to occupancy requests and holds those ranks.
Description now says what one row is (nightly rate, stay total, rating, bedrooms, coordinates, Superhost, photos), names the optional rows (24-month availability calendar with occupancy, reviews) and the free extras (amenities, house rules, host, price breakdown).
The input form is reordered: what to price, the stay and guests, how many listings and which rows (includeDetails, calendarMonths, maxReviewsPerListing, reviewsSort — the last two were below the fold), then filters. minBeds, minBathrooms, proxy and pacing moved lower; nothing was renamed or removed.
Every input now says what to pass, with an example, its default, what it changes and what it costs.checkIn says that without dates every listing row is billed at its displayed price; maxListingsPerQuery says filters apply before the cap; includeDetails lists what it adds and that it is free; calendarMonths says blocked and booked nights look the same; maxReviewsPerListing points to the Airbnb Reviews Scraper for rating filters and more than 200 reviews.
The pricing text lists what is never charged, that there is no start fee, and that a run stops at the maximum cost you set.
README: a section mapping common requests to the exact input and the status contract. seoDescription carries vacation rental, short term rental data and the Spanish, German, French, Portuguese and Italian words for prices.
1.2 — 2026-10-05
Fix: listings whose price Airbnb sends in its new format came back without a price. Airbnb now uses that format for every hotel and, in some cities, for ordinary rentals too — a few results per hundred in Lisbon, around half in Paris and Barcelona, most in New York and Tokyo. The actor read it as "no price", so those listing rows were delivered with price_total: null and were not billed. They now carry the same price fields as every other listing (price_total, price_original, price_nightly, price_nights, the breakdown), from a search and from listingIds / includeDetails alike. For a hotel this is Airbnb's "from" price for the stay: its cheapest room type. Billing is unchanged: one listing charge per row that carries a price.
2026-08-30
Reliability: a run that cannot act on its input — a URL from the wrong site, a name nothing resolves to, an empty target list, a number outside the documented range — now ends cleanly with the reason on the run card instead of as a failed run. Nothing is charged in either case; a blocked or throttled source still fails loudly.
Store listing: moved into the categories buyers actually browse (the old Business category has no Store page).
1.1 — 2026-08-26
Dataset consistency and billing fixes.
One listing shape for the whole dataset. Rows produced from listingIds omitted every field Airbnb had not answered, while rows from locationQueries carried the full column set — so a mixed run exported ragged CSVs with columns appearing and disappearing. Every listing row now carries the same columns, with null where there is no value. available, cancellation_policy and unavailable_message now appear on all listing rows as documented.
Calendars bill for exactly the months delivered. When a run's spending limit was reached part-way through a calendar, the full 12- or 24-month row was still delivered against a partial charge. The row is now trimmed to the months actually billed and its occupancy summary recomputed for them.
A failed calendar or review no longer marks a listing job failed. For listingIds inputs an add-on error flipped the job's status to error even though the listing row had been delivered and billed. Add-on failures are now counted in calendar_errors/review_errors on both paths, as they already were for searches.
A malformed listing id now says so. It previously reported "give at least one place…", hiding which id was wrong.
Bad input fails the run cleanly instead of crashing it. Non-numeric adults, calendarMonths, maxListingsPerQuery, maxReviewsPerListing, sessions or perIp raised an unhandled error mid-run; out-of-range values were accepted silently. All numeric inputs are now checked against the ranges this page documents, reviewsSort and roomTypes must be listed values, locale must be a real code, and priceMax must be at least priceMin.
maxListingsPerQuery: 0 was silently treated as 40 and billed for 40 listings. Values outside 1–280 are now rejected before anything is fetched.
1.0 — 2026-08-26
First public release.
Airbnb prices for your dates and guests in any currency and language: search any place, paste Airbnb search or listing URLs, or give listing ids.
listing rows: total for the stay, base nightly rate and effective per-night price, discounts, rating and review count, bedrooms/beds/baths, coordinates, badges (Guest favorite, Superhost), free cancellation, pictures — paged up to Airbnb's ~280-result cap per search.
calendar rows: up to 24 months of day-by-day availability per listing with occupancy for the next 30/90/365 nights, next available date and typical minimum stay.
Listing details on request: description, amenities, house rules, cancellation policy, category ratings, host, capacity, sleeping arrangement and the exact price breakdown for the dates (including "not available" for the dates).
Reviews: newest, highest, lowest or most relevant first, with reviewer, date and host reply.
Honest billing: pay per listing row that carries a price, per calendar month and per review; unknown places (Airbnb would otherwise return listings from all over the world), empty searches and status rows cost nothing; each listing and stay is billed once per run.
No login, no cookies: the same public API the airbnb.com front-end uses, with automatic refresh of Airbnb's query hashes when they change.
Relative dates for schedules; Console views for listings, calendar, reviews and run status.