RealtyTrac Foreclosure & REO Scraper

RealtyTrac Foreclosure & REO Scraper

Scrape distressed real estate listings from any RealtyTrac location URL, including pre-foreclosures, auctions, and bank-owned REOs, up to a million per run. Every record includes the property address, estimated value, beds, baths, square footage, and listing status. Export to CSV, JSON, Excel, or XML.

Real estate investors, agents, and analysts need off-market leads, but RealtyTrac has no open API and manually copying listings is slow and error-prone. This scraper reads the public foreclosure and REO feeds from any state, county, or city URL you give it and returns each property in one flat table. You control the exact geography and how many records to pull.

Who uses it	What they scrape RealtyTrac for
Real estate investors	Build a fresh list of pre-foreclosure or REO leads in a target county.
Real estate agents	Pinpoint off-market opportunities for buyer clients searching for distressed homes.
Market analysts	Track the volume of foreclosure and auction listings in a metro area over time.
Property wholesalers	Assemble a pipeline of deeply discounted bank-owned properties by ZIP code.

What it does

This Actor collects distressed property listings from a RealtyTrac location URL and returns each one as a flat row with address, beds, baths, square footage, estimated value, and listing status.

• 🏠 Property types: pre-foreclosures, active foreclosures, bank-owned (REO) properties, and sheriff sales.
• 📍 Location-driven: feed it any RealtyTrac location URL and get the exact listings for that page.
• 📏 Flexible volume: set a cap from a single page to a million listings per run so you only pull what you need.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with RealtyTrac data

📋 Build a distressed lead list.

An investor runs the scraper on a Los Angeles County URL, pulls 500 pre-foreclosures, and loads the flat file into PropStream for skip-tracing.

🏦 Monitor REO inventory by market.

An agent sets the actor on a Texas statewide URL once a week, exporting bank-owned listings to spot price drops before they hit the MLS.

📊 Compare auction activity across counties.

An analyst feeds five county URLs, gathers sheriff-sale counts each Friday, and charts the data to advise a hard-money lender on local risk.

🔍 Filter for specific property specs.

A wholesaler scrapes a city URL, then filters the output spreadsheet by bedrooms and estimated value to find three-bedroom REOs under $200,000.

Why choose this scraper

	What you get
No API needed	Reads the live RealtyTrac foreclosure feed like a browser, with no registration or key.
Consistent output	Every property lands in your dataset with the same fields, ready for your CRM or spreadsheet.
Full geography control	Point it at exactly the foreclosure market you care about, from a state page to a single ZIP.

How it compares

This actor focuses exclusively on RealtyTrac foreclosure feeds with simple URL-based configuration, while the competitor listed below scrapes the same source.

Feature	ParseForge	RealtyTrac Foreclosure & REO Listings Scraper (jungle_synthesizer)
Pre-foreclosure listings	Yes	Yes
Active foreclosure listings	Yes	Yes
Bank-owned (REO) listings	Yes	Yes
Sheriff sale listings	Yes	Yes
Location URL input	Yes	Not listed
Configurable maximum items per run	Up to 1,000,000	Not listed

Configure the run

Drive the Actor from any RealtyTrac location URL, from the state level down to a city or ZIP code, and set a maximum number of listings so you stop when you have enough leads. The Input tab lists every parameter.

A first run with the defaults:

{
 "locationUrl": "https://www.realtytrac.com/foreclosure/california/los-angeles-county/",
 "maxItems": 10
}

A larger pull:

{
 "locationUrl": "https://www.realtytrac.com/foreclosure/california/los-angeles-county/",
 "maxItems": 200
}

Pricing

Pay-per-result: $0.01 per result collected. You pay only for the results written to your dataset.

Results collected	Approximate cost
100 results	$1.00
1,000 results	$10.00
10,000 results	$100.00

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the RealtyTrac Foreclosure & REO Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to RealtyTrac through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/realtytrac-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results?

Check that the locationUrl is a valid RealtyTrac foreclosure page and that the page shows listings when you open it in a regular browser. If the URL is a general location page without any active listings, the actor will return zero rows. Try a broader or different location.

The actor stops early before reaching the maxItems count.

RealtyTrac pagination may end earlier than expected if the location has fewer properties. Confirm how many listings exist on the live page, then adjust your maxItems to match or exceed that number if you want every available record.

Some properties are missing data like beds or baths.

RealtyTrac does not always display every field for every listing. If a bedroom count or value is missing on the live site, that field will be empty in your output. This is source-level data, not a scraper error.

I get a timeout or a browser error.

Increase the run timeout in your task settings if the location has a very large number of listings. If the error persists, the target page layout may have changed; open a support ticket and include the locationUrl you used.

FAQ

Question	Answer
Can I scrape a single ZIP code instead of a whole state?	Yes. Paste the exact RealtyTrac URL for that ZIP code into the locationUrl field. The actor will only return listings from that page and any pagination that follows it.
Does the scraper handle pre-foreclosures and sheriff sales?	It collects whatever listings appear on the RealtyTrac URL you provide. If the page shows pre-foreclosures, active foreclosures, REOs, or sheriff sales, those will all appear in your dataset.
Do I need a RealtyTrac account to run this?	The actor reads the public listing data that RealtyTrac shows to logged-out visitors. You do not need an account or a subscription to collect that information.
What fields does the scraper return?	You get the property address, number of bedrooms and bathrooms, square footage, estimated value, and listing status. Additional fields that are visible on the page, such as lot size or year built, may also be included when present.
How many listings can I pull in one run?	You can set the maximum from 1 to 1,000,000. A single run will keep paginating until it hits your cap or runs out of available listings on that location URL.
Can I schedule this actor to run weekly?	Yes. After you configure the run, open the Schedules tab, set a weekly interval, and the actor will automatically collect fresh leads on your cadence.
Is the output ready for a spreadsheet or CRM?	The default dataset is a table of rows and columns that you can export to CSV, JSON, Excel, or XML. Most CRMs and spreadsheet tools can import those formats directly.
Will the actor pick up auction dates and starting bids?	If a listing on the current RealtyTrac page includes an auction date or a starting bid, that information will appear in the dataset row for that property. The actor captures the fields as they are shown on the live page.

Related actors

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by ATTOM Data Solutions. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.