Litigation Risk Assessment API

API ID 12623

Search over 500 million U.S. federal court dockets from PACER — district courts, circuit courts, bankruptcy courts, and SCOTUS — in a single API call. Find every case where a company or person appears as a party. Get case name, court, filing date, judge, nature of suit, and cause of action. 98% cheaper than Westlaw CourtAlert at a fraction of the price.

1,557 ms avg response

API Documentation

Endpoints

Request

Returns a paginated list of federal cases where the given entity or person appears as a party (plaintiff, defendant, or other participant).

Endpoint ID: 24423
GET https://zylalabs.com/api/12623/litigation+risk+assessment+api/24423/search+federal+cases+by+party+name
INPUT PARAMETERS

Search federal cases by party name — Endpoint Features

Object Description
name Required Party or entity name. Min 2 characters. Try `"Tesla"`, `"Goldman Sachs"`, `"Elon Musk"`.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

name
API EXAMPLE RESPONSE
JSON
{"count":1000,"page":1,"page_size":20,"has_more":true,"results":[{"id":73362177,"case_name":"McCullough v. Tesla Motors GIGA factory","court_id":"nvd","docket_number":"3:26-cv-00373","date_filed":"2026-05-19","url":"https://www.courtlistener.com/docket/73362177/"},{"id":73359268,"case_name":"Salcedo v. Tesla, Inc.","court_id":"ord","docket_number":"3:26-cv-00989","date_filed":"2026-05-18","nature_of_suit":"355 Motor Vehicle Product Liability","cause_of_action":"28:1332 Diversity-Personal Injury","assigned_judge":"Stacie F. Beckerman","url":"https://www.courtlistener.com/docket/73359268/"},{"id":73352639,"case_name":"Allen v. Tesla, Inc.","court_id":"cand","docket_number":"3:26-cv-04644","date_filed":"2026-05-15","nature_of_suit":"442 Civil Rights: Jobs","cause_of_action":"28:1332 Diversity-(Citizenship)","url":"https://www.courtlistener.com/docket/73352639/"},{"id":73351749,"case_name":"Silas Santiago Alvarenga and Jordan Tesla-Nikkole Alvarenga","court_id":"canb","docket_number":"26-10360","date_filed":"2026-05-15","url":"https://www.courtlistener.com/docket/73351749/"},{"id":73344734,"case_name":"VIERRA v. TESLA FLORIDA, INC.","court_id":"flnd","docket_number":"3:26-cv-03819","date_filed":"2026-05-14","nature_of_suit":"710 Labor: Fair Standards","cause_of_action":"28:1331 Fed. Question","assigned_judge":"Margaret Catharine Rodgers","url":"https://www.courtlistener.com/docket/73344734/"},{"id":73340818,"case_name":"Daniels v. Tesla, Inc.","court_id":"cand","docket_number":"3:26-cv-04485","date_filed":"2026-05-14","url":"https://www.courtlistener.com/docket/73340818/"},{"id":73338736,"case_name":"Harless Jr v. Tesla Motors, Inc.","court_id":"vaed","docket_number":"1:26-cv-01285","date_filed":"2026-05-13","url":"https://www.courtlistener.com/docket/73338736/"},{"id":73329146,"case_name":"CHRISTIAN MICHAEL WHITE and MARY TESLA WHITE","court_id":"mtb","docket_number":"4:26-bk-40053","date_filed":"2026-05-12","url":"https://www.courtlistener.com/docket/73329146/"},{"id":73316240,"case_name":"Black v. Tesla, Inc.","court_id":"cand","docket_number":"3:26-cv-04244","date_filed":"2026-05-08","url":"https://www.courtlistener.com/docket/73316240/"},{"id":73316047,"case_name":"Byars v. Tesla, Inc.","court_id":"txwd","docket_number":"1:26-cv-01211","date_filed":"2026-05-07","nature_of_suit":"442 Civil Rights: Jobs","cause_of_action":"42:2000e Job Discrimination (Employment)","assigned_judge":"David A. Ezra","url":"https://www.courtlistener.com/docket/73316047/"},{"id":73303291,"case_name":"McQuaid v. Tesla, Inc.","court_id":"txwd","docket_number":"1:26-cv-01192","date_filed":"2026-05-05","nature_of_suit":"365 Personal Inj. Prod. Liability","cause_of_action":"28:1331 Fed. Question: Personal Injury","assigned_judge":"Alan D. Albright","url":"https://www.courtlistener.com/docket/73303291/"},{"id":73298574,"case_name":"Kharbanda v. Tesla, Inc.","court_id":"nyed","docket_number":"2:26-cv-02661","date_filed":"2026-05-04","url":"https://www.courtlistener.com/docket/73298574/"},{"id":73267641,"case_name":"Hussain v. Tesla Inc.","court_id":"cand","docket_number":"3:26-cv-03662","date_filed":"2026-04-28","assigned_judge":"Laurel D. Beeler","url":"https://www.courtlistener.com/docket/73267641/"},{"id":73254790,"case_name":"Caro v. Tesla, Inc.","court_id":"cand","docket_number":"3:26-cv-03649","date_filed":"2026-04-28","nature_of_suit":"442 Civil Rights: Jobs","cause_of_action":"28:1332 Diversity-(Citizenship)","url":"https://www.courtlistener.com/docket/73254790/"},{"id":73248610,"case_name":"United States v. 4 Hermes Birkin Bags","court_id":"caed","docket_number":"2:26-cv-01634","date_filed":"2026-04-24","nature_of_suit":"690 Forfeit/Penalty: Other","cause_of_action":"28:1345 Complaint for Forfeiture","assigned_judge":"Jeremy D. Peterson","url":"https://www.courtlistener.com/docket/73248610/"},{"id":73247545,"case_name":"Bracko v. Tesla, Inc.","court_id":"msnd","docket_number":"4:26-cv-00061","date_filed":"2026-04-24","assigned_judge":"Robert P. Chamberlin","url":"https://www.courtlistener.com/docket/73247545/"},{"id":73238813,"case_name":"LAM v. Tesla, Inc.","court_id":"cand","docket_number":"3:26-cv-03477","date_filed":"2026-04-23","url":"https://www.courtlistener.com/docket/73238813/"},{"id":73228033,"case_name":"Sipin v. Tesla Inc.","court_id":"tnmd","docket_number":"3:26-cv-00497","date_filed":"2026-04-22","nature_of_suit":"190 Contract: Other","cause_of_action":"15:2301 Magnuson-Moss Warranty Act","assigned_judge":"Eli Jeremy Richardson","url":"https://www.courtlistener.com/docket/73228033/"},{"id":73208875,"case_name":"Tesla P. Cruz","court_id":"flsb","docket_number":"26-14838","date_filed":"2026-04-17","assigned_judge":"Corali Lopez-Castro","url":"https://www.courtlistener.com/docket/73208875/"},{"id":73192820,"case_name":"TESLA 18, LLC v. Westchester Surplus Lines Insurance Company","court_id":"flsd","docket_number":"2:26-cv-14123","date_filed":"2026-04-15","nature_of_suit":"110 Insurance","cause_of_action":"28:1332 Diversity-Notice of Removal","assigned_judge":"Aileen M. Cannon","url":"https://www.courtlistener.com/docket/73192820/"}]}
Search federal cases by party name — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/12623/litigation+risk+assessment+api/24423/search+federal+cases+by+party+name?name=Tesla' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request

