US County & City Unclaimed Funds Scraper avatar

US County & City Unclaimed Funds Scraper

Pricing

from $0.49 / 1,000 results

Go to Apify Store
US County & City Unclaimed Funds Scraper

US County & City Unclaimed Funds Scraper

Search unclaimed money and uncashed checks published by US county and city treasuries across six states. Search by owner name or browse by state, with amount, holder, property type and dates where disclosed.

Pricing

from $0.49 / 1,000 results

Rating

0.0

(0)

Developer

vexaloom-labs

vexaloom-labs

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Share

US Unclaimed Property & Funds Scraper

Search unclaimed money and uncashed checks across 12 public US registers in one run. The actor reads statewide bulk files from California and Iowa plus municipal open-data registers, then returns owner, amount, holder, property type, dates and property IDs where the source discloses them.

What it does

  • Three modes: search by owner name, browse a register, and byPropertyId for an exact property, warrant or check lookup.
  • 12 sources in 7 states: California, Iowa, Massachusetts, Maryland, Minnesota, Rhode Island and Texas.
  • Up to 50,000 records per run — the old 1,000-row ceiling is gone, and every source is paginated or streamed to its own limit.
  • Useful filters: amount range, include/exclude records with no disclosed amount, date range, broad property-type groups, raw type text and property ID.
  • Seven sort orders: amount, date, owner name and source order.
  • Empty fields are omitted — the actor never invents a value for a field a source does not publish.

Services covered

StateSourceWhat it publishes
CACalifornia State Controller (SCO)Statewide unclaimed property, weekly ZIP/CSV archive
CAMarin CountyUncashed county checks
CACity of RosevilleStale-dated municipal checks
CASonoma CountyStale-dated county checks
IAIowa Department of Administrative ServicesOutdated state warrants by fiscal year
MATown of FraminghamUnclaimed payroll checks
MATown of FraminghamUnclaimed resident/vendor/AP checks
MDMontgomery CountyUnclaimed vendor payments
MNRamsey CountyUnclaimed money
RICity of ProvidenceUncashed municipal checks
TXCity of AustinUnclaimed property
TXCity of Corpus ChristiUnclaimed property

How it works

Municipal registers are queried through their public Socrata (SODA) JSON APIs with $limit, $offset, deterministic $order and server-side filters. California publishes four value-range ZIP archives (plus an all-records archive the actor does not download); the actor streams the selected range file to a temporary file with HTTP Range resume, scans the CSV parts line by line, and deletes the file. Iowa publishes one XLSX per fiscal year, read in openpyxl's read-only mode and deleted after the scan. All sources are anonymous: no account, cookie, API key or proxy setup is required.

The California statewide file has no date field. When a date filter is set, California statewide and the other date-less registers are skipped and the status message says so. The default California range is $500 and above (about 163 MB); choosing all value ranges scans four files one at a time, which takes much longer. A property-ID lookup always checks every California range, smallest archive first, and stops once the bucket containing the ID has been scanned, so an ID below $500 is never hidden by the default.

Input

FieldTypeDefaultNotes
modeselectsearchsearch, browse or byPropertyId
stateselectMNALL, CA, IA, MA, MD, MN, RI, TX
jurisdictionselectALLNarrow to one of the 12 sources
ownerNametext—Case-insensitive; word order and commas do not matter
propertyIdtext—Exact property ID, warrant or check number
minAmountUsdnumber0Amount floor; 0 means no floor
maxAmountUsdnumber—Amount ceiling
includeUnknownAmountbooleanfalseKeep records with no amount when an amount filter is active
dateFromtext—Earliest date, YYYY-MM-DD
dateTotext—Latest date, inclusive, YYYY-MM-DD
propertyTypeselectALL10 broad groups over raw NAUPA codes and source categories
propertyTypeContainstext—Raw type substring filter, e.g. Dividend
sortByselectamountDescAmount, date, owner name or source order
maxItemsinteger201–50,000
valueRangeselect500plusCalifornia archive range; ignored for property-ID lookups, which scan all ranges
iaFiscalYearselectlatestIowa fiscal year, all, or a specific year

Examples

Search one name across every state:

{"mode": "search", "state": "ALL", "ownerName": "Smith", "maxItems": 50}

Browse California's largest balances:

{"mode": "browse", "state": "CA", "jurisdiction": "ca_sco", "minAmountUsd": 1000, "maxItems": 100}

Look up a California property ID:

{"mode": "byPropertyId", "state": "CA", "propertyId": "13755891"}

Browse Iowa warrants from FY2026 with dates:

