# QuintoAndar Property Scraper (Brazil) (`scrapyx/quintoandar-properties-scraper`) Actor

Scrapes apartments and houses for rent or sale from QuintoAndar, Brazil's largest rental platform. Search any city or neighbourhood; returns price, area, bedrooms, bathrooms, address, amenities and photos.

- **URL**: https://apify.com/scrapyx/quintoandar-properties-scraper.md
- **Developed by:** [Ibnu Adzim](https://apify.com/scrapyx) (community)
- **Categories:** Real estate
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.56 / 1,000 results

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/platform/actors/running/actors-in-store#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

## QuintoAndar Property Scraper (Brazil)

Scrapes apartments and houses for rent or sale from
**[QuintoAndar](https://www.quintoandar.com.br)** — Brazil's largest
rental-focused real estate platform.

Public data only. No login, no cookies, no browser.

### The one thing you need to know before using this

**Each location returns a single fixed batch of 12-26 listings — there is
no pagination this actor can reach.** QuintoAndar's search page always
renders the exact same first batch server-side regardless of any page/sort/
offset parameter (all tried and confirmed to change nothing); real
pagination happens client-side against a `/busca` endpoint that
`robots.txt` explicitly disallows for generic crawlers. This actor honours
that. **`locations` being a list is therefore the only way to cover more
ground** — query many neighbourhoods instead of one city, the way you would
split a search into narrower slices anyway.

### What you get

Three record types share one dataset, told apart by `recordType`.

#### `PROPERTY` — one row per listing

Search rows (`listing`) carry price, area, bedrooms, bathrooms,
neighbourhood, condo fee (IPTU), parking spots, amenities and photos. With
**Fetch full property details** on (the default), each row also gets a
`propertyDetails` object with the detail page's richer payload: a full
boolean-flag amenity list, exact street address, and the site's internal
display id.

#### `SEARCH_SUMMARY` — one row per location searched

Upstream's own claimed total (informational only — see above, this actor
can never reach more than the fixed batch) and how many rows this run
actually returned.

### Input

| Field | What it does |
| --- | --- |
| **Alugar / comprar** | rent or buy |
| **Locations** | QuintoAndar slugs: `sao-paulo-sp-brasil`, `vila-madalena-sao-paulo-sp-brasil`… one fixed batch per entry |
| **Property URLs** | scrape specific listings directly, skipping search |
| **Fetch full property details** | off = fast listing-only crawl |

#### Example

```json
{
  "transactionType": "alugar",
  "locations": ["vila-madalena-sao-paulo-sp-brasil", "pinheiros-sao-paulo-sp-brasil", "itaim-bibi-sao-paulo-sp-brasil"],
  "includePropertyDetails": true
}
```

### Notes on reliability

- **No WAF challenge.** Serves data cold on every TLS profile tested.
- **Runs unattended.** No human-captured session, no expiring token.
- **Unknown locations fail cleanly** as `not_found` — QuintoAndar answers
  with an explicit `houses.error: true`, never a silent fallback to a
  nationwide or default search (verified live; a genuine exception among
  real-estate targets in this portfolio, most of which DO silently widen on
  a bad filter).
- **Residential proxy by default** on cloud runs.
- **Failures never vanish.** A listing withdrawn mid-crawl degrades that one
  row (`_detailError`); every input maps to at least one output row.

### Output envelope

Every record carries `_input`, `_source` and `_scrapedAt`. Upstream field
names pass through **verbatim** under `listing` (search) and
`propertyDetails` (detail) — no renaming. `_source` is `S1-nextdata-search`
for listing-only rows and `S1-nextdata-search+S2-nextdata-detail` once
details are attached.

See [`CRAWLING_METHOD.md`](CRAWLING_METHOD.md) for the full reverse-engineering
trail, including why pagination isn't offered and a sample of QuintoAndar's
\~99 supported city slugs.

# Actor input Schema

## `transactionType` (type: `string`):

Which side of the market to search.

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

QuintoAndar location slugs -- ONE FIXED BATCH OF 12-26 LISTINGS PER ENTRY (see below), so this list is the main way to cover more ground, not an optimisation. Cities: 'sao-paulo-sp-brasil', 'rio-de-janeiro-rj-brasil', 'belo-horizonte-mg-brasil', 'porto-alegre-rs-brasil', 'brasilia-df-brasil' (see CRAWLING\_METHOD.md for the ~99 supported cities). Neighbourhoods also work and return a different, often larger batch: 'vila-madalena-sao-paulo-sp-brasil', 'pinheiros-sao-paulo-sp-brasil'. An unrecognised slug returns a clean not\_found row, never a silently-wrong nationwide result.

## `propertyUrls` (type: `array`):

Scrape specific listings directly, skipping search. Accepts a full QuintoAndar property URL (https://www.quintoandar.com.br/imovel/894223429/alugar/...) or a bare numeric id. Can be combined with a location search in the same run.

## `includePropertyDetails` (type: `boolean`):

Fetch the richer detail-page payload (boolean-flag amenity list, exact address, display id) for each result via one extra request per property. Turn this off for a fast listing-only crawl -- search rows already carry price, area, bedrooms, bathrooms, neighbourhood, condo fee, amenities and photos.

## `maxConcurrency` (type: `integer`):

Upper bound on requests in flight at once, across locations and detail fetches.

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

QuintoAndar runs no active bot challenge and a direct connection worked cleanly across every probe this session, but Residential is the default for cloud runs -- container egress is a different posture than a home connection, and this portfolio has lost a full cloud run to that difference before (jobstreet-jobs-scraper, bayt-jobs-scraper).

## Actor input object example

```json
{
  "transactionType": "alugar",
  "locations": [
    "sao-paulo-sp-brasil"
  ],
  "propertyUrls": [],
  "includePropertyDetails": true,
  "maxConcurrency": 4,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `items` (type: `string`):

One row per scraped record. See the dataset's default view for field definitions.

# 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": [
        "sao-paulo-sp-brasil"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapyx/quintoandar-properties-scraper").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": ["sao-paulo-sp-brasil"] }

# Run the Actor and wait for it to finish
run = client.actor("scrapyx/quintoandar-properties-scraper").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": [
    "sao-paulo-sp-brasil"
  ]
}' |
apify call scrapyx/quintoandar-properties-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapyx/quintoandar-properties-scraper"
        }
    }
}

```

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/eEFbtzwsdBNlLe7QX/builds/phoj3iawEVJQZxhtM/openapi.json