Returns the complete record for a single docket using the CourtListener numeric ID (the `id` field from `/v1/search` results).

Endpoint ID: 24424
GET https://zylalabs.com/api/12623/litigation+risk+assessment+api/24424/get+full+case+details
INPUT PARAMETERS

Free test requests remaining: 3 of 3.

API EXAMPLE RESPONSE
JSON
{"id":73352639,"case_name":"Allen v. Tesla, Inc.","court_id":"cand","docket_number":"3:26-cv-04644","date_filed":"2026-05-15","nature_of_suit":"442 Civil Rights: Jobs","jurisdiction_type":"Diversity","url":"https://www.courtlistener.com/docket/73352639/allen-v-tesla-inc/"}
Get full case details — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/12623/litigation+risk+assessment+api/24424/get+full+case+details&id=Required' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request

Returns the individual filing events within a case — complaints, motions, orders, and rulings — paginated chronologically in reverse order (most recent first).

Endpoint ID: 24425
GET https://zylalabs.com/api/12623/litigation+risk+assessment+api/24425/get+docket+entries+-+filing+events
INPUT PARAMETERS

Get docket entries - filing events — Endpoint Features

Object Description
page Required Page number. Default: `1`.
page_size Optional Results per page. Default: `20`. Max: `100`.
id Required

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

