# HomeFinder Listing Scraper (`moving_beacon-owner1/homefinder-listing-scraper`) Actor

Scrapes homes-for-sale listings from HomeFinder, including prices, addresses, beds, baths, square footage, property details, photos, coordinates, and listing URLs. Supports location, ZIP code, or custom search URLs with configurable result limits.

- **URL**: https://apify.com/moving\_beacon-owner1/homefinder-listing-scraper.md
- **Developed by:** [Jamshaid Arif](https://apify.com/moving_beacon-owner1) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $9.99 / 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.

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

## HomeFinder Listing Scraper

Collects homes-for-sale listings from HomeFinder.com for a location you choose. Each result includes the price, address, beds/baths, size, photos, and a link to the listing.

### Input

| Field | Default | Description |
|---|---|---|
| `location` | `San-Antonio_TX` | Location to search: `City, ST` (`San Antonio, TX`), slug form (`San-Antonio_TX`), or a ZIP code. Ignored when `start_urls` is set. |
| `start_urls` | `[]` | Explicit HomeFinder search URLs (e.g. `https://homefinder.com/realestateandhomes-search/Austin_TX`); override `location`. |
| `limit` | `42` | Maximum number of listings to return (1–500). |
| `proxyConfiguration` | US proxy on | Optional. Enable a US-based proxy for the most reliable results. |

### Output

Each listing is one record with flat fields plus the full original payload in `raw`.

```json
{
    "property_id": "7398870748",
    "listing_id": "2999751426",
    "status": "for_sale",
    "list_price": 90000,
    "beds": 3,
    "baths": "1",
    "sqft": 6500,
    "lot_sqft": 6534,
    "year_built": 1971,
    "property_type": "single_family",
    "street_address": "5326 Indian Pipe St",
    "city": "San Antonio",
    "state": "TX",
    "postal_code": "78242",
    "county": "Bexar",
    "latitude": 29.344359,
    "longitude": -98.603129,
    "list_date": "2026-08-16T18:56:42.000000Z",
    "listing_url": "https://homefinder.com/realestateandhomes-detail/5326-Indian-Pipe-St_San-Antonio_TX_78242_M73988-70748",
    "primary_photo_url": "https://ap.rdcpix.com/...s.jpg",
    "raw": { ... }
}
```

### Notes

- Runs with empty input (defaults to `San-Antonio_TX`).
- Enable a US-based proxy for the most reliable results.
- Collects only publicly listed data; use it in line with the site's Terms of Service and applicable privacy laws.

# Actor input Schema

## `location` (type: `string`):

Location to search on HomeFinder. Accepts 'City, ST' (e.g. 'San Antonio, TX'), the realtor slug form 'City\_ST' (e.g. 'San-Antonio\_TX'), or a ZIP code. Ignored when 'start\_urls' is provided.

## `start_urls` (type: `array`):

Explicit HomeFinder search URLs to scrape, e.g. https://homefinder.com/realestateandhomes-search/Austin\_TX . When set, these override 'location'. Each is paged automatically.

## `limit` (type: `integer`):

Maximum number of listings to return (42 per search page).

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

Proxy settings for the run. Enable a US-based proxy for the most reliable results, especially for sites that limit non-US or datacenter traffic. Optional — leave off to run directly.

## Actor input object example

```json
{
  "location": "San-Antonio_TX",
  "start_urls": [],
  "limit": 42,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 = {
    "location": "San-Antonio_TX",
    "start_urls": [],
    "limit": 42,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("moving_beacon-owner1/homefinder-listing-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 = {
    "location": "San-Antonio_TX",
    "start_urls": [],
    "limit": 42,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("moving_beacon-owner1/homefinder-listing-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 '{
  "location": "San-Antonio_TX",
  "start_urls": [],
  "limit": 42,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call moving_beacon-owner1/homefinder-listing-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,moving_beacon-owner1/homefinder-listing-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/hXRO8JZfOPOxLvL3X/builds/0kCtTBpoJSdj5TOwd/openapi.json