Foreclosure API data sources, coverage and fields

Choose the inventory your product needs

Foreclosure Finder combines five supported sources through common search routes. They represent different inventories, so a combined result is a set of source listings—not a complete census of foreclosures or a deduplicated count of physical properties.

Set the path’s source to all for a combined search, choose a single source such as /city/hud, or select a subset with sources=auction,hud on an /all route. A request to this independent service does not imply affiliation with or endorsement by these sources.

Understand geographic coverage

Search by five-digit US ZIP code, city and state, or street address. Explicit radius values are 5, 10, 25, 50 and 100 miles. Collection limits, nearby behavior and state boundaries vary by source; specifying a radius does not make every source an exhaustive radius search.

For example, Redfin radius searches filter the ZIP page and its nearby suggestions. Inventory outside that collected set is not added just because it lies inside the circle. When present, isNearby and distanceMiles help distinguish returned nearby listings. Check the address and original propertyLink for the property you need.

Test your intended markets and source combinations before building an inventory promise into your product. An empty result may reflect sparse source inventory, filters, collection limits or an unavailable source.

Read prices, identifiers and missing fields

• Record identity: use the pair (source, listingId). Different sources can list the same physical property.
• Core fields: address, openingBid, bedrooms, bathrooms, squareFootage, propertyType, status, photoUrl and propertyLink provide a shared search format. Missing values can be null.
• Search price: openingBid represents an auction opening bid or an REO/MLS asking price. Standard price filters and price sorting use that value. A nominal opening bid such as $1 is not a purchase price.
• Paid fields: every paid plan includes the same expanded data where supplied, such as coordinates, lot size and year built, plus Auction.com bidding and estimate fields. Plans differ in request allowance.
• Details: /listing/{source}/{listingId} adds available descriptions, photos, facts, contacts, documents and source-specific details. The presence of a search result does not guarantee every detail field.

Auction.com deal metrics use an eligible current high bid, otherwise the opening bid. grossYield is estimated annual rent divided by that bid, multiplied by 100 and rounded to one decimal: 15 means 15%. It excludes expenses and acquisition costs. Treat estimates and calculated discounts as screening inputs, and confirm the underlying figures on the listing.

Check freshness and partial results

Search responses use a one-hour cache. Source caches and upstream publication delays can make the underlying information older, so bidding values are snapshots. X-Cache: HIT or MISS reports the response cache, not the age of each record.

Combined searches can return HTTP 200 while one source is unavailable. Inspect meta.failedSources and meta.sourceErrors. CSV exports carry unavailable sources in the X-Failed-Sources header. Keep a check status alongside stored results so a partial response is not mistaken for a market-wide change.

Use since as a filter, not a change feed

For “new to my watchlist,” save (source, listingId) across successful searches and record your own first-seen date. A missing row in a later response may reflect filtering, source failure or a withdrawn listing; it is not itself proof of a sale.