page
page_size
API EXAMPLE RESPONSE
JSON
{"docket_id":73352639,"count":7,"page":1,"page_size":20,"has_more":false,"results":[{"id":464522947,"entry_number":7,"date_filed":"2026-05-19"},{"id":464406433,"date_filed":"2026-05-18"},{"id":464279984,"entry_number":5,"date_filed":"2026-05-15","description":"NOTICE by Tesla, Inc. of Related Cases (Adams, Vincent) (Filed on 5/15/2026) (Entered: 05/15/2026)"},{"id":464278571,"entry_number":2,"date_filed":"2026-05-15","description":"Declaration of Vincent J. Adams in Support of 1 Notice of Removal, filed byTesla, Inc.. (Attachments: # 1 Exhibit A. Package, # 2 Exhibit B. Answer, # 3 Exhibit C. Notice to State Court)(Related document(s) 1 ) (Adams, Vincent) (Filed on 5/15/2026) (Entered: 05/15/2026)"},{"id":464279982,"entry_number":3,"date_filed":"2026-05-15","description":"Certificate of Interested Entities by Tesla, Inc. (Adams, Vincent) (Filed on 5/15/2026) (Entered: 05/15/2026)"},{"id":464279983,"entry_number":4,"date_filed":"2026-05-15","description":"Rule 7.1 Disclosures by Tesla, Inc. (Adams, Vincent) (Filed on 5/15/2026) (Entered: 05/15/2026)"},{"id":464278790,"entry_number":1,"date_filed":"2026-05-15","description":"NOTICE OF REMOVAL from Alameda County Superior Court. Their case number is 26CV174065. (Filing fee $405 receipt number ACANDC-21993056). Filed by Tesla, Inc.. (Attachments: # 1 Civil Cover Sheet)(Adams, Vincent) (Filed on 5/15/2026) (Entered: 05/15/2026)"}]}
Get docket entries - filing events — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/12623/litigation+risk+assessment+api/24425/get+docket+entries+-+filing+events?page=1&page_size=1&id=Required' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Litigation Risk Assessment API simply include your bearer token in the Authorization header.

Headers
Header Description
Authorization Required Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

(Save 2 months with annual billing 🎉)

🚀 Enterprise Plan

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Overview

Federal Litigation Risk Monitor is a real-time REST API that gives developers and data teams instant access to U.S. federal court litigation records from PACER — the official federal court document system — via the CourtListener RECAP Archive. With a single API call you can search over 500 million docket entries spanning every federal district court, appellate court, bankruptcy court, and the U.S. Supreme Court.

Search any company name, executive name, or legal entity and receive back structured, normalized JSON: case name, court, docket number, filing date, assigned judge, nature of suit, cause of action, jurisdiction type, and a direct link to the CourtListener case record. Drill deeper into any case to retrieve its complete docket entry timeline — every complaint, motion, order, and ruling filed in that proceeding.

Who is this for?

Hedge fund analysts and quantitative researchers use this API to surface undisclosed litigation risk in portfolio companies before earnings events or position entries. A securities class action filed in the Southern District of New York or an SEC enforcement action filed in D.D.C. can be detected within hours of filing — without a Westlaw or Bloomberg Law subscription.

