Airbnb Listings Scraper
Pricing
from $0.03 / 1,000 result extracteds
Scrape public Airbnb listings from search pages and room URLs with prices, ratings, review counts, amenities, images, and listing metadata.
Public HTTPS Airbnb search (/s/...) or room (/rooms/...) URLs. Provide these, a location, or resume work; they are combined when supplied together. Preserve filters in a search URL when you need an exact search.
Optional Airbnb location search, for example New York, NY. Used in addition to start URLs when provided.
Optional real YYYY-MM-DD date for generated location searches only. Supply checkOut too, later than checkIn. Does not modify explicit start or resume URLs.
Optional real YYYY-MM-DD date for generated location searches only. Supply checkIn too. Does not modify explicit start or resume URLs.
Maximum listing records saved across all inputs, from 1 to 10000. The form default is 20; API calls omitting this field use 25. This is a cap, not a guarantee of availability.
Optional three-letter currency code for generated location searches and output fallback, for example USD, EUR, or GBP. Does not change explicit URLs or convert prices. The form prefills USD; API omission leaves the fallback unset.
Number of adult guests for generated location searches.
Stop cleanly before the platform timeout and save unfinished source URLs for a later resume run.
Optional public Airbnb source URLs saved in PENDING_URLS by an earlier partial run. Use Resume state when it is available for an interrupted search page.
[]Optional advanced checkpoint from PENDING_WORK. It avoids replaying listing IDs already saved from an interrupted search-results page.
[]The form prefills useApifyProxy=false for direct requests. API/task omission preserves the SDK managed-proxy default; it is not the form prefill. Explicit useApifyProxy=false with no custom URLs opts out. Valid proxyUrls use your custom proxies; managed groups/country settings are passed through unchanged. Configured proxies are used from the first request, with no automatic direct-to-proxy fallback. Invalid or unsupported settings fail before proxy setup and extraction. Proxy service charges may apply separately; never share credentials in support reports.