# Airbnb Listings Scraper - Fast Issue Response (`kasimba/airbnb-listings`) Actor

Search Airbnb by location and get price, rating, reviews and property type per listing. Filters out non-listing page elements before billing — you're never charged for a decoy.

- **URL**: https://apify.com/kasimba/airbnb-listings.md
- **Developed by:** [John J. K. Omolo](https://apify.com/kasimba) (community)
- **Categories:** Travel, Real estate, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $28.00 / 1,000 listing scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Airbnb Listings Scraper — Fast Issue Response

Search a location on Airbnb, get structured listing data: price, rating, reviews, host, coordinates.

### Why this exists

The most-used Airbnb listings scraper on the Store has 668+ monthly users and a 172-item closed-issue history, almost all of it one repeating pattern: Airbnb's page structure shifts, the scraper throws `Cannot read properties of undefined (reading 'map')`, and the fix lands roughly nine days later. Not a quality problem — a diagnostics and response-time problem.

Two things are built specifically against that pattern.

**Every run tells you what it actually got.** Airbnb's own search page states how many listings exist for a location. Every run in this Actor compares its scraped count against that number and reports the ratio — in the `RUN_STATS` record, per location. If a run returns 12 of a claimed 250, you're told, not left to notice the shortfall yourself. The incumbent's most common closed issue — *"Only 41 results returned when Airbnb shows 478 listings"* — is exactly the failure this is built to surface instead of hide.

**When extraction breaks, it says what broke.** Three independent extraction strategies run in order, and every failure is logged with which strategy failed and why — "selector `[data-testid='card-container']` matched 0 elements," not a bare stack trace three layers deep. When Airbnb changes shape again, whoever is fixing it gets a diagnosis, not a mystery.

### What you get

Per listing: `listingId`, `url`, `title`, `priceText`, `currency`, `rating`, `reviewsCount`, `isSuperhost`, `latitude`, `longitude`, plus which location it came from and which extraction strategy produced it.

**On currency:** Airbnb prices in whatever currency matches the residential proxy's exit region, and it can genuinely change between runs and even between locations in the same run - one run returned Moroccan Dirham for Vilnius, Trinidad and Tobago Dollars for Tallinn, and a bare `$` for Riga, all in the same three-location call. `priceText` always carries whatever currency marker Airbnb actually showed rather than a bare number, and `currency` makes it explicit: an ISO-style code (`TTD`, `MAD`) when Airbnb showed one - authoritative, since several currencies share the same symbol - or a bare symbol when it didn't, which is honestly ambiguous rather than guessed as USD. To pin a consistent currency across runs, add `display_currency=USD` (or your preferred code) to a full Airbnb search URL and pass that URL directly in `locations` - passing a full URL instead of a bare place name is already supported.

### Input

| Field | Required | Description |
|---|---|---|
| `locations` | yes | City/region names, or a full Airbnb search URL if you need filters already applied |
| `maxListingsPerLocation` | no | Caps billable results per location. Default 50 |
| `proxyConfiguration` | no | Defaults to Apify Residential. Don't turn this off — Airbnb blocks datacenter IPs within a handful of requests |

### Scope, honestly

**v1 covers one search results page per location** — Airbnb's default load, roughly 18–20 listings. No pagination yet. That's a deliberate scope choice, not an oversight: this is a genuinely new engineering surface (real browser, anti-bot, a target site that reshapes itself), and the discipline that held up building the rest of this catalogue was proving something narrow works before expanding it. Pagination is a contained addition once this has real running history behind it.

**Coverage is reported, never hidden.** If a location returns fewer listings than Airbnb claims exist — because of the one-page limit, a partial load, or a shape change — that shows up in `RUN_STATS` as a coverage ratio, not as a silent shortfall.

**A suspect result gets one retry with a fresh proxy before it's accepted.** Confirmed live: a completely valid, unambiguous search returned scattered, unrelated content from all over the world when it landed on a proxy IP Airbnb's anti-bot evidently didn't trust — then worked perfectly when re-run alone. Two signals now trigger an automatic retry: a suspiciously low listing count (below 5, against a healthy ~10), or titles with no geographic coherence at all (Airbnb's generic fallback content looks like this; even a loosely fuzzy-matched real result clusters around a handful of nearby places). When a retry fires, `RUN_STATS` records why and which attempt was kept. This roughly doubles the time and proxy cost for the specific locations it triggers on — not every run, and not most locations.

### Pricing

Pay per listing scraped. An empty result fails the run rather than billing you for nothing. A retried location may use roughly double the compute and proxy bandwidth of a normal one; this is absorbed the same way all platform usage is, not passed through as a separate charge.

### Limits

- One results page per location in this version (see Scope, above).
- Needs a real browser and residential proxies; this is not a lightweight Actor.
- Airbnb's page structure changes periodically. This Actor is built to diagnose that quickly when it happens, not to be immune to it — nothing scraping this site can honestly claim immunity.

### For maintainers: what's verified and what isn't

The extraction logic is tested against synthetic HTML fixtures (`tests/test_smoke.py`) that model Airbnb's known data shape from general knowledge of how the site is built. **Those tests confirm the parsing logic is internally correct. They cannot confirm the selectors or JSON keys still match the real, current airbnb.com** — this was built in an environment with no network path to Airbnb, so the very first live run against the real site is the real test, not a formality.

If the first live run returns zero listings for every location, read `RUN_STATS.shapeDriftEvents` first — it names the exact strategy and selector that failed, which is the fastest way back to a working extractor.

# Actor input Schema

## `locations` (type: `array`):

City or region names (e.g. "Vilnius, Lithuania"), or paste a full Airbnb search URL directly if you need specific filters already applied.

## `maxListingsPerLocation` (type: `integer`):

Caps what you're billed for per location. Default 50.

## `proxyConfiguration` (type: `object`):

Which proxies to route requests through. Residential is strongly recommended - Airbnb blocks datacenter IPs within a handful of requests.

## Actor input object example

```json
{
  "locations": [
    "Vilnius, Lithuania"
  ],
  "maxListingsPerLocation": 50,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `listings` (type: `string`):

One record per listing: listingId, url, title, priceText, rating, reviewsCount, isSuperhost, latitude, longitude, searchLocation, extractionStrategy.

## `runStats` (type: `string`):

Per-location coverage ratios and any shape-drift events. Read this before trusting a run's completeness.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "locations": [
        "Vilnius, Lithuania"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("kasimba/airbnb-listings").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "locations": ["Vilnius, Lithuania"] }

# Run the Actor and wait for it to finish
run = client.actor("kasimba/airbnb-listings").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "locations": [
    "Vilnius, Lithuania"
  ]
}' |
apify call kasimba/airbnb-listings --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,kasimba/airbnb-listings"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/JsyxpDTEa2oCl6Kba/builds/hfnQ3tq7xxhXxynSD/openapi.json