{"mode": "browse", "state": "IA", "iaFiscalYear": "2026", "dateFrom": "2025-07-01", "sortBy": "dateDesc", "maxItems": 100}

Output

Every record contains the fields the source actually discloses. Existing fields are unchanged; the revamp adds richer fields beside them.

FieldDescription
ownerNameOwner/payee name
amountUsdCurrent cash balance or warrant/check amount
reportedDateCheck, warrant or payment date (YYYY-MM-DD)
address, city, postalCodeOwner last-known address, where disclosed
ownerState, ownerCountryOwner state/country, where disclosed (California)
recordIdSource record/check/warrant ID
propertyIdCalifornia property ID
checkNumber, warrantNumberSource check or warrant number
departmentCodeIssuing Iowa department
vendorId, invoiceDate, paymentStatusMontgomery County vendor-payment fields
holderNameEntity holding the funds
holderAddress, holderCity, holderState, holderZipHolder location, where disclosed (California)
propertyTypeRaw source category or NAUPA property-type string
cashReported, sharesReportedReported cash and share counts (California)
securitiesName, cusipSecurity description and CUSIP (California)
numberOfOwners, pendingClaims, paidClaimsOwnership and claim counts (California)
valueRangeCalifornia archive range the row came from
state, jurisdictionTwo-letter state and source name
sourceKey, sourceName, sourceTypeSource traceability
sourceUpdatedAtSource file date (California/Iowa)
sourceUrl, claimUrlPublic dataset page and official claim/search page
recordTypeAlways unclaimedProperty
scrapedAtUTC scrape timestamp

Usage cost

The actor runs on Apify's standard compute pricing. It uses no paid proxy and no external API key, so the only cost is the run's memory and compute time plus Apify's usual dataset/result charges. The default 2 GB memory is sized for the California ZIP streaming path. Start with a small maxItems and the default $500+ range for browsing; a full California all scan is intentionally expensive in time because it reads four multi-hundred-megabyte archives.

FAQ

Does this search every US state? No. It covers the 7 states listed above. Most other states publish their live search only through CAPTCHA- or WAF-gated portals, and this actor does not attempt to bypass those. The official state claim portals remain the right place to file a claim.

Why are some records missing an amount? A few registers publish names without a dollar value. When an amount filter is active, those records are excluded unless includeUnknownAmount is enabled.

Why does a date filter drop California results? The California statewide file has 25 columns but no date field. Date filters therefore skip it rather than guessing a date.

What is the difference between search and byPropertyId? search treats the name as words in any order. byPropertyId performs an exact match against property IDs, warrants and check numbers. Both accept the other field as an additional filter. A California property-ID lookup scans all four value-range archives because an ID lives in only one of them; this can take several minutes.

How fresh is the data? Municipal Socrata registers refresh on their own schedules, California posts new archives weekly (usually Thursday), and Iowa adds fiscal-year files as warrants are cancelled. The actor always reads the currently published source.

Can I get more than 5,000 rows from multiple sources at once? Yes, up to 50,000, but a multi-source run keeps at most 5,000 candidates per source so memory stays bounded. To take a single source deeper, select that jurisdiction alone.

How do I claim money I find? This actor only reports public records. Contact the jurisdiction/holderName office or use the claimUrl on the record.

Are the addresses and names personal data? Yes — they are public-record claimant data. Use them only with a lawful basis, and do not combine them with other datasets to re-identify people.

Notes

  • Public-record data only: owner names and last-known addresses as published by government offices. No SSN, phone, email or claimant identity is collected.
  • No CAPTCHA solving, no login, no credentials, and no proxy configuration are required or supported.
  • California and Iowa archives are streamed and deleted per run; rows are never materialised in memory all at once.
  • Duplicate rows are removed by source + record identity, while legitimate co-owners on one property ID are preserved.
  • Invalid dates and inverted ranges produce a clear status message and a clean zero-record run rather than a crash.

Limitations

  • 7 states, not 50. MissingMoney.com and most state live-search portals are behind CloudFront/WAF/Turnstile blocks. The actor links users to the official portals instead of bypassing them.
  • No date for California statewide records. The source does not publish one.
  • California property-ID lookups are slower. They must check every value-range archive (smallest first) and stop only after the matching bucket, because the default $500+ range would otherwise hide lower balances.
  • The California all-records archive is large. The default $500+ file is about 163 MB compressed; the full all-records ZIP is 3.25 GB, which is why the actor scans the four smaller range files instead.
  • Some municipal datasets change schema. Column names are verified against the live APIs; a renamed column causes that source to be skipped with a status note rather than returning wrong data.
  • Amounts can be stale. A published balance is the holder's last report, not a live claim valuation.