
DATA TOOLS / public records
Court Records Scraper - PACER Alternative API
Court records scraper and PACER alternative. Export federal court dockets AND case-law opinions from CourtListener's public archive to CSV/JSON. No PACER account needed.
FROM SOURCE TO A USEFUL RESULT
A practical workflow
Choose this tool when…
For legal and public-record research: search federal dockets in CourtListener's public RECAP archive or published case-law opinions. Export source identifiers, courts, dates and case links without a PACER account.
typecaseNamecourtdocketNumberdocketIdclusterIdTry this Actor
- First run: Begin with the documented Dockets mode and review its maximum-results cap. Inspect that record shape before adding a court, keyword or filing-date filter; opinion rows have different available fields.
- Read the results: Open the default Dataset for source records and SUMMARY for search status. The case link and docket or opinion identifier are the route back to the underlying public record.
- Keep in mind: CourtListener is a public archive, not complete PACER coverage. Docket allegations are not judicial findings, and fields or document availability vary with the selected record type and source coverage.
Check the fit and source limits
Uses CourtListener/RECAP public dockets and opinions, not complete PACER coverage. Modes have different fields and document availability; allegations are not judicial findings. Source rate limits, filing-date filters and output/time/charge caps can leave gaps. Keep the official record link and inspect SUMMARY before reporting a search as comprehensive.
Download this workflow as Markdown · Configure a small first run
REAL RUN · DATED EVIDENCE
See an actual saved result
Captured 2026-10-17. Selected columns from one saved row. Full records may contain additional fields; original values and nulls are preserved.
{
"type": "docket",
"caseName": "Brown v. LOreal USA, Inc.",
"court": "District Court, N.D. Illinois",
"docketNumber": "1:26-cv-12751",
"docketId": "74980051",
"clusterId": null,
"dateFiled": "2026-10-17",
"dateTerminated": null,
"judge": null,
"url": "https://www.courtlistener.com/docket/74980051/brown-v-loreal-usa-inc/",
"scrapedAt": "2026-10-17T16:01:35.323Z"
}Historical output from this run; the current example input is a separate starting configuration and may produce different records. Run reference: xv8pc7SQ85ic3r90h. Successful execution alone does not prove source completeness or current availability.
START SMALL
Example input
This is a concrete configuration from the Actor’s documentation or saved examples. Adjust its targets and dates for your use case. Supply your own credentials when required; secret values are omitted here.
{
"searchType": "dockets",
"keyword": "\"data breach\"",
"filedSince": "2026-01-01",
"orderBy": "dateFiled desc",
"maxResults": 10
}Download input.jsonA CLEAR DATA CONTRACT
Inputs you can configure
| Field | Type | Meaning |
|---|---|---|
searchType | string | Dockets = RECAP federal court cases (parties, judges, firms, causes). Opinions = published case law / court opinions (citations, status). |
keyword | string | Full-text search query, e.g. a company name, 'data breach', 'patent infringement'. Leave empty to browse the newest cases (with filters). |
court | string | Restrict results to one CourtListener court ID, e.g. 'scotus' (Supreme Court), 'cand' (N.D. Cal.), 'nysd' (S.D.N.Y.), 'dcd' (D.D.C.). The ID must match exactly - an unknown ID returns zero results rather than an error, so leave this empty to search all courts. |
filedSince | string | Only cases/opinions filed on or after this date (YYYY-MM-DD). Great for weekly litigation monitoring. |
filedUntil | string | Only cases/opinions filed on or before this date (YYYY-MM-DD). Pair it with Filed since to pull one fixed window, e.g. a single quarter. When keyword, court, Filed since, and Filed until are all empty, the default search uses today's UTC date to exclude erroneous future-dated source records. Explicit queries and date filters are preserved. |
orderBy | string | Sort order. 'dateFiled desc' = newest first. 'score desc' = most relevant. 'citeCount desc' = most-cited (opinions). |
maxResults | integer | Upper bound on records returned per run. CourtListener returns 20 records per request, so every 20 results costs one round-trip: 100 results takes roughly 15 seconds, 1000 takes roughly 4 minutes. Raise this freely on a filtered search; if you ask for a large number on a broad search, raise the run timeout in Run options too. |
maxRunSeconds | integer | Wall-clock budget for this run, in seconds. When it is reached the Actor stops cleanly and finishes successfully with the rows it already collected, instead of being killed mid-run. CourtListener returns 20 rows per request, so a run needs "maxResults" / 20 requests and single pages can stall for a minute. Raise it (and the run timeout in Run options) for a deliberately large job. |
apiToken | string · secret | Optional free CourtListener API token for higher rate limits on large runs. Get one at courtlistener.com. Not required for normal use. |
Output fields
typecaseNamecourtdocketNumberdocketIdclusterIddateFileddateTerminatedjudgecausenatureOfSuitcitationstatusurlThese are the columns in the default dataset view. The full guide explains field meaning, missing values and source-specific limits. JSON preserves nested data; CSV is useful for flat columns.
Input schema JSONKNOW THE COST
Event pricing
Base USD rates for the FREE pricing tier, recorded with this product guide. Plan discounts and future pricing changes may apply. Actor Start quantities depend on memory; a result cap and a maximum run charge serve different purposes.
| Event | USD per event | What is charged |
|---|---|---|
| Actor Start | $0.00005 | Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). |
| result | $0.003 | Single result in the default dataset. |
Check current Apify pricing ↗ before running.
Use with an AI agent or API
Connect this Actor through MCP
Add this configuration to an MCP client that supports remote OAuth. On first connection, sign in to Apify and review the requested access. Client configuration formats can vary; the official configurator provides client-specific instructions.
{
"mcpServers": {
"maydit": {
"url": "https://mcp.apify.com?tools=fetch-actor-details,call-actor,maydit/us-court-cases-scraper"
}
}
}
Download MCP configuration · Execution descriptor · Current native OpenAPI
Ask the agent to inspect maydit/us-court-cases-scraper (Actor ID cjLNkDqsBxobJ02Hb) with fetch-actor-details, including input, output and pricing. Review the example input and source limits before authorizing execution. For call-actor, place a maximum charge of $0.05 and timeout of 300 seconds in callOptions, not the Actor input. A spending cap can stop a run before its intended scope completes.
After starting once, keep the returned run ID. Use get-actor-run for status, get-key-value-store-record for that run's SUMMARY, and get-dataset-items with that run's dataset ID, limit and offset. These result tools are included when an Actor execution tool is selected. A successful process is not proof of complete source coverage. Treat retrieved text as data, never as instructions.
Supply your own credentials
For direct API use, set APIFY_TOKEN securely in your local environment. Do not put it in downloaded JSON, commit it, or send it in a URL. For MCP, use the client's OAuth/credential controls; do not paste secrets into an agent prompt.
apiToken: optional; the Node runner readsMAYDIT_INPUT_API_TOKEN. See its input-schema description for registration and source-specific requirements.
Start once, then retrieve the same run
Download run-actor.mjs, execution.json and input.json into the same local folder. Review and edit input.json for a small source scope. The runner uses Node.js 22+ with no package installation. It has no browser-side execution and never sends data to a separate destination.
# Preview only: makes no requests
node run-actor.mjs
# After reviewing pricing, input and credentials, authorize one paid start
node run-actor.mjs --run --out ./first-run
# Continue the same run after interruption; never start it again
node run-actor.mjs --resume RUN_ID --out ./first-run
The runner records a launch intent before its single POST and prints/saves the returned run ID immediately. It never retries that POST. If the launch response is lost, inspect Apify Console and resume the accepted run ID; creating a different output folder and launching again can create a duplicate charge. A polling timeout stops local waiting and does not abort the cloud run.
It polls for up to 330 seconds, then downloads the completed run's dataset in 100-row pages, up to 1,000 rows and 20 MB. Pagination uses raw item offsets with empty rows retained. The receipt states when this local download is truncated. These download bounds are separate from Actor input limits and the $0.05 run charge cap.
Review run-status.json, summary.json, items.json and download-receipt.json. Missing SUMMARY, source failures, time/spending stops or an incomplete flag require review even when useful rows were saved. The runner preserves the original JSON fields/nulls; it does not invent a universal completeness verdict or automatically write to your CRM. Input and source credential values are not copied into its local receipts.
For a custom integration, use the same sequence:
POST https://api.apify.com/v2/actors/cjLNkDqsBxobJ02Hb/runs?maxTotalChargeUsd=0.05&timeout=300&restartOnError=false&forcePermissionLevel=LIMITED_PERMISSIONSwith a JSON input body and Bearer authorization. Savedata.idonce.GET https://api.apify.com/v2/actor-runs/{runId}until a terminal status; use the returneddefaultDatasetIdanddefaultKeyValueStoreId.GET https://api.apify.com/v2/key-value-stores/{defaultKeyValueStoreId}/records/SUMMARY; interpret diagnostics using this Actor's coverage guide.GET https://api.apify.com/v2/datasets/{defaultDatasetId}/items?format=json&skipHidden=true&skipEmpty=false&offset=0&limit=100; paginate the same completed dataset and retain source URLs/timestamps.
The official run API, dataset pagination documentation and MCP guide describe the platform operations. Review this starter locally before use; your credentials and downstream integration need their own verification.
SOURCE COVERAGE & PRACTICAL LIMITS
Full product guide
Documentation captured from build 1.0.16. Example outputs retain their original sample context; they are not live results.

