Airbnb Scraper — Listings, Prices, Ratings, Hosts

Scrape Airbnb stays by location (city, region, or address) with optional date and guest filters. Returns 26 structured fields per listing including price/night, total stay price, room type, bed/bedroom info, rating, review count, superhost status, host name, GPS coordinates, amenities, and image URLs.

Features

• Search by any location — city name, address, or region (e.g. "Paris, France", "New York, NY")
• Optional date filtering — pass checkIn/checkOut to get actual stay prices
• Guest count — filter by number of adults
• Price range — priceMin / priceMax per night in USD
• Full host info — host name + Superhost / Guest Favorite badges
• Amenities — list of available amenities per listing (Wifi, Kitchen, AC, etc.)
• GPS coordinates — latitude/longitude for every listing
• 26 fields per listing — pay only for what you get (PPE pricing)

Use Cases

• Short-term rental market research — compare prices, ratings, and amenity offerings across neighborhoods
• Investment property analysis — find average nightly rates and occupancy signals
• Lead generation — identify superhosts and top-rated properties for partnership outreach
• Travel planning tools — build apps that surface the best stays for any destination
• Competitive intelligence — monitor pricing and availability trends

Input

Field	Type	Description
location	string	Required. City, region, or address (e.g. "Paris, France")
checkIn	string	Check-in date YYYY-MM-DD (optional, for actual stay prices)
checkOut	string	Check-out date YYYY-MM-DD (optional)
adults	integer	Number of adult guests (default: 1)
priceMin	integer	Minimum price per night in USD
priceMax	integer	Maximum price per night in USD
maxItems	integer	Max listings to return (default: 100; 0 = all available)
enrichDetails	boolean	Fetch detail page for host name + amenities (default: true)
proxyConfiguration	object	Proxy settings (Apify Residential recommended)

Output

Each record contains:

{
  "listing_id": "1536119775792438782",
  "url": "https://www.airbnb.com/rooms/1536119775792438782",
  "title": "Apartment in Paris",
  "name": "Balcony Eiffel Tower View : Newly Refurbished Apt",
  "room_type": "Entire home/apt",
  "price_per_night": 534.63,
  "price_total": 2674.0,
  "price_original": null,
  "stay_nights": 5,
  "currency": "USD",
  "rating": 4.97,
  "review_count": 39,
  "is_superhost": true,
  "is_guest_favorite": true,
  "host_name": "Toni",
  "host_id": "540951866",
  "bedrooms": "1 bedroom",
  "beds": "2 beds",
  "bathrooms": "1 bath",
  "person_capacity": 4,
  "latitude": 48.84328,
  "longitude": 2.29114,
  "amenities": ["Kitchen", "Wifi", "TV", "Elevator", "Washer", "Dryer"],
  "images": ["https://a0.muscache.com/..."],
  "search_location": "Paris, France",
  "scraped_at": "2026-06-05T10:23:00+00:00"
}

Pricing

Pay-per-result: $1.90 per 1,000 listings (charged after successful push, never on failure).

Notes

• Airbnb caps search results at approximately 270–300 listings per location search.
• For broader coverage search by neighborhood or use date ranges to vary results.
• enrichDetails: false skips detail-page fetches (faster, no host_name/amenities).
• The actor uses Airbnb's internal GraphQL API — no fragile HTML scraping.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Agoda Scraper
• Opentable Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.