Auction.com Foreclosure Listings Scraper

Collect public Auction.com foreclosure, bank-owned (REO), and private-seller auction listings by US location or copied search URL.

Turn changing auction inventory into clean, typed records for deal sourcing, market monitoring, underwriting queues, and real-estate data pipelines.

• 🏠 Search by state, ZIP code, or City, ST
• 🔗 Preserve filters from copied Auction.com residential search URLs
• 💵 Capture opening bids, current bids, value signals, and auction timing
• 📍 Export addresses, coordinates, property facts, occupancy, photos, and public sale flags
• 🔁 Deduplicate listings across all searches in one run
• 🔒 Anonymous, read-only workflow with no login or bidding

What does Auction.com Foreclosure Listings Scraper do?

The Actor opens public Auction.com residential search pages and captures the structured listing data used to render their property cards.

For each property it normalizes the listing ID, public detail URL, address, sale type, listing status, auction dates, price signals, physical attributes, location, and available public terms.

You can run one focused ZIP search or combine several markets in the same job.

The result is a default Apify dataset ready for JSON, CSV, Excel, XML, RSS, or direct API access.

Who is it for?

Distressed-property investors

Build a daily acquisition queue for foreclosure and REO opportunities in selected markets.

Wholesalers and brokers

Find newly active listings, compare auction windows, and prioritize properties for further research.

Servicers and asset managers

Monitor public status, occupancy, bid, and sale-condition changes across known markets.

Real-estate data teams

Feed Auction.com inventory into warehouses, dashboards, valuation models, and change-detection systems.

Market researchers

Measure inventory mix, property characteristics, and auction activity by geography over time.

Why use this Actor?

Manual Auction.com research is useful for one property but difficult to repeat across many markets.

This Actor makes the workflow reproducible:

• ✅ Consistent field names and data types
• ✅ Global result cap for predictable runs
• ✅ Stable deduplication by Auction.com listing ID
• ✅ Source search URL on every row
• ✅ Missing values omitted instead of represented by misleading placeholders
• ✅ Conservative browser sessions through Apify Proxy
• ✅ Public data only

What Auction.com data can you extract?

Category	Example fields
Identity	listingId, propertyId, url, sourceUrl
Address	streetAddress, city, state, county, postalCode, formattedAddress
Status	listingStatus, listingStatusGroup, statusLabel
Sale	productType, assetType, saleFormat, venueType
Auction	auctionStart, auctionEnd, openingBid, currentBid, bidCount, reserveStatus
Values	sellerValue, estimatedValue, estimatedRent
Property	bedrooms, bathrooms, squareFeet, lotSizeAcres, yearBuilt
Classification	occupancyStatus, structureType
Geography	latitude, longitude
Media	primaryPhotoUrl, photoCount
Public flags	buyer premium, financing, interior access, First Look, direct offer, reserve availability
Provenance	eventCode, marketingTags, scrapedAt

Fields are emitted only when Auction.com supplies a meaningful value for that listing.

How to scrape Auction.com listings

1. Open the Actor input page.
2. Keep the prefilled GA location for a small first run, or replace it.
3. Enter states, ZIP codes, or cities such as Atlanta, GA.
4. Optionally paste one or more filtered Auction.com residential search URLs.
5. Set Maximum property listings to the number you need.
6. Keep the default Apify proxy unless you have a specific network requirement.
7. Click Start.
8. Open the Dataset tab to preview or export the records.

A first test with 10–25 records is enough to validate your workflow before scaling up.

Input options

Locations

Accepted values are:

• A two-letter state code: GA
• A five-digit ZIP code: 30016
• A city and state: Atlanta, GA

You may provide multiple locations.

Auction.com search URLs

Paste public URLs beginning with:

https://www.auction.com/residential/

This mode is useful when you already selected filters on Auction.com and want the Actor to preserve that search path.

Login, account, bidding, and unrelated Auction.com URLs are rejected.

Maximum property listings

maxItems is a global cap after duplicates are removed.

The allowed range is 1–10,000 and the default is 20.

Proxy configuration

Apify datacenter proxy is enabled by default because it works with the verified browser route.

