Pricing

Rating

Developer

Actor stats

Categories

Share

Airbnb Property Details Scraper

Turn Airbnb listing pages into a structured table — one row per property with amenities, capacity, pricing context, host display (name, Superhost flag, tenure), ratings, coordinates, images, and a completeness score. Export to CSV, JSON, or Excel for analysis, comps, or internal tools.

No company legal / B2B contact fields — this actor is listing intelligence only. For pro host emails, phones, and company details at scale, use Airbnb Professional Host Scraper. Custom integrations: corentin@outreacher.fr

No login. No API key. No Airbnb account needed.

Who is this for?

By default you get: URL, listing ID, title, room type, capacity, amenity flags, rating, GPS, host display, and price context — typically 25–33 fields per listing.

For B2B contacts (email, phone, company name, SIREN) from professional hosts, use the companion scraper linked above.

Quick start

1. Open the actor in Apify Console
2. Mode: choose City search
3. City name(s): enter Lyon, France (one per line)
4. Click Start — results appear in the Dataset tab within minutes

To scrape specific listings instead: switch Mode to Listing URLs, paste your /rooms/… links, and run.

What it extracts

The dataset has two table views: overview (key fields) and amenities breakdown — selectable in the Console Dataset tab.

Locales: Phase 2 detail fetches match the listing domain (.fr, .es, .de, .com). roomType is always in neutral English; raw propertyType and amenities stay in the page language.

Input parameters

Console fields

API-only fields (pass via JSON input)

These are not in the Console form but are accepted by the actor:

JSON example (API / bulk):

{
"mode":"city",
"city":["Amsterdam","Barcelona, Spain"],
"amenities":["Pool"],
"maxResults":200,
"maxPages":5
}

How it works

1. Phase 1 — Discovery: For each city, builds a search URL (Airbnb autocomplete → place_id), crawls search result pages with Cheerio (no browser needed), and collects all /rooms/… URLs.
2. Phase 2 — Extraction: Opens each listing page, parses the niobeClientData JSON block, extracts all fields, applies locale-aware normalization, and pushes one row per listing to the dataset.

Output sample

{
"listingId":"12345678",
"url":"https://www.airbnb.fr/rooms/12345678",
"title":"Charming apartment near the canal",
"propertyType":"Logement entier : appartement",
"roomType":"Entire place",
"guests":4,
"bedrooms":2,
"bathrooms":1,
"beds":2,
"pricePerNight":95,
"totalPrice":475,
"location":"Amsterdam, Netherlands",
"latitude":52.3676,
"longitude":4.9041,
"hostName":"Marie",
"hostType":"Superhost",
"hostSinceYears":5,
"rating":4.87,
"ratingCount":142,
"hasPool":false,
"hasWifi":true,
"amenities":["Wi-Fi","Cuisine","Machine à laver"],
"mainImage":"https://a0.muscache.com/im/pictures/…",
"completenessScore":82,
"extractedAt":"2026-06-29T16:00:00.000Z"
}

How much does it cost to scrape Airbnb listings?

This actor uses HTTP-only crawling (no browser) — compute is very cheap.

No residential proxies required for most cities. For heavily geo-restricted searches, enabling Apify datacenter proxies (included at no extra cost on paid plans) is sufficient.

Is scraping Airbnb legal?

This actor only accesses data that Airbnb makes publicly available on their website — the same pages any visitor can see without logging in. As with any data collection involving publicly visible information, ensure your use complies with Airbnb's Terms of Service and applicable regulations (GDPR, CCPA, etc.) for your specific use case.

Also available

Airbnb Professional Host Scraper — Extract B2B contact data (email, phone, company name, SIREN/VIES) from professional hosts. Same city-search engine, different output.

Airbnb Host Portfolio Scraper — Get all listing URLs from a host profile page. Combine with this actor's URL mode for full listing intelligence on a specific host.

Local development

npminstall
# Write input to the Apify local storage:
cp input-city-with-filters.json storage/key_value_stores/default/INPUT.json
# Or use --input-file:
apify run --input-file=./input-city-with-filters.json

storage/ is excluded from Docker via .apifyignore. When not on Apify cloud, the actor merges the repo-root input.json (if present) with Actor.getInput() — KV input wins on key collision.

Tests: npm run test:unit — pure input / URL builders, no network.

Changelog

See CHANGELOG.md.