Federal Litigation Monitor — New Filings by Company
New federal court filings matched against your company watchlist, via CourtListener/RECAP's free public mirror of PACER — the kind of monitoring paid tools like Docket Alarm sell. Party role is reported honestly (first/second-named party), not a guessed plaintiff/defendant label.
Federal Litigation Monitor — New Filings by Company returns 13 documented output fields, including matchedCompany, caseName, court, docketNumber and dateFiled. Every field carries a declared type, a written description and an example value. 21 runs are recorded on Apify.
- 13
- Output fields
- 4
- Inputs
- 21
- Runs
- 2026-10-16
- Last run
01 — output
What it returns
Every field the extractor writes to its dataset, with its type, a written description and an example value.
| Field | Type | What it holds | Example |
|---|---|---|---|
| matchedCompany | stringnull | Company that matched. | <matchedCompany> |
| caseName | stringnull | Name of the case. | <caseName> |
| court | stringnull | Court the case was heard in. | <court> |
| docketNumber | stringnull | Docket number for the case. | <docketNumber> |
| dateFiled | stringnull | Date the document was filed. | <dateFiled> |
| dateTerminated | stringnull | Date the record was terminated or closed. | <dateTerminated> |
| party1 | stringnull | First party to the case. | <party1> |
| party2 | stringnull | Second party to the case. | <party2> |
| companyRole | stringnull | Role this person holds at the company. | <companyRole> |
| docketUrl | stringnull | Link to the docket at its source. | <docketUrl> |
| documentCount | integernull | Number of documents found or processed. | 0 |
| status | stringnull | Outcome recorded for this row. | ok |
| verdict | stringnull | The Actor's conclusion for this row, stated in words. | pass |
02 — sample
One record
Assembled from the example values declared on the schema above, not invented at render time.
{
"matchedCompany": "<matchedCompany>",
"caseName": "<caseName>",
"court": "<court>",
"docketNumber": "<docketNumber>",
"dateFiled": "<dateFiled>",
"dateTerminated": "<dateTerminated>",
"party1": "<party1>",
"party2": "<party2>"
}03 — input
What you give it
| Input | Type | Description |
|---|---|---|
| companies | arrayrequired | Company names to watch for new federal court filings, e.g. Apple Inc., Tesla, Inc. Use the full legal name where possible for the best match. |
| daysBack | integeroptional | How many days of new filings to check, up to 5 years. |
| maxCasesPerCompany | integeroptional | How many matching cases to return per company. |
| maxItems | integeroptional | Hard cap on items returned across all companies. You are never charged beyond this. |
04 — run
Run Federal Litigation Monitor on your own input
It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.
05 — questions
Asked before running it
13 of 13 fields described
- What does Federal Litigation Monitor — New Filings by Company return?
- It returns 13 documented output fields: matchedCompany, caseName, court, docketNumber, dateFiled, dateTerminated, party1, party2, companyRole, docketUrl, documentCount and status. Each field declares its type, a description of what it holds, and an example value. The remaining 1 are listed in the output schema below.
- What input does Federal Litigation Monitor — New Filings by Company require?
- companies is required. A further 3 inputs are optional. The full input schema, with types and defaults, is below.
- Does Federal Litigation Monitor — New Filings by Company need an API key or login?
- No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
- How do I run Federal Litigation Monitor — New Filings by Company?
- It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.