HUD Home Store Foreclosure Listings Scraper

Extract current HUD Home Store foreclosure listings without a login or API key.

Search by city, state, ZIP code, or copied HUD search URL and export clean property records for sourcing, monitoring, and analysis.

The scraper returns list prices, bid windows, bidder eligibility, FHA financing, property facts, coordinates, amenities, and images from the public HUD Home Store.

What does HUD Home Store Foreclosure Listings Scraper do?

HUD Home Store Foreclosure Listings Scraper turns public US government-owned foreclosure and REO searches into structured data.

Use a location such as Houston, TX, a state code such as TX, or a HUD search URL.

The Actor then:

• 🔍 fetches the official anonymous search result;
• 🏠 extracts every property in the source response;
• 🧹 normalizes prices, counts, dates, and coordinates;
• 🔁 deduplicates overlapping searches by HUD case number;
• 🎯 applies your price, bedroom, bathroom, property, period, and bidder filters;
• 📦 exports the result to JSON, CSV, Excel, XML, or RSS.

Unlike browser-heavy alternatives, this Actor uses the server-rendered HUD data route and normally needs only 256 MB of memory.

No HUD account, API token, or manual CAPTCHA step is required.

Who is it for? HUD foreclosure buyers and monitors

Real-estate investors and wholesalers

• Sweep states or local markets for distressed inventory.
• Filter by list price, bedroom count, and property type.
• Feed qualified deals into underwriting spreadsheets.

Brokers and buyer agents

• Watch new and price-reduced HUD inventory.
• Track list dates, bid-open dates, and bid deadlines.
• Separate all-bidder listings from restricted eligibility periods.

Owner occupants and housing organizations

• Find homes open to owner occupants.
• Identify nonprofit or government-agency eligibility.
• Check FHA financing and the HUD $100 Down program flag.

Data and operations teams

• Schedule repeat state searches.
• Compare case numbers between runs to detect new inventory.
• Send changed records to a database, CRM, Slack, or webhook.

Why use this HUD Home Store scraper?

• ✅ Current official source — records come from public HUD Home Store searches.
• ✅ Rich listing data — not just addresses and prices.
• ✅ Typed output — prices, areas, years, and coordinates are numbers.
• ✅ ISO dates — source dates are normalized to YYYY-MM-DD.
• ✅ Stable deduplication — HUD case number is the unique key.
• ✅ No browser overhead — fast direct HTTP for ordinary runs.
• ✅ No login or API key — only anonymous listing search is used.
• ✅ Apify-native automation — API, schedules, datasets, webhooks, and integrations are included.

The Actor intentionally excludes bidding, favorites, account access, and email/share actions.

What HUD foreclosure data can you extract?

Category	Fields
Identity	HUD case number, street address, full location
Geography	city, state, ZIP, county, latitude, longitude
Pricing	list price
Property facts	beds, baths, square feet, year built, age, stories
Classification	property type, property status, listing period
Financing	FHA financing status, HUD $100 Down flag
Bid workflow	list date, bid-open date, bid deadline
Eligibility	eligible bidder summary and bidder types
Features	indoor amenities, outdoor amenities, parking
Media	thumbnail URL and gallery image URLs
Provenance	source search URL and scrape timestamp

Optional fields are omitted when HUD does not publish a value for that listing.

Pricing: How much does it cost to scrape HUD foreclosure listings?

This Actor uses pay-per-event pricing.

You pay a $0.005 search-run start fee and a small amount per unique listing saved.

Apify plan	Price per listing	100 listings plus start
Free	$0.000064738	$0.0115
Starter / Bronze	$0.000056294	$0.0106
Scale / Silver	$0.000043909	$0.0094
Business / Gold	$0.000033776	$0.0084
Platinum	$0.000022518	$0.0073
Diamond	$0.000015762	$0.0066

Filtering happens before listings are saved and charged.

The Apify Free plan includes platform credits, so a small local-market search is inexpensive to evaluate.

How to scrape HUD Home Store listings

1. Open the Actor on Apify.
2. Add one or more locations.
3. Keep maxItems low for your first run.
4. Add optional price, bedroom, property, or bidder filters.
5. Click Start.
6. Preview the dataset while the run executes.
7. Export the finished records or connect an integration.

A simple city input:

{
  "locations": ["Houston, TX"],
  "maxItems": 25
}

A state inventory sweep:

