FindLaw Case Law Scraper
Pricing
from $9.99 / 1,000 results
FindLaw Case Law Scraper
Scrapes FindLaw case-law pages into structured records with case names, citations, court details, dates, summaries, breadcrumbs, and full opinion text. Supports multiple URLs, citation parsing, JSON-LD extraction, and Cloudflare-aware scraping.
Pricing
from $9.99 / 1,000 results
Rating
0.0
(0)
Developer
Jamshaid Arif
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Apify actor that turns caselaw.findlaw.com opinion pages into structured records. One dataset item per page.
Input
{"urls": ["https://caselaw.findlaw.com/court/us-supreme-court/347/483.html","/court/us-supreme-court/410/113.html"],"maxBodyChars": 50000,"requestDelaySecs": 2}
Bare paths are resolved against caselaw.findlaw.com. Article and
attorney-profile pages on findlaw.com work too (they yield the
JSON-LD fields instead of case fields).
What gets parsed
The generic engine pulls title, description, JSON-LD (Article/Attorney/Person: name, phone, rating, address, date). On top of that, case-law pages get properly structured:
| Field | Example |
|---|---|
case_name | BROWN v. BOARD OF EDUCATION |
citation | 347 U.S. 483 |
volume / reporter / first_page | 347 / U.S. / 483 |
year | 1954 |
court | US Supreme Court |
docket_number | 10 |
argued_date | 1952-12-09 (ISO) |
decided_date | 1954-05-17 (ISO) |
case_summary | FindLaw's summary, boilerplate stripped |
breadcrumbs | ["FINDLAW", "CASE LAW", "United States", "US Supreme Court"] |
body_text / body_chars | full opinion text (truncated to maxBodyChars; 0 = unlimited) |
Citation parsing handles digit-bearing reporters (F.3d,
F.Supp.2d, Cal.App.4th), not just U.S.
Non-case pages simply omit the case fields rather than guessing.
Cloudflare
FindLaw is Cloudflare-protected. The actor uses curl_cffi browser TLS
impersonation (rotating chrome/safari/edge/firefox on blocks),
interstitial detection, and backoff — which cleared it in testing at
low volume. For batches keep requestDelaySecs at 2+ and enable Apify
RESIDENTIAL proxy if blocks appear.