# Homes.com Scraper - Homes For Sale & Rent (`s-r/homes-com-scraper`) Actor

Scrape property listings from Homes.com. Address, asking price, beds, baths, floor area, price per square foot and open-house times, for any city or filtered search.

- **URL**: https://apify.com/s-r/homes-com-scraper.md
- **Developed by:** [SR](https://apify.com/s-r) (community)
- **Categories:** Real estate, E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 per-run start fees

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Homes.com Scraper

Property listings from Homes.com as a clean table. Give it a city and get back
what is on the market there: the full address, the asking price, the bed and
bath counts, the floor area, the price per square foot, and the open-house
window when one is advertised.

It takes Homes.com's own slug, like `new-york-ny` or `austin-tx`, and walks the
result pages for you. It also takes a full search URL, so if you have already
narrowed a search in the browser to three bedrooms under $800,000, paste that
URL and every filter in it is respected.

Both sides of the market come back the same way. `listing_type` says `for sale`
or `for rent` on every row, taken from the page rather than guessed from the
price, so a mixed search stays sortable.

### What you get per listing

- `address`, `url`, `property_key`, `listing_key`
- `price`, `beds`, `baths`, `sqft`
- `price_per_sqft`, worked out for you
- `listing_type`, `open_house`
- `search`, `search_page`, `position`, and `result_count`

`price_per_sqft` is the first thing anyone computes and the easiest to get
subtly wrong across a mixed set, so it is done once, here. It is null rather
than zero whenever either input is missing.

`result_count` is the total the search itself reports, which is much larger
than what any run returns. New York reports over twenty thousand listings and
serves eighteen pages of them. Having both numbers on the row tells you what
share of a market you are holding.

### Run sizes and paging

Result pages hold forty listings each. **Maximum listings** caps the run across
every location and trims the last page, so asking for 50 costs the same as
asking for 80. **Maximum pages per location** is the rail that stops one large
city from consuming a whole run.

A hundred listings takes a few seconds. There is no second request per listing:
everything above is on the search page already, so a run is one page load per
forty rows and nothing more.

### Errors

A location that fails becomes an entry in the `errors` record rather than a
missing set of rows:

| Code | Meaning |
|---|---|
| `bad_input` | No location supplied |
| `no_results` | The location was read and genuinely has no listings |
| `fetch_failed` | A result page could not be read after several attempts |

`no_results` and `fetch_failed` are deliberately different. An empty city and a
page that would not load look identical if you only count rows, and only one of
them is worth rerunning.

### A note on reliability

Route access to this site is narrow and can change without warning. If a run
suddenly returns `fetch_failed` across the board where it worked last week,
that is what has happened; it is not a bad location. Re-run once, and if it
persists, say so rather than working around it.

### Related actors

For US rentals specifically, use **Apartments.com Scraper**. For homes for sale
with MLS numbers and sold history, use **Redfin Scraper**. For the UK market,
use **Rightmove Scraper**.

# Actor input Schema

## `search` (type: `array`):

One per line. Use homes.com's own slug, for example new-york-ny, or paste a full search URL with filters already applied.

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

Across all locations. Result pages hold forty listings each, so this trims the last page rather than shortening it.

## `maxPages` (type: `integer`):

The safety rail on a large city.

## Actor input object example

```json
{
  "search": [
    "new-york-ny",
    "https://www.homes.com/austin-tx/homes-for-rent/"
  ],
  "maxItems": 100,
  "maxPages": 10
}
```

# Actor output Schema

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

One row per listing.

## `summary` (type: `string`):

Locations walked and listings returned.

## `errors` (type: `string`):

Locations that could not be read.

# 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 = {
    "search": [
        "new-york-ny"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("s-r/homes-com-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 = { "search": ["new-york-ny"] }

# Run the Actor and wait for it to finish
run = client.actor("s-r/homes-com-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 '{
  "search": [
    "new-york-ny"
  ]
}' |
apify call s-r/homes-com-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,s-r/homes-com-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/7J0WnzXSbhyjNeFrX/builds/APbLOL6EInMxZbDRT/openapi.json