DEV Community

Crawler Bros
Crawler Bros

Posted on

How to Search US Unclaimed Property Across Multiple States

Finding uncashed municipal checks, vendor refunds, and unclaimed funds across various jurisdictions is a crucial task for asset-recovery researchers, genealogy firms, financial investigators, and data-driven journalists. However, retrieving this public information at scale presents significant operational hurdles.

Most state-level search portals—such as MissingMoney.com or individual state treasury websites—are guarded by aggressive anti-bot defenses, including Cloudflare Turnstile challenges, AWS WAF rules, and CAPTCHAs. These mechanisms block automated scrapers, forcing researchers to manually type queries into web interfaces one search at a time.

To conduct efficient multi-state searches without running into anti-bot walls, automated workflows must tap into the open-data layer underneath state portals: public municipal open-data APIs. The US Unclaimed Property Scraper provides a streamlined solution by directly querying unauthenticated Socrata (SODA) open-data endpoints published by municipal and county treasuries.

Why Traditional Unclaimed Property Portals Are Difficult to Scrape

Most primary live search portals for unclaimed property rely on interactive web applications protected by multi-layered bot detection systems. Sites like MissingMoney.com enforce Cloudflare Turnstile challenges and WAF restrictions on both headless browsers and raw HTTP requests. Similarly, national portals like the FDIC require reCAPTCHA tokens, and state databases often mandate individual access requests.

Instead of targeting web applications blocked by CAPTCHAs, the US Unclaimed Property Scraper accesses the public open-data infrastructure used directly by local treasuries. Many city and county government bodies publish their unclaimed property ledgers and uncashed check registers to public Socrata open-data platforms.

Because these APIs are built for public transparency, they require no authentication, no login credentials, no proxies, and no CAPTCHA solving. The scraper aggregates these public endpoints into a single, structured multi-state lookup tool.

Government Sources and Covered Jurisdictions

The actor extracts data across 6 US states and 9 distinct county and city treasury sources:

  • California: Marin County (Uncashed county checks) and City of Roseville (Stale-dated municipal checks)
  • Maryland: Montgomery County (Unclaimed vendor payments)
  • Massachusetts: Town of Framingham (Unclaimed payroll checks and resident/vendor/AP checks)
  • Minnesota: Ramsey County (Unclaimed money)
  • Rhode Island: City of Providence (Uncashed municipal checks)
  • Texas: City of Austin (Unclaimed property) and City of Corpus Christi (Unclaimed property)

Note: For complete statewide data in California beyond municipal open data, the separate CAUnclaimedPropertyScraper is available, which processes the California State Controller's bulk CSV dataset.

Key Features of the US Unclaimed Property Scraper

The actor is designed to query open registers systematically and emit clean, standardized JSON or tabular output.

1. Dual Operational Modes

The actor operates in two distinct execution modes specified by the mode parameter:

  • search: Searches registers for records matching a specific full or partial payee name via the ownerName input.
  • browse: Fetches an entire state or jurisdiction register without requiring a name filter.

2. Multi-State Execution in a Single Run

By setting the state parameter to ALL, the actor queries all 9 covered government open-data sources concurrently and merges the results into a single dataset. Alternatively, you can target specific states (CA, MD, MA, MN, RI, TX) or narrow down the search to an individual source using the jurisdiction parameter.

3. Financial and Sorting Filters

You can isolate actionable leads using specific numeric and chronological thresholds:

  • minAmountUsd: Filters out low-value records, keeping only balances that meet or exceed a specific dollar amount.
  • maxAmountUsd: Sets an upper limit on property values.
  • sortBy: Reorders returned records by amountDesc, amountAsc, dateDesc, dateAsc, or source relevance.
  • maxItems: Limits the maximum number of emitted records per run.

Understanding Output Fields

Each record emitted by the scraper uses standard field naming conventions across jurisdictions. When a source government body does not disclose a particular detail, that field is left omitted rather than populated with placeholder data.

Standard output fields include:

  • ownerName: The name of the person, vendor, or entity owed money.
  • amountUsd: Disclosed monetary value (omitted if the source does not list amounts, as with the City of Austin).
  • reportedDate: ISO check or transaction date (YYYY-MM-DD).
  • address, city, postalCode: The last known mailing address on file.
  • recordId: Source-specific check or item identifier.
  • vendorId and invoiceDate: Specific to Montgomery County, MD vendor records.
  • paymentStatus: Discloses bank/ERP status (e.g., "Negotiable" or "Void") where available.
  • jurisdiction / holderName: The municipal government entity holding the funds.
  • propertyType: The asset category (e.g., "Unclaimed Vendor Payment (County)").
  • sourceUrl: The exact URL of the government open-data page hosting the record.
  • recordType: Set to "unclaimedProperty".
  • scrapedAt: UTC timestamp recorded when the data was extracted.

How to Run the US Unclaimed Property Scraper

Setting up and running a search requires only a few basic inputs. Here is a step-by-step guide to configuring the actor:

  1. Select the Mode: Choose search to look up specific individuals or corporate entities, or choose browse to export full public registers for analysis.
  2. Set Target Geography: Select ALL in the state field to run a nationwide search across all supported sources, or select a specific state code like CA or TX.
  3. Specify Search Parameters: If running in search mode, enter your target string into ownerName (for instance, Smith or Acme).
  4. Apply Financial Thresholds: Set minAmountUsd to 100 or higher to exclude small balances and focus strictly on high-value recoveries.
  5. Set Result Limits and Sorting: Select amountDesc in the sortBy drop-down menu to view larger items first, and specify your output cap using maxItems.
  6. Execute and Export: Run the actor to fetch live results directly from the government APIs. Export the output in JSON, CSV, or Excel formats for downstream processing.

Practical Professional Use Cases

  • Asset-Recovery Research: Asset finders can scan county and municipal registers for uncollected funds, filter for high-value checks using minAmountUsd, and contact rights-holders.
  • Heir and Genealogy Identification: Estate researchers can run surname queries across multiple jurisdictions using mode="search" and state="ALL" to locate lost assets belonging to estates.
  • Corporate Accounting Audits: Finance and accounting teams can search company names against vendor payment logs to identify uncollected municipal checks or outstanding vendor credits.
  • Investigative Journalism: Local reporters can browse city registers (e.g., setting state to MA or TX) to report on unclaimed public funds or stale municipal checks.

Frequently Asked Questions

Does this scraper search every state treasury in the US?

No. It queries 9 specific county and municipal open-data datasets across CA, MD, MA, MN, RI, and TX that expose public Socrata APIs. State-level treasury portals generally enforce anti-bot challenges that prevent direct automated scraping.

Why do some records lack a dollar amount?

Certain jurisdictions (such as the City of Austin, TX) publish public owner registers without revealing the underlying dollar value. To maintain data integrity, amountUsd is omitted when not disclosed by the source.

Can I claim funds directly through this tool?

No. The scraper strictly retrieves public open data for research and analysis. To claim funds, you must contact the specific government office listed in the holderName field or visit the link provided in sourceUrl.

How up to date is the returned data?

Because the actor makes live requests directly to each government dataset's Socrata API, results reflect the most current public data published by each treasury.


Ready to try it yourself? Run *US Unclaimed Property Scraper** on the Apify Store -- no setup required.*

Top comments (0)