{
  "locations": ["TX"],
  "maxItems": 250,
  "maxConcurrency": 2
}

An owner-occupant sourcing workflow:

{
  "locations": ["TX"],
  "maxPrice": 250000,
  "minBedrooms": 3,
  "eligibleBidders": ["Owner Occupant"],
  "maxItems": 100
}

Input parameters

Parameter	Type	Default	Description
locations	string[]	[]	City, ST, two-letter state code, or ZIP searches
searchUrls	URL[]	[]	Copied HUD /searchresult URLs with citystate
maxItems	integer	25	Global unique-listing limit
minPrice	integer	—	Minimum USD list price
maxPrice	integer	—	Maximum USD list price
minBedrooms	number	—	Minimum bedroom count
minBathrooms	number	—	Minimum bathroom count
propertyTypes	string[]	[]	Exact HUD property-type labels
listingPeriods	string[]	[]	Exact HUD period labels, such as Exclusive
eligibleBidders	string[]	[]	Match any exact bidder type
maxConcurrency	integer	3	Simultaneous HUD searches, from 1 to 10
proxyConfiguration	object	—	Optional Apify or custom proxy configuration

At least one non-empty locations or searchUrls value is required.

Search URLs are restricted to the official HTTPS HUD Home Store search-result path.

HUD property filter values

HUD labels can change as inventory changes.

Common propertyTypes include:

• Single Family Home
• Condo

Common listingPeriods include:

• Exclusive
• Extended

Common eligibleBidders values include:

• Investor
• Owner Occupant
• Nonprofit
• Government Agency

String filters are exact but case-insensitive.

If you filter on a value that HUD omitted, that listing is excluded rather than guessed.

Output example

{
  "caseNumber": "493-806212",
  "address": "802 Seafoam Rd",
  "city": "Houston",
  "state": "TX",
  "zipCode": "77062",
  "fullLocation": "802 Seafoam Rd, Houston, TX 77062",
  "county": "Harris",
  "listPrice": 287040,
  "bedrooms": 4,
  "bathrooms": 3,
  "squareFeet": 2494,
  "yearBuilt": 1971,
  "propertyType": "Single Family Home",
  "propertyStatus": "Price Reduced",
  "listingPeriod": "Extended",
  "fhaFinancing": "IE (Insured Escrow)",
  "listDate": "2026-07-14",
  "bidOpenDate": "2026-07-16",
  "bidDeadlineDate": "2026-11-25",
  "eligibleBidders": "All Bidders",
  "bidderTypes": ["Investor", "Owner Occupant", "Nonprofit", "Government Agency"],
  "specialProgram100Down": true,
  "latitude": 29.5572,
  "longitude": -95.1306,
  "thumbnailUrl": "https://res.cloudinary.com/yardi/image/upload/.../Front_73825875.png",
  "imageUrls": ["https://res.cloudinary.com/yardi/image/upload/.../Front_73825875.png"],
  "sourceSearchUrl": "https://www.hudhomestore.gov/searchresult?citystate=Houston%2C+TX",
  "scrapedAt": "2026-07-16T00:00:00.000Z"
}

HUD controls inventory and can remove or update records at any time.

Monitor new and changed HUD listings

Use an Apify schedule to run the same state or city search daily.

The stable caseNumber field makes change detection straightforward:

• a new case number means a newly observed listing;
• a missing case number may mean inventory was removed;
• the same case number with a new price or deadline means the listing changed.

For production monitoring, store the prior dataset in your database or compare datasets with an automation platform.

Tips for best results

• Start with one city and maxItems: 25.
• Use a two-letter state code for broader coverage.
• Search overlapping locations freely; duplicates are removed.
• Use exact HUD labels in array filters.
• Keep concurrency between 1 and 3 for large scheduled sweeps.
• Omit proxy configuration unless your network needs it.
• Treat a valid empty dataset as “no current matching inventory,” not necessarily an error.
• Check run logs when every source search fails.

Integrations and automation workflows

HUD listings → Google Sheets

Append affordable listings to a shared acquisitions sheet for underwriting.

HUD listings → Slack or Discord

Send a message when a new case number appears or a bid deadline changes.

HUD listings → Make or Zapier

Create a CRM lead, map task, or broker follow-up for every qualified property.

Scheduled state monitor

Run each morning and compare case number, list price, status, and deadline with the previous run.

Dataset webhook → data warehouse

