Auction.com Property Scraper

Collect foreclosure, bank-owned (REO), short-sale and private-seller auction listings from Auction.com in minutes. Search by state, city, ZIP, property type, asset type, beds, baths, square footage and price, or paste any Auction.com search URL. Every listing comes back with 45+ structured fields including auction dates, starting bids, estimated value, occupancy, coordinates and photos.

Why this scraper

• Two input modes. Build a query from structured filters, or paste one or more Auction.com URLs. Multiple URLs are supported in a single run.
• 45+ fields per listing, well past the typical 30-field offering: auction window, starting bid, estimated resale value, occupancy status, financing and buyer-premium flags, beds/baths/sqft, lot size, year built, latitude/longitude, photos and more.
• Walks the whole catalogue by default. maxPages defaults to 0 (unlimited) — the run walks every result page using offset pagination, stopping on its own once the site's reported total is reached, a page comes back empty, or a page returns no new listings (repeat-page guard). There is no artificial page-number ceiling; the only cap you need is maxListings.
• maxListings is the sole cap on volume (default 20, so a first run is small and fast; set 0 for unlimited on paid plans).
• Resumable runs. Set resumeFromRunId to a previous run or dataset id to collect only the listings that run doesn't already have (a delta) — combine both datasets for the full set. Long unlimited runs also checkpoint their progress to the key-value store, so an Apify platform migration or a Resurrect of a failed run picks up where it left off instead of starting over.
• Incremental & dedup mode for scheduled runs. Turn on incrementalMode and run the same search daily — the actor remembers the previous run itself and returns only NEW, UPDATED, and REAPPEARED listings by default; unchanged listings are suppressed (and not billed). See Resume & recurring updates.
• Optional full-detail mode. Turn on fetchDetails for complete auction terms, financing preference, deposit and earnest-money minimums, leaseback terms and days-to-close per listing (plus any extra media the listing exposes).
• Fast and lightweight. Reads structured data directly, so runs finish quickly and cheaply on the default Apify datacenter proxy. No residential proxy required.
• Multi-state and multi-URL in a single run, with automatic de-duplication.

Data you get

Sample shape: values are illustrative placeholders, not from a live listing.

Field	Example
listingId	00000001
url	https://www.auction.com/details/123-sample-st-city-st-00000001
address	123 Sample St, Springfield, ST 00000, Sample County
city / state / zip	Springfield / ST / 00000
county	Sample County
latitude / longitude	38.0000 / -90.0000
propertyTypeGroup	SINGLE_FAMILY
assetType	BANK_OWNED
listingStatusGroup	ACTIVE
bedrooms / bathrooms	3 / 2
squareFootage	1800
lotSize	0.25
yearBuilt	1995
startingBid	150000
estimatedValue	225000 (property value estimate)
rentalEstimate	1800 (monthly rent estimate)
auctionType	ONLINE
auctionStartDate	2026-01-01T00:00:00Z
auctionEndDate	2026-01-03T00:00:00Z
occupancyStatus	VACANT
financingAvailable	true
buyerPremiumAvailable	false
isRemoteBidEnabled	true
primaryPhoto	https://adc-tenbox-prod.imgix.net/resi/property_image/0000000-1-G.v4.jpg
photoCount	12
financePreference (detail mode)	CASH
daysToClose (detail mode)	30
earnestMoneyDepositMinimum (detail mode)	5000

Plus marketing tags, open houses, trustee-sale flags, valuation bands, and the complete source record under raw for any field not surfaced flat.

How to use

Search a single state for active listings:

{
  "mode": "search",
  "states": ["CA"],
  "listingStatus": "active",
  "maxListings": 200
}

Walk an entire state's active-listing catalogue with no page limit (bounded only by the site's own total and maxListings):

{
  "mode": "search",
  "states": ["CA"],
  "listingStatus": "active",
  "maxListings": 0
}

Resume a previous run, collecting only listings it doesn't already have:

{
  "mode": "search",
  "states": ["CA"],
  "maxListings": 0,
  "resumeFromRunId": "<a previous run id or dataset id from this account>"
}

Search with filters (condos and townhouses, 3+ beds, under 300k, in two states):

