Airbnb Scraper — Listings, Prices, Reviews & Availability

Turn Airbnb searches into a structured rental-market dataset — from nightly price to host, reviews, amenities, and availability.

Scrape Airbnb listings by location or URL. Export prices, ratings, photos, amenities, host data, reviews, and availability calendars for short-term rental and market research.

All examples below use fictional DEMO-* identifiers, reserved .test domains, and masked contact details. They do not represent real people, listings, products, or companies.

🚀 What this Actor does

• Flexible collection: fast, full.
• Structured output: clean JSON records organized into listings, pricing, host_ratings, calendar_summary views.
• Production-ready: concurrency, retries, proxy support, limits, and source-aware diagnostics are exposed through the Actor input.
• Easy automation: run from the Apify Console, API, schedules, webhooks, Make, Zapier, or any HTTP client.

🎛️ Modes and workflows

Mode or workflow	What it does
fast	Search and return listing-level price, rating, capacity, and location fields with minimal enrichment.
full	Open listing details and add richer amenities, host, reviews, calendar, and availability data.

💡 Common use cases

• Short-term rental comps and pricing research
• Availability and occupancy signal tracking
• Amenity, host, and review analysis

📥 Input schema

Configure the Actor in the Input tab or send the same JSON through the API. Fields not needed for your workflow can be omitted.

Field	Type	Description	Default
mode	string	Fast is optimized for discovery and pricing. Full enriches every listing with all supported public details. Allowed: fast, full.	fast
queries required	array<string>	Add cities, neighborhoods, regions, or direct Airbnb room URLs. The actor detects each value automatically.	—
dateRange	string	Optional check-in/check-out pair in YYYY-MM-DD/YYYY-MM-DD format.	—
adults	integer	Number of adult guests.	2
children	integer	Number of children.	0
infants	integer	Number of infants.	0
pets	integer	Number of pets.	0
maxItemsPerQuery	integer	Maximum unique listings collected for each destination or direct URL batch.	50
maxReviewsPerListing	integer	Maximum guest reviews collected for each listing in Full mode.	50
minPrice	integer	Optional lower price filter for destination searches.	—
maxPrice	integer	Optional upper price filter for destination searches.	—
minBedrooms	integer	Keep listings with at least this many bedrooms.	—
minBathrooms	integer	Keep listings with at least this many bathrooms.	—
minBeds	integer	Keep listings with at least this many beds.	—
roomType	string	Optional Airbnb room-type filter. Allowed: ``, Entire home/apt, Private room, Shared room, Hotel room.	``
currency	string	Currency used for displayed prices. Allowed: USD, EUR.	USD
locale	string	Locale code such as en, de, fr, es or it.	en
proxy	object	The default Apify Proxy configuration is recommended.	{"useApifyProxy": true, "apifyProxyGroups": []}

▶️ Example input

{
  "mode": "full",
  "queries": [
    "Lisbon"
  ],
  "maxItemsPerQuery": 25,
  "maxReviewsPerListing": 10,
  "adults": 2
}

📦 Output schema

Each successful item is written to the default dataset. Select a dataset view in the Apify Console or export the full dataset as JSON, CSV, Excel, XML, or RSS.

listings — Listings

Listing-level records.

Fields: scrapeMode, detailStatus, id, name, displayLocation, displayPrice, pricePerNight, priceTotal, available, displayRating, reviewsCount, roomType, personCapacity, bedrooms, beds, bathrooms, amenityCategoriesCount, amenitiesCount, availableAmenitiesCount, houseRulesCount, safetyItemsCount, highlightsCount, imageUrl, url, scrapedAt

pricing — Pricing

Price-focused records for analysis and monitoring.

Fields: id, name, displayLocation, displayPrice, pricePerNight, priceTotal, priceOriginalTotal, currency, available, url

host_ratings — Hosts & ratings

Host identity, badges, and rating fields.

Fields: id, name, displayRating, ratingValue, reviewsCount, hostName, isSuperhost, hostResponseRate, hostResponseTime, badges, url

calendar_summary — Calendar metrics

Availability and occupancy summary fields.

Fields: id, name, calendarStartDate, calendarEndDate, calendarMonthsCount, calendarDaysCount, calendarAvailableDaysCount, calendarBlockedDaysCount, calendarAvailabilityPercent, calendarOccupancyEstimatePercent, calendarAvailableNext30Days, calendarBlockedNext30Days, calendarOccupancyNext30Percent, calendarAvailableRevenueNext30, calendarAvailableNext90Days, calendarBlockedNext90Days, calendarOccupancyNext90Percent, calendarAvailableRevenueNext90, calendarAvailableNext365Days, calendarBlockedNext365Days, calendarOccupancyNext365Percent, calendarAvailableRevenueNext365, displayPrice, pricePerNight, url

📤 Example output

{
  "scrapeMode": "full",
  "detailStatus": "complete",
  "id": "DEMO-LISTING-01",
  "name": "Demo riverside apartment",
  "displayLocation": "Demo District",
  "displayPrice": "$145 night",
  "pricePerNight": 145,
  "displayRating": "4.8",
  "reviewsCount": 42,
  "bedrooms": 2,
  "url": "https://www.airbnb.com/rooms/DEMO-LISTING-01"
}

Missing source values are returned as null, empty arrays, or documented availability/status fields; the Actor does not invent unavailable source data.

🔌 API example

Replace the placeholder with an Apify token and send the same input used in the Console:

curl -X POST "https://api.apify.com/v2/acts/trakk~airbnb-scraper-v2/runs?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"mode": "full", "queries": ["Lisbon"], "maxItemsPerQuery": 25, "maxReviewsPerListing": 10, "adults": 2}'

For synchronous integrations, use the run-sync-get-dataset-items API endpoint. For larger jobs, start an asynchronous run and consume its default dataset when the run succeeds.

🧩 Automation and exports

• Schedule recurring runs from the Apify Console.
• Trigger downstream systems with webhooks when a run succeeds or fails.
• Reuse named monitoring keys or stores where the selected workflow supports change tracking.
• Export dataset views to JSON, CSV, Excel, XML, or RSS, or access items through the Apify API.

❓ FAQ

Do I need a login or browser session?

Use only the inputs shown in the Actor schema. If authentication or cookies are supported, the relevant encrypted field is explicitly available in the Input tab; otherwise no account is required.

Why can some fields be empty?

Source pages vary by region, content type, privacy settings, and availability. Optional enrichment also depends on the selected mode. Empty values are preserved honestly instead of being guessed.

How should I run this at scale?

Start with a small representative input, inspect the dataset and cost, then raise item limits and concurrency gradually. Use Apify Proxy when the schema exposes it, and use schedules plus monitoring keys for recurring collection.

Is the example data real?

No. Every example in this README is intentionally fictional and uses demo identifiers, reserved domains, or masked contact values.