Load normalized property records into BigQuery, Snowflake, PostgreSQL, or an internal deal platform.

API usage with Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/hud-home-store-foreclosure-listings-scraper').call({
  locations: ['Houston, TX'],
  maxItems: 25,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

The call waits for completion and returns the run metadata.

Use the Apify API with Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/hud-home-store-foreclosure-listings-scraper').call(
    run_input={'locations': ['TX'], 'maxItems': 100}
)
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

Use asynchronous client methods when integrating into an async service.

Use the Apify API with cURL

curl -X POST \
  "https://api.apify.com/v2/acts/automation-lab~hud-home-store-foreclosure-listings-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"locations":["Houston, TX"],"maxItems":25}'

Read the run's defaultDatasetId, then download its items through the Dataset API.

Use with AI agents via MCP

HUD Home Store Foreclosure Listings Scraper is available to AI assistants through the Model Context Protocol.

For Claude Code:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=automation-lab/hud-home-store-foreclosure-listings-scraper"

For Claude Desktop, Cursor, or VS Code:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=automation-lab/hud-home-store-foreclosure-listings-scraper"
    }
  }
}

Your client will request Apify authentication when first connected.

Try asking specific example prompts such as:

• “Use automation-lab/hud-home-store-foreclosure-listings-scraper to find current HUD homes in Houston under $250,000.”
• “Find three-bedroom Texas HUD listings open to owner occupants and sort them by bid deadline.”
• “Create a daily monitor for new HUD case numbers and price reductions in my target state.”

Reliability and error handling

Each source request has three bounded attempts with incremental backoff.

A normal source response with no inventory produces zero records successfully.

A response missing HUD's expected embedded data is treated as extraction failure.

If every requested search fails, the run exits non-zero instead of silently reporting success.

If one search fails but another succeeds, the run preserves useful results and logs the failed URL.

Limitations

• Inventory is limited to what HUD Home Store publishes publicly.
• Some city or ZIP searches legitimately have no active properties.
• HUD may omit optional fields for individual homes.
• Filters use current source labels and do not infer missing values.
• The Actor does not open property detail pages or submit bids.
• Bidding eligibility should always be confirmed with HUD and a qualified broker.
• Search behavior can change when HUD updates its website.

Legality: Is it legal to scrape HUD Home Store?

This Actor extracts publicly accessible government property-listing data without logging in or bypassing access controls.

Scraping public information is generally lawful in many jurisdictions, but your use of the data may be subject to website terms, fair-housing rules, privacy law, and other obligations.

Use reasonable run frequency, collect only data needed for a legitimate purpose, and do not use housing data for unlawful discrimination.

You are responsible for complying with applicable law and HUD requirements.

FAQ

How fast is the HUD foreclosure scraper?

A city search usually completes in seconds because the Actor reads server-rendered data without launching a browser. Multiple locations run with conservative parallelism.

How much does one run cost?

The run starts at $0.005 plus the tier-specific fee for each unique listing saved. A Bronze run saving 100 listings costs about $0.0106.

Does HUD provide an official public API key?

No key is needed for this workflow. The Actor reads the same public listing data served by HUD Home Store's anonymous search page.

Why did my location return no results?

HUD may have no current inventory matching that city or ZIP. Try a two-letter state search and remove filters to distinguish no inventory from an overly narrow query.

Why is an optional field missing?

HUD does not publish every attribute for every property. Missing values are omitted rather than replaced with inaccurate guesses.

Can this Actor place a bid?

No. It supports research and monitoring only. Bid submission, login, favorites, and email/share features are deliberately out of scope.

Can I use a copied HUD URL?

Yes. Add an official HTTPS /searchresult URL containing the citystate query parameter to searchUrls.

Related real-estate scrapers

Build a broader property-data workflow with other Automation Labs Actors:

• Auction.com Foreclosure Listings Scraper — private auction and REO inventory.
• Zillow Scraper — residential listing and property data.
• Realtor.com Scraper — residential search records.
• Redfin Scraper — market and listing research.
• Google Maps Scraper — local broker and service-provider discovery.

Use HUD Home Store Foreclosure Listings Scraper when you specifically need official HUD-owned inventory and bidder-window data.

Support

For a reproducible support request, include:

• the Actor run URL;
• the exact input used;
• the location or HUD search URL;
• the expected case number, if known;
• whether the source page currently shows that property.

Do not include passwords, private account cookies, or bid information.