{
  "mode": "search",
  "states": ["TX", "FL"],
  "propertyTypes": ["condos-townhouses"],
  "minBeds": 3,
  "maxPrice": 300000,
  "sortBy": "price-asc",
  "maxListings": 500
}

Bank-owned, online auctions, with full details:

{
  "mode": "search",
  "states": ["GA"],
  "assetTypes": ["bank-owned"],
  "auctionFormats": ["online"],
  "fetchDetails": true,
  "maxListings": 100
}

Paste Auction.com URLs (apply filters on the website, then copy the URL):

{
  "mode": "url",
  "urls": [
    "https://www.auction.com/residential/CA/active_lt/single-family_pt",
    "https://www.auction.com/residential/TX/active_lt"
  ],
  "maxPages": 3
}

Input parameters

Parameter	Type	Default	Description
mode	string	search	search (use filters) or url (paste links)
states	array	["CA"]	Two-letter US state codes
city	string		City name to narrow the search
zipCodes	array		List of 5-digit ZIP codes
keyword	string		Free-text search across street, city, state, ZIP
listingStatus	string	active	active or sold
propertyTypes	array		single-family, condos-townhouses, multi-family, land
assetTypes	array		bank-owned, foreclosures, short-sales, private-seller
auctionFormats	array		online, in-person, remote-bid
minBeds / maxBeds	integer		Bedroom range
minBaths	integer		Minimum bathrooms
minSqft / maxSqft	integer		Living area range in square feet
minPrice / maxPrice	integer		Starting bid range in USD
sortBy	string	default	Sort order
urls	array		Auction.com URLs (URL mode)
fetchDetails	boolean	false	Fetch the full gallery and terms per listing
maxPages	integer	0	Optional bound on pages walked per search/URL (100 listings per page). 0 = walk the whole catalogue: stops on its own at the site's reported total, an empty page, or a page with no new listings — never an artificial page cap. Does not cap listing count; use maxListings for that.
maxListings	integer	20	The sole cap on total listings collected (max 1,000,000). 0 means unlimited.
resumeFromRunId	string		Optional id of a previous run (or dataset) of this actor. Listings already in that dataset are skipped, so this run returns only new listings (a delta). For recurring daily monitoring of the same search, use incrementalMode instead.
incrementalMode	boolean	false	Turn on for daily/recurring monitoring. Returns only NEW/UPDATED/REAPPEARED listings after the first run; unchanged listings are suppressed and not billed unless emitUnchanged is on.
stateKey	string		Optional. Name a monitoring campaign explicitly, or share state across differently-configured runs. Leave empty to derive a key automatically from the search/filter setup.
emitUnchanged	boolean	false	Also return listings unchanged since the last run, marked UNCHANGED (extra billed rows).
emitExpired	boolean	false	Also return listings no longer found, marked EXPIRED. Only produced once a run fully scans the tracked search (not capped, not resumed).
proxy	object	Apify datacenter	Proxy configuration

Resume & recurring updates

There are two different things here — pick the one that matches what you're doing:

Need	Use
A run stopped and should continue	resumeFromRunId / automatic checkpoint recovery
Run the same search every day and receive only changes	incrementalMode
Keep separate daily campaigns for similar searches	distinct stateKey values
Run a normal full snapshot	leave both off

Resume (resumeFromRunId) continues one specific interrupted or previous large run: paste a run id or dataset id and this run skips listings already collected there, returning only the remaining new listings. An automatic same-run checkpoint also protects against platform migrations/Resurrects without any input needed.

Incremental mode (incrementalMode) is for a schedule (for example, daily): the actor remembers the previous run of the same search by itself, so you never paste a run id. The first run returns everything as NEW. Later runs return only NEW, UPDATED, and REAPPEARED listings by default — duplicates and unchanged listings are suppressed (and not charged). Turn on emitUnchanged or emitExpired only when you also want those rows returned (and billed for). State is isolated automatically per mode/states/city/zipCodes/keyword/listingStatus/propertyTypes/assetTypes/auctionFormats/beds/baths/sqft/price/sortBy/urls/fetchDetails setup — maxPages/maxListings are caps, not filters, and deliberately do not affect the state key, so raising your cap on a later run does not re-bill the whole catalogue. Set stateKey to name or deliberately share a monitoring campaign. EXPIRED is only synthesized once a run fully scans every search/URL target (not capped by Max listings/Max pages, not a Resume run, not a checkpoint-interrupted run).

