# Estately Real Estate Scraper (`crawlerbros/estately-scraper`) Actor

Scrape Estately.com real-estate listings by city, ZIP code, or state - active for-sale or recently-sold homes with price, beds/baths, square footage, photos, and full property-detail lookups by URL.

- **URL**: https://apify.com/crawlerbros/estately-scraper.md
- **Developed by:** [Crawler Bros](https://apify.com/crawlerbros) (community)
- **Categories:** Real estate, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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

## Estately Real Estate Scraper

Scrape real-estate listings from [Estately.com](https://www.estately.com) — active for-sale homes or recently-sold/closed comps, searched by city, ZIP code, or state. Also fetch a full property-detail record (description, features, walkability scores, agent, photos) from any Estately listing URL. No login, no API key, no cookies required.

### What this actor does

- **Two modes:** `byLocation` (search) and `byPropertyUrl` (detail lookup)
- **Search by** city name, ZIP code, or both, within a US state
- **Listing status:** active for-sale or recently-sold/closed
- **Filters:** property type, price range (server-side), min bedrooms/bathrooms, square-footage range (client-side)
- **Full pagination** — up to 200 listings per request page, automatically paginated to your `maxItems`
- **Rich detail records:** description, flattened feature list (100+ possible attributes: building, interior, financial, schools, parking, utilities), agent contact, walk/bike/transit scores, photo gallery
- **Empty fields are omitted** — every record only contains data Estately actually published for that listing

### Output per listing (search mode)

- `listingId`, `mlsNumber`, `mlsAcronym`
- `sourceUrl` — canonical Estately listing URL
- `status`, `propertyType`, `isRental`
- `price`, `soldDate`, `timeOnSite`
- `beds`, `baths`, `sqft`, `lotSqft`, `photoCount`
- `address`, `city`, `state`, `zipCode`, `latitude`, `longitude`
- `officeName`, `officePhone`
- `thumbnailUrl`
- `recordType: "listing"`, `scrapedAt`

### Additional fields (detail mode, `byPropertyUrl`)

- `description` — full listing narrative (`marketingRemarks`)
- `yearBuilt`, `pricePerSqft`, `annualTax`, `hoaDues`
- `agentName`, `agentPhone`
- `features[]` — flattened `"Group > Label: Value"` strings across every Estately attribute group (building, interior, room dimensions, financial & terms, location, property, taxes, heating/cooling, utilities, appliances, schools, community, parking)
- `walkScore`, `bikeScore`, `transitScore`
- `photoUrls[]` — full-size listing photos (capped at 30)
- `recordType: "propertyDetail"`

### Input

| Field | Type | Console prefill | Description |
|---|---|---|---|
| `mode` | select | `byLocation` | `byLocation` (search) or `byPropertyUrl` (detail lookup) |
| `state` | select | `tx` | US state (mode=byLocation); optional if `zipCode` is given. No forced default via API - if omitted, no state filter is applied |
| `city` | string | `Austin` | City name (mode=byLocation). No forced default via API - `city` and/or `zipCode` is required |
| `zipCode` | string | – | 5-digit ZIP, used instead of `city` |
| `listingStatus` | select | `forSale` | `forSale` or `sold`. No forced default via API - falls back to `forSale` in code if omitted |
| `propertyType` | select | `any` | `any` / `house` / `condo` / `townhouse` / `multiFamily` / `land` |
| `minPrice` / `maxPrice` | int | – | Price range in USD |
| `minBeds` / `minBaths` | int | – | Minimum bedrooms / bathrooms |
| `minSqft` / `maxSqft` | int | – | Living-area square-footage range |
| `propertyUrls` | array | – | Estately listing URLs/paths (mode=byPropertyUrl); deduplicated automatically |
| `maxItems` | int | `50` | Hard cap (1–1000) |
| `proxyConfiguration` | object | AUTO | Optional; free Apify datacenter proxy fallback (not required in practice) |

> Note: only `mode`, `maxItems`, and `proxyConfiguration` have a real schema default (auto-filled when omitted from an API call). All other fields listed with a "Console prefill" value only pre-populate the Console *Start* button/daily test run - they are **not** injected when the field is omitted from a programmatic `POST /runs` call, so omitting `state`/`city`/`listingStatus` leaves them genuinely unset (subject to the code-level fallback noted above).

#### Example: for-sale condos in Miami under $500k

```json
{
  "mode": "byLocation",
  "state": "fl",
  "city": "Miami",
  "propertyType": "condo",
  "maxPrice": 500000,
  "maxItems": 50
}
```

#### Example: recently-sold homes in a ZIP code

```json
{
  "mode": "byLocation",
  "state": "tx",
  "zipCode": "78704",
  "listingStatus": "sold"
}
```

#### Example: full detail for specific listings

```json
{
  "mode": "byPropertyUrl",
  "propertyUrls": [
    "https://www.estately.com/listings/info/8211-greenslope-dr-austin-tx-78759--1"
  ]
}
```

### Use cases

- **Home buyers/renters** — track new listings and price drops in a target city or ZIP
- **Real-estate investors** — pull comps (recently-sold) alongside active listings for a market
- **PropTech / data products** — feed structured listing data into a dashboard or valuation model
- **Market research** — compare price-per-sqft and inventory mix across cities
- **Lead generation** — collect listing-office contact info for a target area

### Data source & limitations

Estately's own front-end calls a public, unauthenticated JSON API (`estately.com/api/v3/search`) to render its search results, and embeds a structured JSON data island on every listing-detail page. This actor reads both directly instead of parsing rendered HTML.

- Bedroom/bathroom/square-footage filters are applied to the fetched listings client-side, because the upstream search API does not support them as query parameters (only price range and property type are server-side filters). Results are still complete — the actor paginates through every upstream page up to your `maxItems` before applying these filters.
- No login, cookies, or paid proxy are required. An optional free Apify AUTO datacenter proxy is exposed as a fallback but is not needed in practice.
- Sold-listing records may omit `price` where the source MLS restricts display of the closing price (a common MLS rule) — this is a genuine data-availability gap, not a scraping bug.

### FAQ

**Do I need an Estately account or API key?** No — this actor only reads publicly-served, unauthenticated endpoints.

**What if my city isn't found?** The actor returns a clear status message ("no results for location=...") when Estately doesn't recognize the location; try `zipCode` instead, or check spelling/state.

**How many listings can I get per run?** Estately's API returns up to 200 listings per page; the actor paginates automatically until it reaches `maxItems` (max 1000) or upstream results are exhausted.

**Can I get more than the top-level listing fields?** Yes — pass any listing's `sourceUrl` into a `byPropertyUrl` run to get the full detail record (description, all feature groups, walkability scores, photos, agent).

# Actor input Schema

## `mode` (type: `string`):

What to fetch.

## `state` (type: `string`):

US state the city is in. Optional when searching by `zipCode`.

## `city` (type: `string`):

City name, e.g. `Austin`. Provide `city` and/or `zipCode`.

## `zipCode` (type: `string`):

5-digit US ZIP code. Used instead of `city` if both are omitted from `city`.

## `listingStatus` (type: `string`):

Active for-sale listings, or recently-sold/closed listings.

## `propertyType` (type: `string`):

Restrict to one property type.

## `minPrice` (type: `integer`):

Drop listings priced below this.

## `maxPrice` (type: `integer`):

Drop listings priced above this.

## `minBeds` (type: `integer`):

Drop listings with fewer bedrooms than this.

## `minBaths` (type: `integer`):

Drop listings with fewer bathrooms than this.

## `minSqft` (type: `integer`):

Drop listings smaller than this (living area, sqft).

## `maxSqft` (type: `integer`):

Drop listings larger than this (living area, sqft).

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

Full Estately listing-detail URLs (e.g. from a `sourceUrl` field of a byLocation run), or bare `/listings/info/...` paths.

## `maxItems` (type: `integer`):

Hard cap on emitted records.

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

Optional. Uses Apify's free datacenter (AUTO) proxy pool. A direct (no-proxy) fetch is used by default; this is only a fallback.

## Actor input object example

```json
{
  "mode": "byLocation",
  "state": "tx",
  "city": "Austin",
  "listingStatus": "forSale",
  "propertyType": "any",
  "propertyUrls": [],
  "maxItems": 50,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

Dataset containing all scraped Estately records.

# 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 = {
    "mode": "byLocation",
    "state": "tx",
    "city": "Austin",
    "listingStatus": "forSale",
    "propertyType": "any",
    "propertyUrls": [],
    "maxItems": 50,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("crawlerbros/estately-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 = {
    "mode": "byLocation",
    "state": "tx",
    "city": "Austin",
    "listingStatus": "forSale",
    "propertyType": "any",
    "propertyUrls": [],
    "maxItems": 50,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("crawlerbros/estately-scraper").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "mode": "byLocation",
  "state": "tx",
  "city": "Austin",
  "listingStatus": "forSale",
  "propertyType": "any",
  "propertyUrls": [],
  "maxItems": 50,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call crawlerbros/estately-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=crawlerbros/estately-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

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