Client projectAutomationData pipelinesReal estate and public records

A court records scraper that replaced one-case-at-a-time downloads

A team working county court records in the US. October to November 2023, 2 months.

Court records scraper at a glance

Challenge
A team working county court records ran the same foreclosure searches every day and downloaded filings one at a time.
Solution
A Selenium-driven search of the Hamilton County clerk-of-court system, with PDF retrieval, retries and structured output.
Result
A search once repeated by hand, case by case, runs in one pass, and a failed download retries itself.

The court records scraper challenge

Teams that depend on public records pay people to run the same searches every day and download documents one at a time. The team needed the Hamilton County foreclosure search run repeatably, every matching filing retrieved, and the result in a shape it could work with.

What went into the court records scraper

Web scrapingWorkflow automation

  1. Automated search against the county clerk-of-court system, driven through Selenium

  2. Matching PDF retrieval and structured output

  3. Retries on PDF retrieval, so a failed download is re-attempted within the run

More of what we built1
  1. Repeatable runs, so the same search is not re-done by hand

Court records scraper results

The same search stopped being re-done by hand, and a failed download was retried within the run instead of noticed later.

Your project, next

Have a problem in this shape?

Say so in a few sentences. The free plan comes from the person who built this one.

We usually reply within 2 business days with a free plan for what to do first. No call needed.