Watchlist: monitor any company or person for new court cases in India
A watchlist is the list of companies and people you want CasePrimus.ai to keep an eye on. Add a customer, vendor or partner once, and every new case filed against it in an Indian court or tribunal is found, read by AI, and sent to you as an alert. Nobody on your team has to search court portals by hand.
What the watchlist does
Litigation involving the entities you depend on rarely makes headlines the day it starts. It usually surfaces months later, as a frozen contract, a failed audit or a liability you never saw coming. The watchlist closes that gap. It checks every entity you add against India's court system every day, including nights, weekends and public holidays, so you find out first, not last.
Find out first
New cases reach you the day they appear, not when a partner mentions them.
Hours back for your legal team
AI reads and summarizes each order, so your team reviews conclusions, not raw filings.
Protection that never sleeps
Every hearing, order and new case is checked daily against your whole watchlist.
Add an entity to your watchlist
An entity is a company (BUSINESS) or an individual (PERSON). You can add one from the dashboard or through the API. Both do the same thing.
In the dashboard
- Open Watchlist and add an entity. Choose whether it is a company or a person.
- Enter the name. Use the legal name where you have it, for example “MakeMyTrip India Private Limited”.
- Add identifying details: a registration number and address for companies; father's name and date of birth for people.
- Choose the courts to monitor.
ALLis the recommended default. - Optionally turn on the historical lookup, which finds cases filed before you added the entity.
- Save. Monitoring starts straight away.
Nimbus Freight Pvt Ltd
Cheque bounce case filed (Sec. 138)
Sundar Components Pvt Ltd
Hearing scheduled
Reputation score ↓ from 82 Medium risk
AI summary: new case discovered — score updated automatically.
Illustrative preview — sample data
With the API
Send a POST request to /watchlist/entities with your API key. The response contains the new entity's _id.
BASE="https://api.caseprimus.ai/api/caseprimus/v1" curl -X POST "$BASE/watchlist/entities" \ -H "X-CasePrimus-Api-Key: $CASEPRIMUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "name": "Acme Traders Pvt Ltd", "entityType": "BUSINESS", "monitoredCourts": [ "ALL" ], "fetchHistoricalCases": false }'
const BASE = "https://api.caseprimus.ai/api/caseprimus/v1"; const res = await fetch(BASE + "/watchlist/entities", { method: "POST", headers: { "Content-Type": "application/json", "X-CasePrimus-Api-Key": process.env.CASEPRIMUS_API_KEY, }, body: JSON.stringify({ "name": "Acme Traders Pvt Ltd", "entityType": "BUSINESS", "monitoredCourts": [ "ALL" ], "fetchHistoricalCases": false }), }); const data = await res.json();
import os import requests BASE = "https://api.caseprimus.ai/api/caseprimus/v1" res = requests.request( "POST", BASE + "/watchlist/entities", headers={"X-CasePrimus-Api-Key": os.environ["CASEPRIMUS_API_KEY"]}, json={ "name": "Acme Traders Pvt Ltd", "entityType": "BUSINESS", "monitoredCourts": ["ALL"], "fetchHistoricalCases": False, }, ) data = res.json()
Full field list and responses: Add entity to watchlist.
Courts covered
CasePrimus.ai covers India's court system through the eCourts network and our verification data partners. When you add an entity you pass monitoredCourts: either ALL, or a list of the codes below.
| Code | Court or tribunal |
|---|---|
ALL | Every court and tribunal below. Recommended. If used it must be the only value. |
SC | Supreme Court of India |
HC | High Courts |
DC | District Courts |
CC | Consumer Commissions |
NCLT | National Company Law Tribunal |
NCLAT | National Company Law Appellate Tribunal |
DRT | Debts Recovery Tribunals |
DRAT | Debts Recovery Appellate Tribunals |
GSTAT | Goods and Services Tax Appellate Tribunal |
CESTAT | Customs, Excise and Service Tax Appellate Tribunal |
Use ALL
ALL is the recommended choice.Help us match the right entity
Many Indian companies and people share similar names. The more you tell us, the fewer false matches you will see.
For a company
Give the legal name, and add the registrationNumber and the registered location if you have them. For companies, our AI also searches likely spelling variations of the name, so a case filed under a slightly different spelling is not missed.
For a person
Give the full name, plus fatherName and birthDate (in DD-MM-YYYY format, for example 15-08-1990), and a location. These fields apply to people only and are ignored for companies.
What happens after you add an entity
Immediately
Name variations are generated
For a company, AI creates likely spelling variants of the name to search for. This never delays the response.
Optional
One-time historical lookup
If you turned on fetchHistoricalCases, we look back for cases already filed. It runs in the background and applies to companies only. Results appear on the entity as candidates, and the entity.historical_scan_completed event tells you when it has finished.
Every day
New cases are found
A new case is either added to the watchlist automatically (case.added) or held for your review first (case.pending_review).
Every case
We keep tracking it
New orders and hearing dates, status changes, refreshed AI summaries and changes in risk level all raise an alert. The entity's reputation score updates as its cases change.
Get alerts and webhooks
Alerts appear in your dashboard. If you would rather have the data flow into a system you already run, subscribe a webhook to the events you care about. These are the ones most teams start with.
| Event | What it tells you |
|---|---|
| case.added | A new case was detected and added to the watchlist without needing manual review. |
| case.pending_review | A newly discovered case is waiting for your review before monitoring begins. |
| case.new_order_or_hearing | A new order was uploaded, or a hearing date was added/changed, on a monitored case. |
| case.risk_level_changed | A monitored case's computed risk level moved to a different band (e.g. Medium to High). |
| case.summary_refreshed | A new AI-generated summary was produced for a monitored case after a data refresh. |
| entity.reputation_changed | A watched entity's reputation score moved into a different band. |
| entity.historical_scan_completed | The one-time historical case scan for a newly added entity finished running. |
See all 13 webhook events and their payloads, or read how deliveries are signed and retried.
API reference for the watchlist
Everything above is available over a REST API. Here is the call that adds an entity, and the other watchlist endpoints you will use with it.
/watchlist/entitiesAdds a company or person to your watchlist. Requires the watchlist.write permission. name (2 to 255 characters) and entityType are required; everything else is optional.
Authentication and limits
X-CasePrimus-Api-Key header. Create one from the Developer console. See Authentication and Rate limits & errors.Frequently asked questions
Which courts does CasePrimus.ai monitor?
The Supreme Court, High Courts, District Courts, Consumer Commissions, and tribunals including NCLT, NCLAT, DRT, DRAT, GSTAT and CESTAT. When you add an entity, the recommended value for monitoredCourts is ALL.
How often are cases checked?
Every day. Every hearing, order and new case is checked against your whole watchlist daily, including weekends and Indian public holidays.
Can I monitor an individual, not just a company?
Yes. Set entityType to PERSON. Adding a father's name and date of birth helps avoid matching someone with a similar name.
Will I see cases that were filed before I added the entity?
Yes, if you turn on the historical lookup (fetchHistoricalCases). It is a one-time search that runs in the background and applies to companies only. You will get an entity.historical_scan_completed event when it finishes.
How do I get an API key?
Create one from the Developer console in your CasePrimus.ai dashboard, where you can also manage keys and webhooks. Don't have an account yet? Request a demo and we will set you up.
Is there a limit on API requests?
By default 300 requests per minute per account, counted across all your keys, unless your plan says otherwise. Every response carries rate-limit headers, and going over returns a 429 with a Retry-After header.
You shouldn't be the last to know about your own risk.
Bring a few of the Indian customers, vendors or partners you work with. We'll show you what continuous monitoring surfaces in your first week.
Request a DemoLast updated 14 October 2026