Advanced users may supply another Apify proxy configuration if their environment requires it.

Input examples

Search one state

{
  "locations": ["GA"],
  "maxItems": 25
}

Search a city and ZIP code

{
  "locations": ["Atlanta, GA", "30016"],
  "maxItems": 100
}

Use a filtered Auction.com URL

{
  "searchUrls": [
    {
      "url": "https://www.auction.com/residential/TX/active_lt/auction_date_order,resi_sort_v2_st/y_nbs"
    }
  ],
  "maxItems": 50
}

Combine URL and location modes

{
  "locations": ["FL"],
  "searchUrls": [
    {
      "url": "https://www.auction.com/residential/GA/active_lt/auction_date_order,resi_sort_v2_st/y_nbs"
    }
  ],
  "maxItems": 200
}

Output example

{
  "listingId": "2117192",
  "propertyId": "1454629",
  "url": "https://www.auction.com/details/40-oak-terrace-dr-covington-ga-2117192",
  "sourceUrl": "https://www.auction.com/residential/GA/active_lt/auction_date_order,resi_sort_v2_st/y_nbs",
  "formattedAddress": "40 Oak Terr Dr, Covington, GA 30016, Newton County",
  "listingStatus": "AUCTION_IN_PROGRESS",
  "assetType": "BANK_OWNED",
  "auctionStart": "2026-07-13T12:00:00Z",
  "auctionEnd": "2026-07-15T15:03:20Z",
  "openingBid": 100000,
  "currentBid": 150000,
  "bedrooms": 4,
  "bathrooms": 3,
  "squareFeet": 1907,
  "yearBuilt": 2006,
  "occupancyStatus": "VACANT",
  "latitude": 33.593629,
  "longitude": -83.9259868,
  "scrapedAt": "2026-07-14T04:27:03.978Z"
}

Values above illustrate the output shape. Auction status and prices change at the source.

How much does it cost to scrape Auction.com listings?

This Actor uses pay-per-event pricing. A $0.005 start charge covers browser and proxy-session startup, then each saved listing is charged once.

Apify plan tier	Price per listing	Approx. 1,000 listings plus start
Free	$0.00059408	$0.60
Bronze	$0.00051659	$0.52
Silver	$0.00040294	$0.41
Gold	$0.00030995	$0.31
Platinum	$0.00020664	$0.21
Diamond	$0.00014465	$0.15

A measured 20-listing run finished in about 31 seconds. Use a low maxItems value for a cheap test, then estimate a larger run from your source geography.

No item event is charged for a property skipped as a duplicate.

Monitoring new foreclosures and auction changes

Apify schedules can run the same Actor input hourly, daily, or weekly.

A practical monitoring workflow is:

1. Create one task per market or portfolio.
2. Run the task on a regular schedule.
3. Export listing IDs, status, auction dates, and bids to your database.
4. Compare the newest dataset with the previous snapshot.
5. Notify an analyst when a listing is new or a tracked field changes.

Because every row includes listingId, sourceUrl, and scrapedAt, downstream change detection stays straightforward.

Data quality and deduplication

The Actor deduplicates by Auction.com's listing ID across all supplied inputs.

It preserves source-native status and type labels instead of guessing equivalent categories.

Monetary and area values are emitted as numbers.

Auction timestamps are kept in the ISO format supplied by the source.

Optional fields are omitted when the source does not provide them.

This avoids confusing empty strings and top-level null values in exports.

Tips for reliable runs

• 🎯 Start with one state, city, or ZIP and a low result limit.
• 🔗 Copy the full residential search URL after applying filters.
• 🧭 Use City, ST, including the comma, for city inputs.
• 📦 Split very different markets into separate tasks when you want independent schedules.
• 🔁 Use listingId as the primary key in your database.
• 🕒 Treat bid and status fields as snapshots that may change quickly.
• 🧾 Keep sourceUrl for auditability.

If a valid search has no active inventory, try a broader geography or a less restrictive Auction.com filter.

Integrations

Google Sheets

Use the Google Sheets integration to maintain a review queue for acquisitions teams.

Airtable

Upsert records by listingId and create views for states, occupancy, or auction end date.

Slack and email