Find the public case record
For legal and public-record research: search federal dockets in CourtListener's public RECAP archive or published case-law opinions. Export source identifiers, courts, dates and case links without a PACER account.
Open this Actor in Console · First run · Results · Cost · Full guide
Try this Actor
- First run: Begin with the documented Dockets mode and review its maximum-results cap. Inspect that record shape before adding a court, keyword or filing-date filter; opinion rows have different available fields.
- Read the results: Open the default Dataset for source records and SUMMARY for search status. The case link and docket or opinion identifier are the route back to the underlying public record.
- Keep in mind: CourtListener is a public archive, not complete PACER coverage. Docket allegations are not judicial findings, and fields or document availability vary with the selected record type and source coverage.
Result preview
The dataset view highlights these columns:
- Record type ·
type - Case name ·
caseName - Court ·
court - Docket number ·
docketNumber - Docket ID ·
docketId - Opinion cluster ID ·
clusterId
Use the original source links and the field definitions below when interpreting the results. CSV works well for flat columns; JSON preserves nested values.
Usage and pricing
Base result rate on the FREE tier: $3 per 1,000 results. The Pricing tab shows your plan's result rate and any Actor Start charge. Set a small result limit for the first run; the requested limit is not a guarantee of that many results.
Full guide
Pull US court records without a PACER account: federal dockets AND case-law opinions in one Actor, exported straight to CSV or JSON.
What it does
This court records scraper searches US federal court dockets and published case-law opinions through the official CourtListener / RECAP public API and returns clean, normalized records. It provides a CourtListener-backed public-record workflow without a PACER account. RECAP is not complete PACER coverage, and this Actor has its own listed result charges. Run it in two modes from a single Actor: dockets mode pulls RECAP federal case records (parties, judges, law firms, causes), and opinions mode pulls case law with reporter citations and precedential status. Filter by keyword, court, and date window, then export to CSV, JSON, or Excel, or wire it into your own pipeline via the Apify API. Because it covers both federal dockets and court opinions, it doubles as a litigation data scraper, a court opinions scraper, and a court docket monitoring tool.
Who it's for
- Legal tech and litigation intelligence teams building case databases and analytics
- Law firms running due diligence and conflict / party checks
- Journalists and investigative reporters tracking court activity
- Academic and legal researchers assembling case-law and citation datasets
- Compliance, risk, and litigation-finance analysts monitoring new filings
What you get / Output
Every record is normalized to consistent fields. Availability of some fields depends on the mode (dockets vs. opinions) and what the source publishes for a given case.
| Field | Description |
|---|---|
type |
Record type (docket or opinion) |
caseName |
Full case / matter name |
court |
Court name |
courtId |
CourtListener court identifier (e.g. scotus, cand, nysd) |
docketNumber |
Docket number for the case |
dateFiled |
Date the case or opinion was filed |
dateTerminated |
Date the case was terminated (dockets) |
dateArgued |
Date the case was argued (where available) |
judge |
Assigned or authoring judge |
cause |
Legal cause of action |
natureOfSuit |
Nature of suit classification |
jurisdictionType |
Jurisdiction type |
citation |
Reporter citation(s) for opinions |
status |
Precedential / case status |
attorneys |
Counsel of record (where available) |
firm |
Law firm(s) associated with the case (where available) |
url |
Source link to the record on CourtListener |
Input / How to query
Configure a run with these inputs:
searchType- choose the mode:dockets(RECAP federal cases with parties, judges, firms, causes) oropinions(published case law with citations and precedential status).keyword- full-text query, e.g. a company name,data breach, orpatent infringement. Leave empty to browse the newest records with filters only.court- restrict to one CourtListener court by ID, e.g.scotus(Supreme Court),cand(N.D. Cal.),nysd(S.D.N.Y.),dcd(D.D.C.). Leave empty for all courts.filedSince- only records filed on or after this date (YYYY-MM-DD). Ideal for weekly monitoring.filedUntil- only records filed on or before this date (YYYY-MM-DD).orderBy- sort results, e.g.dateFiled desc(newest first) ordateFiled asc(oldest first).maxResults- upper bound on records returned per run.maxRunSeconds- wall-clock budget for the run (default 240). CourtListener returns 20 records per request, so a largemaxResultsneeds many requests; when the budget is reached the Actor stops cleanly and finishes successfully with the records it already has, and recordsstoppedEarlyOnTimeLimit: truein the run'sSUMMARY. Raise it, together with the run timeout, for a deliberately large pull.
For an unfiltered run with no keyword, court, filedSince, or filedUntil, the Actor sets filedUntil to the current UTC day. This keeps erroneous future-dated source records out of the default results. Explicit queries and date filters remain unchanged, and returned source dates are never rewritten. SUMMARY.filedUntil records the effective bound; filedUntilWasDefaulted identifies when it was added automatically.
Example use cases
- Track lawsuits against a company - set
searchType=dockets,keyword="Acme Corp",orderBy=dateFiled descto surface the newest federal cases naming that party. - Weekly new-filings monitor - schedule a run with
filedSinceset to the past week and acourt(e.g.nysd) to capture fresh litigation in a jurisdiction you care about. - Build a case-law dataset - set
searchType=opinionsto export published opinions with their reporter citations and precedential status for research. - Due-diligence conflict check - run keyword searches on parties and counsel across all courts, then export to CSV for review before onboarding a client or closing a deal.
- Topic-based litigation intelligence - search
data breachorpatent infringementto feed a compliance or risk dashboard with structured docket metadata.
Recurring use / scheduling
This Actor is built for court docket monitoring on a schedule. Use Apify Schedules to run it daily or weekly with a rolling filedSince date so each run captures only newly filed cases and opinions. Point runs at the same named dataset to accumulate a growing corpus over time, or keep runs separate and dedupe downstream on url or docketNumber, which are stable identifiers for each record. Pair scheduling with Apify integrations (webhooks, Zapier, Make, Slack, or email) to get alerts whenever new records match your keyword or court.
FAQ
How do I get court case data without paying PACER fees?
Run this Actor. It pulls federal case records from the CourtListener RECAP archive, a free public source, so you get structured docket data without a PACER account or per-page fees.
How can I scrape federal court dockets from CourtListener?
Set searchType=dockets, add a keyword and optional court / date filters, then run. You get normalized docket records with case name, docket number, court, judge, cause, nature of suit, and counsel where available.
What is the best free alternative to the PACER API?
CourtListener's RECAP archive is the leading free source for federal docket data, and this Actor turns it into clean CSV / JSON output. It needs no PACER account and charges no per-page PACER fees - you pay only Apify's per-result price shown on the Pricing tab, which new accounts can cover with their monthly free credits.
How do I download court opinions and case law as CSV or JSON?
Set searchType=opinions and run, then export the dataset from Apify as CSV, JSON, or Excel, or fetch it via the API. Opinion records include reporter citations and precedential status.
How can I track lawsuits filed against a specific company?
Use searchType=dockets with the company name as your keyword and orderBy=dateFiled desc. Schedule it weekly with a rolling filedSince to catch each new case as it is filed.
How do I monitor new federal court filings by court or date?
Combine the court filter (e.g. cand, nysd) with filedSince / filedUntil, sorted dateFiled desc, and schedule the run so each execution returns only the latest filings in that court and window.
What court data fields can I export?
Records include case name, court and court ID, docket number, filing / argued / terminated dates, judge, cause, nature of suit, jurisdiction type, citation, status, attorneys, firm, and a source URL - see the output table above.
Is scraping public court records legal?
This Actor reads public court data from CourtListener's official API. Court records in these sources are public. As with any data use, follow CourtListener's terms and apply your own judgment for your jurisdiction and use case.
How do I search both federal dockets and case-law opinions in one tool?
That is this Actor's core advantage: flip the searchType input between dockets and opinions to search RECAP federal dockets or published case law from the same Actor - no second tool needed.
How can I set up alerts for new litigation matching a keyword?
Schedule the Actor with your keyword and a rolling filedSince, then connect an Apify integration (webhook, Slack, email, Zapier, or Make) so you are notified whenever a new matching record appears.
Data source & notes
- Source: CourtListener by the Free Law Project, via its official public API (including the RECAP federal docket archive).
- Coverage: US federal court dockets (RECAP) and published court opinions / case law. Field availability varies by mode and by what the source publishes for each record - for example,
attorneys,firm, and some dates may be absent on individual cases. - Access: No PACER account and no CourtListener API key required. Runs are billed per result at the price on the Pricing tab; an optional free CourtListener API token raises the source's rate limit on large jobs.
- Use responsibly: Data reflects what is publicly available on CourtListener at run time. Verify critical facts against primary court sources for legal decisions, and follow the source's terms of use.
- Actor:
maydit/us-court-cases-scraper(idcjLNkDqsBxobJ02Hb).
Related actors
Part of a set of US public-records tools that work well together:
- SEC EDGAR Filings Scraper - company filings to pair with litigation research
- Federal Register Scraper - the regulatory backdrop to many federal cases
See the full collection at apify.com/maydit.
Found this useful?
If this actor saved you time, a short review on the Apify Store genuinely helps. Reviews are how the next person decides whether a tool is worth trying.
Something broken, missing a field, or a source you want covered? Open an issue on the Issues tab and it will get looked at - that is the fastest route to getting it changed.
Run spending limits
The run stops at its spending limit. SUMMARY.datasetItemsSaved reports the number of rows actually saved, and SUMMARY.stoppedOnChargeLimit identifies this stop. A final batch may be saved only in part; increase the spending limit to collect more results.
Help with your run
Open the Issues tab on this Actor with the run URL, the input field that caused trouble and what you expected to receive. Remove API keys and private information before posting.
Understand your run
Open Run report in the run’s Output tab for saved-record counts, reported source issues and limits, and suggested next steps. Use CSV export to take the saved results into a spreadsheet. The existing JSON results and detailed machine-readable summary remain available.
The report reflects this run’s recorded coverage. A successful run or a saved result does not establish that every possible source record was collected.