Airbnb Listings Scraper: prices, ratings and coordinates from Airbnb search

Name a city or a destination, optionally give your dates and a guest count, and get the listings back as rows: the listing id, the name, the property type, the star rating, the review count, the price Airbnb showed, the map coordinates and up to five photos.

This reads Airbnb's public search results, so it gives you a sample of a destination rather than its whole inventory. Twenty listings per location, five locations per run, and no paging past that.

🔍 What Airbnb Listings Scraper does

Each location string goes into Airbnb's own stays search the way you would type it:

Toronto, Ontario, Canada

Give it both dates and the prices come back for your actual stay. Give it neither and you get Airbnb's default view. One date on its own is rejected before any request goes out, because a half-specified search silently returns something else.

Every row carries the search that found it: searchLocation, checkIn, checkOut and adults, so a multi-city run stays joinable back to your own list.

There is a wall-clock budget on the whole run. When it runs out, the locations still waiting get a DEADLINE row rather than being dropped in silence.

📥 What you give it

{
  "locations": ["Toronto, Ontario, Canada", "Montreal, Quebec, Canada"],
  "checkIn": "2026-11-10",
  "checkOut": "2026-11-14",
  "adults": 2,
  "maxItemsPerLocation": 20
}

Give it both dates or neither. One on its own stops the run with a single BAD_INPUT row, and no locations are searched.

A location string that is empty or longer than 160 characters stops the whole run, not just that one entry. Check the list before a long batch.

📤 What you get back

A real row from a recent run, with the photo list cut short here for length:

{
  "ok": true,
  "recordType": "listing",
  "listingId": "14822179",
  "name": "Luxury 1BR- Exclusive Maple Leaf Square condo",
  "propertyType": "Condo in Toronto",
  "rating": 4.98,
  "reviewCount": 169,
  "price": "$1,069",
  "priceAmount": 1069,
  "currency": null,
  "priceQualifier": "for 5 nights",
  "priceAccessibilityLabel": "$1,069 for 5 nights, originally $1,211",
  "badges": ["Guest favorite"],
  "spaceDetails": ["1 bedroom", "2 beds", "1 bath"],
  "latitude": 43.64361,
  "longitude": -79.38011,
  "photoUrls": ["https://a0.muscache.com/im/pictures/hosting/Hosting-14822179/original/...", "..."],
  "listingUrl": "https://www.airbnb.com/rooms/14822179",
  "searchLocation": "Toronto, Ontario, Canada",
  "checkIn": "2026-08-10",
  "checkOut": "2026-08-12",
  "adults": 2,
  "source": "airbnb_public_search_html",
  "transport": "direct"
}

🧾 Reading the output

Three kinds of row can land in your dataset.

Filter on _sample being absent, not on recordType. The free sample row also carries recordType: "listing". Note the diagnostic field is code, not errorCode.

One failed location does not stop the others, and a diagnostic row never fails the run.

▶️ How to run it

1. Open Airbnb Listings Scraper and click Try for free.
2. Type your destinations into Locations, one per line, up to five.
3. Fill in Check-in date and Check-out date together if you want prices for real dates.
4. Set Adults, then click Start.
5. Download the dataset as JSON, CSV or Excel, or read it from the Apify API.

💰 How much does it cost?

$0.40 per 1,000 listings. Flat on every Apify plan, no volume tiers.

You pay per listing row delivered. The sample row, diagnostic rows and listings already seen in the same run are all free, and a run that returns no listings is not charged.

💡 What people use it for

• Checking what a city is charging for your dates before setting your own price.
• Sampling several neighbourhoods or nearby towns in one run and comparing the rating spread.
• Pulling coordinates and ratings for a map of where the well-reviewed stays cluster.
• Watching a destination on a schedule, with the same dates each time, to see the price move.
• Giving a model a small clean table of real listings instead of a page of search HTML.

🚧 What it does not do

• No host details. Host name, superhost status and response rate are not on the search cards and are not in these rows.
• No amenities, no availability calendar, no house rules, no per-listing reviews.
• No paging. Twenty per location is the ceiling, so this is a sample of a destination, not its inventory.
• Five locations per run. Anything after the fifth is dropped without a warning.
• priceAmount is not always a nightly rate. It is whatever number leads the card text, and priceQualifier says what that covers.
• Prices are the card's display value, before Airbnb's checkout adds fees and taxes.
• Coordinates are approximate. Airbnb fuzzes the pin until a stay is booked.
• Past dates are accepted and sent as given, which returns whatever Airbnb makes of them.
• Rows are a snapshot, and Airbnb search results move constantly.

🧭 Which stay scraper do you need?

❓ Questions people ask

Do I need an Airbnb account or API key? No. It reads the public search pages.

Why is currency empty? Airbnb only writes the code into the price text on some searches. When it does not, there is nothing to read, so the field stays empty rather than being guessed.

Can I get more than 20 listings for a city? Not in one run. Search neighbourhoods separately, or vary the dates and guest count, and dedupe on listingId.

Why did my run stop after one row? Almost always one date without the other, or a stray blank line in the locations list. The BAD_INPUT row says which.

Can I get the host's name? Not from search results. Airbnb does not put it on the cards.

Is scraping Airbnb listings legal? These are public search results, read the way a browser reads them. Listings can carry personal data, which GDPR and similar laws cover, so have a reason for collecting it. Apify's write-up on scraping and the law is a good starting point, and we are not lawyers.

🆘 If something breaks

Open the Issues tab on the actor page. Send the run ID, the location and the dates you used. The code on the diagnostic row usually names the problem on its own.