Test one market before you pay
Foreclosure Finder supplies data through an API. You can test a search in RapidAPI before writing code; spreadsheet refreshes and alerts need additional setup. Start with the free BASIC plan: 300 requests per month and core listing fields from all five supported sources.
- Open Foreclosure Finder on RapidAPI and choose BASIC under Pricing. Review the current plan terms.
- Open the all-sources ZIP search endpoint and enter a ZIP code you actually research. Start with radius 25 and limit 10.
- Run the request in RapidAPI and inspect the listings and source-status metadata. A source failure or an empty filtered search does not establish that no properties exist.
- Open the returned propertyLink for listings you want to research. Availability, prices and auction status can change.
Keep a small, useful watchlist
| Column | Purpose |
|---|---|
| source + listingId | Identify a source listing across exports; the same physical property may appear at multiple sources. |
| address, bedrooms, bathrooms, squareFootage | Organize the available property facts for your market. |
| openingBid | An auction opening bid or an REO/MLS asking price. It may be missing or nominal; it is not necessarily the current bid. |
| propertyLink | Return to the original source to verify details. |
| Export date and your notes | Keep your own research history rather than replacing every prior snapshot. |
For Excel or Google Sheets, use the related CSV export guide below. Its download workflow retains response headers for completeness checks; its optional Sheets formula provides a simpler current view. The formula contains your API key, so keep that sheet private and share only a separate values-only copy.
Repeat the search within your request allowance
Start with one saved search and a manual refresh. Each search, extra result page and detail lookup consumes a request, including cached responses. For example, 5 ZIP searches once a week for 4 weeks use 20 requests before additional pages and details. A more frequent workflow with 20 ZIP searches per day uses 600 requests in a 30-day month.
For automated foreclosure alerts, schedule the ZIP search in an external tool such as n8n. Compare returned source and listing IDs with your saved rows, then send a digest of newly seen listings. Keep a separate check status for failed sources so you can retry before treating a missing result as a change.
Search responses use caching and source inventory can be older than the export time. Keep the same filters between snapshots and check failed-source metadata before treating a missing listing as a market change. Foreclosure Finder does not provide a complete historical changes feed.
Choose a plan for your request volume
| Your next step | Plan fit |
|---|---|
| Test coverage and export core listing data | BASIC: $0/month, 300 requests. |
| Refresh more markets or inspect more listings | PRO: $5/month, 1,000 included requests, then $0.10 each. |
| Use richer available property fields | PRO adds coordinates and source-dependent Auction.com bidding, valuations, rent estimates and deal metrics. |
| Plan for more than 1,050 requests per month | ULTRA: $10/month, 10,000 included requests, then $0.05 each. |
| Plan for more than 10,200 requests per month | MEGA: $20/month, 50,000 included requests, then $0.04 each. |
Upgrading does not create inventory or fill fields a source does not publish. Test your market first, then compare the paid fields and request allowance with what your workflow needs. Review current pricing, overage rates and usage on RapidAPI before subscribing.