Send notifications only for newly observed IDs or important status and bid changes.

Webhooks

Trigger an ETL job when a scheduled run finishes.

Make and Zapier

Connect dataset items to CRM, due-diligence, or analyst-assignment workflows without custom infrastructure.

Cloud storage and warehouses

Export JSON or CSV to S3, BigQuery, Snowflake, PostgreSQL, or your preferred analytics stack.

API usage

Auction.com scraper API with Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/auction-com-foreclosure-listings-scraper').call({
  locations: ['Atlanta, GA'],
  maxItems: 50,
});

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

Auction.com scraper API with Python

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("automation-lab/auction-com-foreclosure-listings-scraper").call(
    run_input={"locations": ["30016"], "maxItems": 50}
)
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

Auction.com scraper API with cURL

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

Fetch dataset items after the run finishes:

$curl "https://api.apify.com/v2/datasets/DATASET_ID/items?clean=true&format=json"

Use Auction.com data with MCP and AI agents

Connect the Actor to Claude or another MCP-compatible client through:

https://mcp.apify.com/?tools=automation-lab/auction-com-foreclosure-listings-scraper

Example prompts:

• “Find up to 25 active Auction.com listings in Georgia and rank them by opening bid per square foot.”
• “Collect Auction.com listings around ZIP 30016 and summarize vacant bank-owned properties.”
• “Compare today's auction dates and current bids with yesterday's saved dataset.”

Claude Code

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

Claude Desktop, Cursor, and VS Code

Add this server under the Claude Desktop, Cursor, or VS Code MCP settings and authenticate with your Apify token:

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

Ask the connected client to call the Actor with a small input first, inspect the records, and then increase maxItems.

Legality and responsible use

This Actor accesses anonymously visible, public listing data and performs no account or transaction actions.

Whether a particular use is permitted depends on your jurisdiction, Auction.com's terms, the volume and purpose of collection, and how you store or redistribute the data.

You are responsible for:

• Reviewing applicable terms and laws
• Using proportionate collection limits
• Respecting intellectual-property and database rights
• Protecting any derived personal or business information
• Avoiding unlawful discrimination or prohibited real-estate practices

This documentation is not legal advice.

Troubleshooting

Why did my run return no listings?

The search may have no current inventory, filters may be too narrow, or Auction.com may have changed the path.

Try a state-level search with a low maxItems value to confirm the workflow.

Why was my URL rejected?

Only public HTTPS URLs under auction.com or www.auction.com with a /residential/ path are accepted.

Login, saved-search, bidding, and arbitrary external URLs are intentionally blocked.

Why is a field missing?

Auction.com does not expose every field for every listing. Missing optional values are omitted rather than filled with guesses.

Why did a browser session fail?

Auction.com uses bot protection. The Actor retries once with a rotated proxy session and then fails clearly rather than emitting partial challenge pages as data.

Can I scrape sold listings?

Use a copied Auction.com residential search URL containing the desired listing-status filters. The Actor follows the public filter path in that URL.

FAQ

Does this Actor require an Auction.com account?

No. It uses anonymous public residential search data.

Does it place bids or save searches?

No. The Actor is read-only and never automates account or transaction actions.

Can I search several states in one run?

Yes. Add several values to locations; the global maxItems cap applies after deduplication.

Can I scrape one property detail URL?

Version 1 focuses on search results. Supply a residential search URL containing that property and identify it by listingId or url in the output.

How fresh is the data?

Each run is a live snapshot of the public source. The scrapedAt field records collection time.

What should I use as a database key?

Use listingId. propertyId may also be useful, but a property can participate in different listing events over time.

Related real-estate scrapers

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

• Zillow Scraper for mainstream listings and property details
• Realtor.com Scraper for residential inventory research
• Google Maps Scraper for nearby services and local business enrichment

Use Auction.com listing coordinates or ZIP codes as join keys for downstream market enrichment.

Support

If a valid public Auction.com residential search fails, open an Actor issue and include:

• The exact input JSON
• The run ID
• The affected search URL
• The approximate time of the run
• Whether the search works anonymously in your browser

Do not include Auction.com credentials, bidding information, or other sensitive data.