Corporate legal teams and in-house counsel use it to monitor ongoing docket activity against their own entity and track competitor litigation exposure across jurisdictions.

M&A due diligence firms and private equity analysts run systematic litigation scans on acquisition targets, checking for pending product liability suits, IP disputes, ERISA class actions, and regulatory enforcement proceedings that may affect deal valuation.

Fintech compliance officers use it to screen counterparties, borrowers, and business partners against active federal proceedings before onboarding.

Investigative journalists and legal researchers use it to track patterns of litigation across industries, courts, and judges — identifying serial plaintiffs, repeat defendants, and case clustering that signals emerging regulatory risk.

Key capabilities:

Search federal cases by party name with optional filters for court jurisdiction, filing date range, and nature-of-suit code. Filter to specific courts such as the Southern District of New York for securities and finance, Northern District of California for technology, District of Delaware for corporate and M&A, D.D.C. for regulatory and government actions, or Southern District of Texas for energy. Filter by nature-of-suit code to isolate securities fraud cases, product liability, ERISA claims, patent disputes, or any of the 80+ federal suit categories.

Retrieve complete docket details for any individual case by its CourtListener ID, including full case name, judge assignment, jurisdiction type, termination date for closed cases, and a canonical URL.

Fetch paginated docket entries for any case — the individual events and filings that make up the case record — in reverse chronological order, with entry numbers, filing dates, and filing descriptions.

Search party name variants to discover all the exact legal names a company uses across federal proceedings before running a full case search — critical for entities that litigate under multiple subsidiary names.

Architecture: Fully stateless. No database, no polling, no persistent storage. Every request proxies CourtListener in real time and returns clean, normalized JSON.

Response format: All endpoints return consistent, paginated JSON with count, page, page_size, has_more, and results fields. All errors return a structured body with standard HTTP status codes.

Pricing comparison: Westlaw CourtAlert and Bloomberg Law docket monitoring cost $15,000 to $25,000 per year per seat. This API delivers the same underlying PACER data — normalized, filterable, and programmable — through a standard REST interface at a fraction of the cost, with no annual contracts.

Data source: All data originates from PACER (Public Access to Court Electronic Records) via the CourtListener RECAP Archive, operated by the non-profit Free Law Project. Data is provided for informational purposes only and does not constitute legal advice.

Litigation Risk Assessment API FAQs

Each endpoint returns structured JSON data. The Search endpoint provides a list of cases with details like case name, court, and filing date. The Get Full Case Details endpoint returns comprehensive case information, while the Get Docket Entries endpoint lists individual filing events within a case.

Key fields include `case_name`, `court_id`, `docket_number`, `date_filed`, `nature_of_suit`, `cause_of_action`, and `url`. These fields provide essential information about each case and its filings.

The response data is organized in a paginated format, including fields like `count`, `page`, `page_size`, `has_more`, and `results`. Each result contains detailed information about cases or docket entries, making it easy to navigate.

Users can customize requests using parameters such as `party_name`, `court jurisdiction`, `filing date range`, and `nature-of-suit code`. These parameters help filter results to meet specific needs, such as searching for cases in a particular court.

The data originates from PACER (Public Access to Court Electronic Records) via the CourtListener RECAP Archive, ensuring access to official federal court records. This source is maintained by the non-profit Free Law Project.

Typical use cases include monitoring litigation risks for hedge funds, conducting due diligence for M&A, tracking competitor litigation, and screening business partners for active federal proceedings. This data helps inform strategic decisions.

Users can analyze the returned data to identify litigation trends, assess risks, and monitor ongoing cases. For example, filtering by nature-of-suit can help pinpoint specific legal issues relevant to a business or investment strategy.

Data accuracy is maintained through regular updates from PACER and the CourtListener Archive. The API provides real-time access to court records, ensuring users receive the most current and reliable information available.

General FAQs

To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.

You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.

The free trial lasts for 7 days and allows you to make up to 50 API requests.

No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.

Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

You can monitor your API usage through the response headers included with every request:

x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.

Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs