Redfin Property Scraper

Redfin Property Scraper extracts structured records in bulk and exports them for analysis, enrichment and downstream pipelines. It covers twitter, content, posts, related, metadata, indexing, analysis, monitoring, collects, user, timeline, search-query, results, trending-topic, scoped, country, reply, threads, individual, tweets.

Built for teams that need performs, web-based, social, media, returns, social-data, post, text without maintaining scrapers, proxies or browser infrastructure themselves.

Quick start (SDK examples)

Python

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("redfin-property-scraper").call(run_input={"targets": ["<target>"], "maxResults": 100})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript

import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: "YOUR_APIFY_TOKEN" });
const run = await client.actor("redfin-property-scraper").call({ targets: ["<target>"], maxResults: 100 });
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

cURL

curl -X POST "https://api.apify.com/v2/acts/redfin-property-scraper/runs?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"targets":["<target>"],"maxResults":100}'

Fields returned

field	description	type
address	address returned for every record	string
url	url returned for every record	string
price	price returned for every record	string
beds	beds returned for every record	string
baths	baths returned for every record	string
area	area returned for every record	string
image	image returned for every record	string
propertyId	propertyId returned for every record	string
listingId	listingId returned for every record	string
mlsId	mlsId returned for every record	string
mlsStatus	mlsStatus returned for every record	string
unitNumber	unitNumber returned for every record	string
city	city returned for every record	string
scrapedAt	scrapedAt returned for every record	string

What it does

• Extract twitter, content, posts, related, metadata, indexing into structured rows.
• Enrich each record with analysis, monitoring, collects, user, timeline, search-query.
• Bulk export covering results, trending-topic, scoped, country, reply, threads.
• Pipeline integration for individual, tweets, performs, web-based, social, media.
• Downstream analysis across returns, social-data, post, text, timestamps, engagement.
• Recurring monitoring of metrics, author, relationships, trend, identifiers, suitable.
• Deduplicated output keyed on the record identifier.
• Configurable result caps and runtime bounds.

Use cases

• Lead generation — build contactable lists covering twitter, content, posts, related, metadata
• Data enrichment — attach indexing, analysis, monitoring, collects, user to an existing record set
• Market research — map timeline, search-query, results, trending-topic, scoped across a category or region
• Competitive monitoring — track country, reply, threads, individual, tweets over time on a schedule
• AI and RAG pipelines — feed clean structured rows into embeddings and retrieval
• Warehousing — land performs, web-based, social, media, returns into BigQuery, Snowflake or Postgres

Input

Provide targets as a list of URLs or identifiers, one per line.

input	purpose
targets	URLs or identifiers to process, one per line
maxResults	hard cap on returned rows
maxSeconds	runtime bound for the run
includeEmpty	return rows that resolved to no data, or skip them

Output

Every run writes a dataset exportable as CSV, Excel, JSON, or readable directly from the Apify API. Attach a webhook to push results into your own system as soon as a run finishes.

Integrations

Works with Zapier, Make, n8n, Google Sheets, Slack, and any HTTP endpoint via webhooks. The Apify MCP server exposes this Actor to AI agents directly.

Performance and limits

Runs are concurrent and bounded by maxResults and maxSeconds. Proxy rotation and retry handling are managed for you. Failed targets are reported rather than silently dropped.

Frequently asked questions

Do I need an account or cookies?

No. The Actor reads public data only and requires no login, cookies or personal API keys.

What formats can I export?

CSV, Excel, JSON, or read the dataset straight from the Apify API.

What does a row contain?

Every row carries twitter, content, posts, related, metadata, indexing, analysis, monitoring where available.

Can I schedule it?

Yes. Attach a schedule or a webhook and the dataset is produced on your cadence.

How do I limit cost?

Use maxResults to cap returned rows and maxSeconds to bound runtime.

Is the output stable?

Field names are fixed by the dataset schema, so downstream pipelines do not break between runs.

Field glossary

address — the address associated with the record. Present on every row where the source exposes it; absent values are returned as null rather than omitted, so column order stays stable across runs and downstream schemas do not drift. url — the url associated with the record. Present on every row where the source exposes it; absent values are returned as null rather than omitted, so column order stays stable across runs and downstream schemas do not drift. price — the price associated with the record. Present on every row where the source exposes it; absent values are returned as null rather than omitted, so column order stays stable across runs and downstream schemas do not drift. beds — the beds associated with the record. Present on every row where the source exposes it; absent values are returned as null rather than omitted, so column order stays stable across runs and downstream schemas do not drift. baths — the baths associated with the record. Present on every row where the source exposes it; absent values are returned as null rather than omitted, so column order stays stable across runs and downstream schemas do not drift. area — the area associated with the record. Present on every row where the source exposes it; absent values are returned as null rather than omitted, so column order stays stable across runs and downstream schemas do not drift. image — the image associated with the record. Present on every row where the source exposes it; absent values are returned as null rather than omitted, so column order stays stable across runs and downstream schemas do not drift. propertyId — the propertyId associated with the record. Present on every row where the source exposes it; absent values are returned as null rather than omitted, so column order stays stable across runs and downstream schemas do not drift. listingId — the listingId associated with the record. Present on every row where the source exposes it; absent values are returned as null rather than omitted, so column order stays stable across runs and downstream schemas do not drift. mlsId — the mlsId associated with the record. Present on every row where the source exposes it; absent values are returned as null rather than omitted, so column order stays stable across runs and downstream schemas do not drift. mlsStatus — the mlsStatus associated with the record. Present on every row where the source exposes it; absent values are returned as null rather than omitted, so column order stays stable across runs and downstream schemas do not drift. unitNumber — the unitNumber associated with the record. Present on every row where the source exposes it; absent values are returned as null rather than omitted, so column order stays stable across runs and downstream schemas do not drift. city — the city associated with the record. Present on every row where the source exposes it; absent values are returned as null rather than omitted, so column order stays stable across runs and downstream schemas do not drift. scrapedAt — the scrapedAt associated with the record. Present on every row where the source exposes it; absent values are returned as null rather than omitted, so column order stays stable across runs and downstream schemas do not drift.

Troubleshooting

• Empty dataset — Check that targets contains reachable identifiers and that includeEmpty is set the way you expect.
• Run times out — Lower maxResults or raise maxSeconds; very large target lists are better split across scheduled runs.
• Missing fields — Not every source exposes every field. Absent values are returned as null so the schema stays stable.
• Rate limiting — Proxy rotation is automatic. If a source throttles hard, reduce concurrency and retry.
• Duplicate rows — Output is deduplicated on the record identifier; duplicates across separate runs are expected by design.

Data quality notes

Records are parsed from public sources covering twitter, content, posts, related, metadata, indexing, analysis, monitoring, collects, user. Values are returned exactly as published rather than normalised or inferred, so you can audit any row back to its source URL. Timestamps are ISO-8601 UTC. Numeric counters are integers. No field is synthesised when the source does not publish it.

Scheduling and automation

Attach a schedule to run this Actor hourly, daily or weekly. Combine it with a webhook to push each finished dataset into your warehouse, CRM or Slack channel automatically. Runs are idempotent with respect to their input, so a repeated schedule produces a comparable dataset rather than a drifting one.

Support

Open an issue on the Actor's Issues tab. Include the run ID and the input used so it can be reproduced.