When incrementalMode is on, every returned record also carries:

Field	Description
changeType	NEW | UPDATED | UNCHANGED | REAPPEARED | EXPIRED
changedFields	Top-level fields that changed since last seen; non-empty only for UPDATED
firstSeenAt	When this listing was first observed by this monitoring campaign
lastSeenAt	When this listing was last observed

What drives change detection: every flat top-level field (address, status, price/bid, auction dates, occupancy, etc.) except scrapedAt, which is stamped fresh on every push and excluded so it never fakes an UPDATED. The verbatim raw/detailRaw passthrough fields are also excluded from the diff — the GraphQL selection this actor requests (src/dsl.py) is a fixed field list, not a wildcard, and every field it returns is already mirrored onto a flat field above, so raw/detailRaw would only duplicate the same signal while roughly tripling the incremental-state footprint. They are always still returned in the output; a real price, bid, auction-date, or status change still triggers UPDATED as usual.

Scheduled-run example — same search, run daily:

Day 1 (first run ever for this search):

{ "mode": "search", "states": ["CA"], "incrementalMode": true }

→ every listing comes back with "changeType": "NEW".

Day 2 (the schedule fires again, identical input):

{ "mode": "search", "states": ["CA"], "incrementalMode": true }

→ listings whose price/status/auction date/etc. changed come back as "changeType": "UPDATED" with changedFields listing what changed, brand-new listings come back as "changeType": "NEW" — and listings that are still there, unchanged, are not returned at all (suppressed, not charged) unless emitUnchanged is on.

Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step after the scrape — the Apify dataset is never changed.

What gets written to the connector: a condensed, human-readable summary of each record — not the full JSON. Each item becomes one entry with a title and its key fields flattened to plain text. The complete record always stays in the Apify dataset.

1. Authorize a connector once under Apify → Settings → Integrations (Notion, Linear, Airtable, or Apify).
2. Select it in the "Pipe results into your apps" input field. (If the picker is empty, you haven't authorized a connector yet.)
3. For Notion, also set notionParentPageUrl to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.

Output example

Sample shape: values are illustrative placeholders, not from a live listing.

{
  "listingId": "00000001",
  "url": "https://www.auction.com/details/123-sample-st-springfield-st-00000001",
  "address": "123 Sample St, Springfield, ST 00000, Sample County",
  "city": "Springfield",
  "state": "ST",
  "zip": "00000",
  "county": "Sample County",
  "latitude": 38.0000,
  "longitude": -90.0000,
  "propertyTypeGroup": "SINGLE_FAMILY",
  "assetType": "BANK_OWNED",
  "productType": "REO",
  "occupancyStatus": "VACANT",
  "listingStatusGroup": "ACTIVE",
  "bedrooms": 3,
  "bathrooms": 2,
  "squareFootage": 1800,
  "lotSize": 0.25,
  "yearBuilt": 1995,
  "startingBid": 150000,
  "estimatedValue": 225000,
  "estimatedValueLow": 210000,
  "estimatedValueHigh": 240000,
  "auctionType": "ONLINE",
  "auctionStartDate": "2026-01-01T00:00:00Z",
  "auctionEndDate": "2026-01-03T00:00:00Z",
  "financingAvailable": true,
  "buyerPremiumAvailable": false,
  "isRemoteBidEnabled": true,
  "primaryPhoto": "https://adc-tenbox-prod.imgix.net/resi/property_image/0000000-1-G.v4.jpg",
  "photoCount": 12,
  "marketingTags": [],
  "scrapedAt": "2026-01-01T00:00:00Z"
}

Plan requirement

This scraper runs on the default Apify datacenter proxy, so it works on the free plan for small runs. For large runs and faster throughput, any paid plan gives more compute and proxy bandwidth. Residential proxy is optional and not required for this source. If you do select residential, the run rotates a US/CA exit pool (a fresh session per attempt, and any explicit country pin is respected) and automatically fails over to a backup connection pool after repeated failures, so a single flagged exit IP will not stall the run. Free accounts should keep maxListings modest; paid accounts can set it to 0 for unlimited.