Foreclosure Finder

Export foreclosure listings to CSV, Excel and Google Sheets

Download a spreadsheet-ready search and keep track of columns, partial results, pagination and request usage.

Download a search as CSV

Add format=csv to a ZIP, city or nearby search. CSV exports work on the free BASIC plan; paid plans add their expanded fields. Set your RAPIDAPI_KEY environment variable using the quickstart, then run this in a macOS or Linux terminal:

curl · CSV and response headers
curl --fail --show-error --max-time 65 \
  --dump-header foreclosure-headers.txt \
  --output foreclosures.csv \
  "https://foreclosure-finder1.p.rapidapi.com/zipcode/all?zipcode=30067&radius=25&minBeds=3&sort=price_asc&limit=100&format=csv" \
  -H "X-RapidAPI-Key: $RAPIDAPI_KEY" \
  -H "X-RapidAPI-Host: foreclosure-finder1.p.rapidapi.com"

The CSV file contains up to 100 matching rows, with a header even when no rows match. Open it in Excel or import it into Google Sheets. Keep the header file with the export so you can review counts and source availability. If curl reports an error, resolve it before using the output as a completed export.

Read the columns without losing identifiers

The first columns are source, listingId, address, openingBid, bedrooms, bathrooms and squareFootage. Standard columns have a fixed order for your plan; additional source fields can appear after them. Import IDs and ZIP codes as text when your spreadsheet offers that option, so leading zeros and identifier formatting are preserved.

Nested values use dotted column names such as coordinates.latitude or bidding.currentHighBid. A missing value is blank; it does not mean zero. Array values may be joined with | or encoded as JSON. Read the header by name when building an automated importer.

Price sorting uses openingBid: the opening bid for auctions and the asking price for REO/MLS listings. The value may be nominal and is not necessarily the current auction bid. Use propertyLink to verify a listing. Source text that starts like a spreadsheet formula is prefixed with an apostrophe by the API.

Check whether your export is complete

Response headerWhat to check
X-Total-CountMatching source listings before pagination, not unique physical properties.
X-ReturnedThe number of listing rows in this CSV response.
X-Failed-SourcesUnavailable sources in a combined search, when present.
X-CacheWhether the response used cached search results; not a per-record timestamp.

If the total exceeds the returned count, repeat the same search with offset=100, then offset=200, keeping limit=100 and all filters unchanged. Each page is another API request. Combine files by header name and keep one header row. The maximum requested page size is 500.

Source failures make a combined export partial even after HTTP 200. Record the failed sources and retry with a delay before drawing conclusions about inventory changes. Results can change as caches expire, so pagination is not a frozen dataset.

Optional: display a private Google Sheets watchlist

For a simple current view, paste this formula into cell A1 of an empty sheet. Replace YOUR_RAPIDAPI_KEY with your own key. Keep cells below and to the right empty so imported rows can expand.

Google Sheets
=IMPORTDATA("https://foreclosure-finder1.p.rapidapi.com/zipcode/all?zipcode=30067&radius=25&limit=100&sort=price_asc&format=csv&rapidapi-key=YOUR_RAPIDAPI_KEY")

The key is visible in this formula. Keep the sheet private; to share results, copy them as values into a separate sheet without the formula. A browser-side application should use your own server with header authentication instead of embedding a customer key.

This formula shows only the requested page. It cannot inspect X-Failed-Sources or page through additional results, and refreshing replaces the current rows rather than retaining history. Use a script or the file export workflow when you need completeness checks.

Budget refreshes and keep a dated snapshot

CSV is a format choice; it does not bypass authentication or request limits. Every API call counts toward your RapidAPI allowance, including cached responses, extra pages and spreadsheet refreshes. Review usage in RapidAPI and choose a refresh schedule suited to your quota.

For a repeatable export, save the request parameters, export time, response headers and file together. Source-level caching can make records older than the export time. Keep your own saved copies if you need history; neither a fresh export nor the Sheets formula is a complete feed of property changes.