# Case Monitoring API

Source: https://caseprimus.ai/docs/case-monitoring-api

## API To Monitor Individual Court Cases And Read Their Orders Across India

The **Case Monitoring API** puts individual court cases under watch. Add a case by its identifier, or accept one found for a party, and CasePrimus.ai follows it through the court: every order on a monitored case is downloaded and read automatically, summarized by AI, and raises an alert when something changes.

Search the cases you monitor, read any one with its details, court record, orders and AI case summary, and stop monitoring a case when you no longer need it.

> **Built on certified infrastructure.** CasePrimus.ai is operated by Pegadroid IQ Solutions Private Limited, the legal entity behind Attestr's products, which holds ISO/IEC 27001:2022 certification. Data is hosted in India (AWS Mumbai, ap-south-1) and every connection is encrypted in transit.

## Key capabilities

- **Add a case by its identifier.** Send the court type and the CNR or case number to `POST /watchlist/cases`. The case is checked with the court as it is added.
- **Reuse an earlier lookup.** Send the result of a Live Case Lookup as `snapshot` to save a repeat lookup.
- **Never added twice.** If you already track the same case, it is linked instead of duplicated. `linkedExisting` is `true` and you get the case's current status.
- **Every order read for you.** Every order on a monitored case is downloaded and read automatically, and each one gets a summary.
- **An AI case summary and a risk level.** Each case carries an AI summary, a risk level and the reasoning behind it.
- **Search what you monitor.** Search the cases you can see with filters, sorting and paging. Sort on `riskSeverityRank` to put the most severe first.
- **Confirm a disposed case.** If the court already shows a case as disposed, the request is refused with the disposal details unless you send `confirmDisposed`.
- **Stop any time.** Stopping archives the case rather than erasing it, and frees one of your monitored-case slots.

## How it works

1. **Add a case.** Post the case's identifier to `POST /watchlist/cases`, or accept a case found for a party.
2. **We follow it through the court.** New hearings, orders and status changes are picked up every day, and every new order is read and summarized.
3. **Act on what changed.** Read the case with `GET /watchlist/cases/{id}`, or have changes pushed to your endpoint by webhook.

## API definition

### Add a case to monitoring

Adds a case to the watchlist, either manually or by confirming a match from a case search (pass its result as snapshot). If the same case is already tracked, identified by its case identifier, the entity is linked to the existing record instead of creating a duplicate, and the response has linkedExisting true. On accounts where the CasePrimus team reviews new cases, a newly created case starts as PENDING_BACKOFFICE_REVIEW instead of ACTIVE until it is reviewed; so does a case whose identifier the court cannot confirm (backOfficeReviewReason says why). A case the court already shows as disposed is added only when you send confirmDisposed true; otherwise the call fails with code 60430 and the disposal details, and nothing is added. A new case counts against your monitored-case limit (403, code 60417); linking to an existing case does not. Requires case.write.

**Request URL**

`POST https://api.caseprimus.ai/api/caseprimus/v1/watchlist/cases`

**Request headers**

| Type | Name | Value | Optional |
| --- | --- | --- | --- |
| String | `Content-Type` | `application/json` | Required |
| String | `X-CasePrimus-Api-Key` | Your API key | Required |

**Input parameters**

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `caseIdentifier` | object | Required | Identifies one case. Which other fields you send depends on courtType - send exactly one of the alternatives listed for it. DC: cnr. SC: cnr, or caseType + registrationNumber, or diaryNumber. HC: cnr, or establishmentCode + caseType + registrationNumber. CC (consumer commission): registrationNumber (the e-Jagriti case number) only. NCLT, NCLAT, GSTAT: establishmentCode + filingNumber, or establishmentCode + caseType + registrationNumber. DRT, DRAT: establishmentCode + diaryNumber, or establishmentCode + caseType + registrationNumber. CESTAT: establishmentCode + diaryNumber, or establishmentCode + caseType + registrationNumber. NGT: establishmentCode (PB, EZ, CZ, WZ or SZ) + either caseType (OA, RA, MA, AP, EA, IA or TA) + registrationNumber (n/yyyy), or diaryNumber (the 12-digit diary number / year). SAT: establishmentCode (MUM) + either caseType (SEBI, IRDAI or PFRDA) + registrationNumber (the Appeal No., n/yyyy, at most 4 digits before the year), or filingNumber (the AL No. - Appeal Lodging number, n/yyyy). ITAT: establishmentCode (the bench's city in capitals, for example DELHI, MUMBAI or BANGALORE; Cochin is ERNAKULAM and Visakhapatnam is VISHAKHAPATNAM) + caseType (ITA, CO, ITSSA, ITTPA, ITITA, WTA, BMA, GTA, SA or MA) + registrationNumber (the Appeal No. and filing year, n/yyyy, at most 5 digits before the year); all three are required. APTEL: establishmentCode (DEL) + either caseType (APL, OP, EP, RP or CP) + registrationNumber (the Case No., n/yyyy), or diaryNumber (the DFR No., n/yyyy). The DFR number is the tribunal's diary number and every case has one from the day it is filed; a Case No. is allotted only on registration, so a recently filed case may be reachable by its DFR number alone. Note that the year means different things on the two: with a Case No. it is the year the case was registered, with a DFR No. the year it was filed, and for the same case these can differ.  |
| `caseIdentifier.courtType` | enum | Required | One of: DC, SC, HC, CC, NCLT, NCLAT, GSTAT, DRT, DRAT, CESTAT, NGT, SAT, ITAT, APTEL |
| `caseIdentifier.cnr` | string | Optional | DC, SC, HC only. |
| `caseIdentifier.registrationNumber` | string | Optional | Format depends on courtType - see the description above. Usually number/year (for example 87/2018; at most 4 digits for SAT, 5 for ITAT); for HC the number/year is sent with caseType, and for CC it is the whole e-Jagriti case number. |
| `caseIdentifier.filingNumber` | string | Optional | NCLT/NCLAT/GSTAT only, and SAT (the AL No. - Appeal Lodging number - n/yyyy). |
| `caseIdentifier.diaryNumber` | string | Optional | SC, DRT, DRAT, CESTAT, NGT (the 12-digit diary number / year, e.g. 070111601768/2026) and APTEL (the DFR No., n/yyyy). |
| `caseIdentifier.establishmentCode` | string | Optional | Bench/tribunal code - required for HC (when not using cnr) and every tribunal court type. NGT: PB, EZ, CZ, WZ or SZ. SAT: MUM. APTEL: DEL. ITAT: the bench's city in capitals (DELHI, MUMBAI, BANGALORE ...; Cochin is ERNAKULAM, Visakhapatnam is VISHAKHAPATNAM). |
| `caseIdentifier.caseType` | string | Optional | Required alongside registrationNumber for most court types. The valid values depend on courtType, for example NGT: OA, RA, MA, AP, EA, IA, TA; SAT: SEBI, IRDAI, PFRDA; APTEL: APL, OP, EP, RP, CP; ITAT: ITA, CO, ITSSA, ITTPA, ITITA, WTA, BMA, GTA, SA, MA. |
| `watchlistEntityId` | string or null | Optional | The company to link the case to. Must belong to your account (else 400, code 60400). Omit for an unlinked case. |
| `snapshot` | object (free-form) or null | Optional | The whole result of POST /case-lookup - carried into the new case for context (court, parties, risk level,...). Omit for a fully manual add. It is stored as sent and returned by the case endpoints in the normalised form described on WatchlistCase.snapshot. |
| `sharedWith` | array of object or null | Optional |  |
| `sharedWith[].type` | enum | Required | One of: team, user |
| `sharedWith[].id` | string | Required | A team ID when type is 'team', a user ID otherwise. |
| `confirmDisposed` | boolean | Optional | Send true to add a case the court already shows as disposed (it has a decision date or a nature of disposal). Without it such a case is refused with 400, code 60430, whose details carry caseSummary, natureOfDisposal and decisionDate, and nothing is added; resend the same request with true to proceed. |

**Sample request**

```bash
BASE="https://api.caseprimus.ai/api/caseprimus/v1"

curl -X POST "$BASE/watchlist/cases" \
  -H "X-CasePrimus-Api-Key: $CASEPRIMUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "caseIdentifier": {
      "courtType": "DC",
      "cnr": "HRFB010051662020"
    },
    "watchlistEntityId": "CPWLE0exampledemo0001",
    "confirmDisposed": true
  }'
```

**Responses**

- `200`: Case added (or linked to an existing tracked case).
- `400`: Malformed input (60001), the referenced watchlistEntityId does not exist (60400), or the case already appears to be disposed and confirmDisposed was not sent (60430, with details).
- `403`: Caller lacks the case.write permission (60002), or the account's monitored-case limit has been reached (60417).

**Response fields (HTTP 200)**

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `_id` | string |  | The new case's id (CPWLC0...), or the existing case's id when linkedExisting is true. |
| `status` | enum |  | A new case's starting status. When linkedExisting is true: the existing case's current status. One of: ACTIVE, PENDING_BACKOFFICE_REVIEW |
| `backOfficeReviewReason` | string or null |  | Why a new case is PENDING_BACKOFFICE_REVIEW because of its own identifier or add-time live lookup (for example COURT_TYPE_UNRESOLVED, CNR_LOOKS_INVALID, LOOKUP_FAILED); null when the case is ACTIVE, or pending only because the CasePrimus team reviews every new case for your account. Absent when linkedExisting is true. |
| `linkedExisting` | boolean |  | true if this case was already tracked and this call just linked watchlistEntityId to it (no new case, no case quota used). |

**Example response (200)**

```json
{
  "_id": "CPWLC0exampledemo0001",
  "status": "ACTIVE",
  "backOfficeReviewReason": null,
  "linkedExisting": false
}
```

### Search monitored cases

Searches the cases you can see: those in your account and those shared with you. Archived cases are not returned unless your $filter names a status; cases still waiting for the CasePrimus team's review (PENDING_BACKOFFICE_REVIEW) are. It uses the same search envelope as the other search endpoints: $filter for exact matches (a value can also be an operator object such as {"$in": [...]}), $like for case-insensitive substring matches, $sort to order the results (newest first by default; sorting on riskSeverityRank puts the most severe risk first), and $skip with $limit (default 10, up to 1000) to page through them. $filter takes only field = value matches, the operators $eq, $ne, $in, $nin, $gt, $gte, $lt, $lte and $exists, and $or, $and and $nor combining such filters (up to 4 levels deep); any other operator (for example $expr, $where or $regex) or a field the API does not expose is refused with a 400 error. Filter by watchlistEntityIds to list the cases monitored for one entity. Requires case.read.

**Request URL**

`POST https://api.caseprimus.ai/api/caseprimus/v1/watchlist/cases/search`

**Request headers**

| Type | Name | Value | Optional |
| --- | --- | --- | --- |
| String | `Content-Type` | `application/json` | Required |
| String | `X-CasePrimus-Api-Key` | Your API key | Required |

**Input parameters**

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `$filter` | object (free-form) | Optional | Field filters, e.g. {"status": "ACTIVE"}. A field is compared with a value (string, number, boolean or null, an exact match) or with an operator object of $eq, $ne, $in, $nin, $gt, $gte, $lt, $lte or $exists, e.g. {"status": {"$in": ["ACTIVE", "PAUSED"]}} or {"meta.caseId": {"$exists": true}}; this holds on every search. $or, $and and $nor may combine such filters, at most 4 levels deep. Anything else, and a field that is internal to CasePrimus, is rejected with 400 (60001). An empty object filters nothing. |
| `$like` | object (free-form) | Optional | Case-insensitive substring filters, e.g. {"name": "trip"}. An empty string for a field is ignored. A field that is internal to CasePrimus, or a name starting with $, is rejected with 400 (60001). |
| `$skip` | integer | Optional | minimum 0 |
| `$sort` | object (free-form) | Optional | Field to +1/-1 (ascending/descending), e.g. {"created": -1}. A field that is internal to CasePrimus, or a name starting with $, is rejected with 400 (60001). |
| `$limit` | integer | Optional | How many records to return. At most 100 on the task, note, document and activity searches; the watchlist entity, case and candidate searches accept up to 1000. 0 to 1000 |
| `$derived` | object | Optional | FILTERS A `$filter` CANNOT EXPRESS, on the case search only. Everything in `$filter` is matched against a stored field; these three are not stored in a form that can be matched.  The filing date and the next hearing are kept exactly as the court wrote them - one record states `03-11-2026` and the promoted candidate's snapshot of the SAME case states `2026-11-03`, and a next hearing arrives as `07-December-2026` - so a range over them is a range over several formats at once. The case score is not stored at all: it is computed per read (see `caseScore` on the case).  A request carrying any of these is answered by deriving the matching set server-side before paging it, so `recordsFiltered` still counts what the filter matched. It covers the first 5,000 cases the rest of the query matches; `derivedCapReached: true` comes back when that ceiling was reached. |
| `$derived.filedFrom` | string | Optional | Filed on or after this date. A case whose record states no filing date is outside the range rather than inside it. |
| `$derived.filedTo` | string | Optional |  |
| `$derived.hearingFrom` | string | Optional | Next hearing on or after this date - the date the COURT states, which on a record it has not updated since the hearing is one that has passed. |
| `$derived.hearingTo` | string | Optional |  |
| `$derived.scoreMin` | integer | Optional | `caseScore.value`, 0-1000 where higher is better. A case with no score is outside any range given. 0 to 1000 |
| `$derived.scoreMax` | integer | Optional | 0 to 1000 |

**Sample request**

```bash
BASE="https://api.caseprimus.ai/api/caseprimus/v1"

curl -X POST "$BASE/watchlist/cases/search" \
  -H "X-CasePrimus-Api-Key: $CASEPRIMUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "$filter": {
      "watchlistEntityIds": "CPWLE0exampledemo0001"
    },
    "$skip": 0,
    "$limit": 10
  }'
```

**Responses**

- `200`: Matching cases.
- `400`: Malformed search envelope (60001), for example an unknown key or a non-numeric $limit, or a $filter / $like / $sort outside the accepted form - an operator other than the supported ones, or a field the API does not expose (60001).
- `403`: Caller lacks the case.read permission.

**Response fields (HTTP 200)**

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `recordsFiltered` | integer |  | Total matching records, ignoring $skip and $limit. |
| `records` | array of object |  | The matching cases on this page. |
| `records[]._id` | string |  | The case's id. |
| `records[].number` | string |  | Human-readable case number, a string in the form NNNN-NNNNNN-NNNN. |
| `records[].accountId` | string |  | Your account's id. |
| `records[].watchlistEntityIds` | array of string |  | Every watchlist entity this case is linked to - the same real-world case can be tracked against more than one company. |
| `records[].caseIdentifier` | object |  | Identifies one case. Which other fields you send depends on courtType - send exactly one of the alternatives listed for it. DC: cnr. SC: cnr, or caseType + registrationNumber, or diaryNumber. HC: cnr, or establishmentCode + caseType + registrationNumber. CC (consumer commission): registrationNumber (the e-Jagriti case number) only. NCLT, NCLAT, GSTAT: establishmentCode + filingNumber, or establishmentCode + caseType + registrationNumber. DRT, DRAT: establishmentCode + diaryNumber, or establishmentCode + caseType + registrationNumber. CESTAT: establishmentCode + diaryNumber, or establishmentCode + caseType + registrationNumber. NGT: establishmentCode (PB, EZ, CZ, WZ or SZ) + either caseType (OA, RA, MA, AP, EA, IA or TA) + registrationNumber (n/yyyy), or diaryNumber (the 12-digit diary number / year). SAT: establishmentCode (MUM) + either caseType (SEBI, IRDAI or PFRDA) + registrationNumber (the Appeal No., n/yyyy, at most 4 digits before the year), or filingNumber (the AL No. - Appeal Lodging number, n/yyyy). ITAT: establishmentCode (the bench's city in capitals, for example DELHI, MUMBAI or BANGALORE; Cochin is ERNAKULAM and Visakhapatnam is VISHAKHAPATNAM) + caseType (ITA, CO, ITSSA, ITTPA, ITITA, WTA, BMA, GTA, SA or MA) + registrationNumber (the Appeal No. and filing year, n/yyyy, at most 5 digits before the year); all three are required. APTEL: establishmentCode (DEL) + either caseType (APL, OP, EP, RP or CP) + registrationNumber (the Case No., n/yyyy), or diaryNumber (the DFR No., n/yyyy). The DFR number is the tribunal's diary number and every case has one from the day it is filed; a Case No. is allotted only on registration, so a recently filed case may be reachable by its DFR number alone. Note that the year means different things on the two: with a Case No. it is the year the case was registered, with a DFR No. the year it was filed, and for the same case these can differ.  |
| `records[].snapshot` | object or null |  | The discovery record the case was added from, in CasePrimus's normalised form (null for a case added by identifier alone). Only the fields below are returned: provider references, provider documents and raw party structures are never included. Fields without a value are null. |
| `records[].riskLevel` | enum |  | One of: VERY_HIGH, HIGH, MODERATE, LOW, UNCLASSIFIED |
| `records[].caseScore` | object or null |  | THE SCORE TO SHOW ON A ROW, on every case a search returns. 0-1000 where HIGHER IS BETTER, the same scale and direction as a company's `reputationScore` - and the same object `analysis.risk.caseScore` carries on the single case, computed the same way, so a list and a case page cannot print different numbers for one case.  It cannot contradict `riskLevel`: the level fixes the band (VERY_HIGH 0-199, HIGH 200-399, MODERATE 400-599, LOW 600-799, MINIMAL 800-1000) and the indicative scoring decides only the position inside it. Null where the level is UNCLASSIFIED - nothing has been analysed yet, and a case nobody has looked at must not read as the cleanest on the list. Filter on it with `$derived.scoreMin` / `$derived.scoreMax`. |
| `records[].status` | enum |  | One of: ACTIVE, PENDING_BACKOFFICE_REVIEW, REJECTED, ARCHIVED |
| `records[].reviewedAt` | integer (int64) or null |  | Epoch ms the CasePrimus team reviewed the case; null until then. |
| `records[].backOfficeReviewReason` | string or null |  | Why the case went to the CasePrimus team for review because of its identifier or add-time live lookup (for example COURT_TYPE_UNRESOLVED, CNR_LOOKS_INVALID, LOOKUP_FAILED); null otherwise. |
| `records[].disposed` | boolean |  | true once the case is marked disposed. A disposed case stays ACTIVE and keeps using a case-quota slot until it is archived. |
| `records[].disposedAt` | integer (int64) or null |  | Epoch ms the case was marked disposed. |
| `records[].sharedWith` | array of object |  | Teams or users the case is shared with. |
| `records[].assignedTo` | string or null |  | User id of the person who owns following up on the case; null when unassigned. |
| `records[].summarizationStatus` | enum or null |  | State of the AI analysis (case summary, risk level and per-order summaries). null until the analysis has started. One of: PENDING, COMPLETE, FAILED,  |
| `records[].summarizationFailureReason` | string or null |  | Set when summarizationStatus is FAILED, for example NO_COURT_TYPE, INVALID_CNR, CAPTCHA_REQUIRED or FETCH_FAILED; null otherwise. |
| `records[].summarizationUpdated` | integer (int64) or null |  | Epoch ms the analysis last ran or changed state. |
| `records[].fullDetails` | object or null |  | The case details last fetched live from the court (same fields as the POST /case-lookup result, without searchId and latestSummary): caseType, filingNumber/Date/Year, registrationNumber/Date, cnrNumber, state, district, courtName, courtNumberAndJudge, courtEstablishment, first/next/previousHearingDate, caseStage, decisionDate, natureOfDisposal, caseStatus, petitioners/respondents (with counsel), acts, caseHistory, orders, linkedCases, transfers and more. null until a fetch has succeeded. |
| `records[].fullDetailsCourtType` | string or null |  | The court type the details were fetched for (DC, HC, SC, ...). |
| `records[].lastFetchedAt` | integer (int64) or null |  | Epoch ms of the last successful live fetch of the case, even if nothing changed; null if none has succeeded. |
| `records[].caseSummary` | string or null |  | AI-generated summary of the case; null until the analysis completes. |
| `records[].riskJustification` | string or null |  | AI-generated reasoning behind riskLevel; null until the analysis completes. |
| `records[].caseLabels` | array of string or null |  | What this case is ABOUT, from the same analysis call that wrote `caseSummary`. The same catalogue the litigation report uses, so the two products never disagree about what a case is. One or more ids, or `PROCEDURAL_ONLY` (neither the orders nor the court record reveal the subject matter) or `OTHERS` (the subject matter is clear but we have no id for it). Null until the analysis completes. |
| `records[].caseLabelBasis` | enum or null |  | Which evidence the labels came from. `ORDER` - the case's own orders say so. `RECORD` - the case has no readable order and the label comes from the court's index entry, which is weaker and never reads HIGH. `BOTH` - they agree. `NEITHER` - `PROCEDURAL_ONLY`. One of: ORDER, RECORD, BOTH, NEITHER |
| `records[].caseLabelConfidence` | enum or null |  | How good the evidence is, not how strongly we feel. A label alleging conduct requires an order to describe that conduct, never a statute name. One of: HIGH, MEDIUM, LOW |
| `records[].caseLabelEvidence` | string or null |  | The words that decided the labels, quoted. Published so a label can be checked rather than taken on trust. |
| `records[].casePartySide` | enum or null |  | Which side the monitored entity is on. The same outcome words mean opposite things depending on it. One of: PETITIONER, RESPONDENT, BOTH, UNCLEAR |
| `records[].caseSuggestedLabel` | object or null |  | Set only where `caseLabels` is `OTHERS`: our own proposal for what this kind of case should be called, because a case we cannot categorise is still a case you need described. |
| `records[].orderSummaries` | array of object |  | One AI summary per order (up to 60), reused across refreshes while the order is unchanged. |
| `records[].analysis` | object |  | The fields a single case carries beyond the list, shared by the report's case detail and the watchlist's case analysis. |
| `records[].lawfulBasisNoticeVersion` | string or null |  | Version of the lawful-basis notice in force when the case was added. |
| `records[].created` | integer (int64) |  | When the case was added, in milliseconds since the Unix epoch. |
| `records[].createdBy` | string or null |  |  |
| `records[].updated` | integer (int64) or null |  | When the case was last updated, in milliseconds since the Unix epoch. |
| `records[].updatedBy` | string or null |  |  |

**Example response (200)**

```json
{
  "recordsFiltered": 1,
  "records": [
    {
      "_id": "CPWLC0exampledemo0001",
      "number": "4821-310045-8001",
      "accountId": "CPA0exampledemo0001",
      "watchlistEntityIds": [
        "CPWLE0exampledemo0001"
      ],
      "caseIdentifier": {
        "cnr": "HRFB010051662020",
        "courtType": "DC"
      },
      "snapshot": {
        "cnrNumber": "HRFB010051662020",
        "caseNumber": "135/2020",
        "filingNumber": "1821/2020",
        "registrationNumber": "135/2020",
        "court": "District and Sessions Courts, Faridabad",
        "courtType": "District Court",
        "state": "Haryana",
        "district": "Faridabad",
        "caseType": "APP",
        "caseTypeName": "Application",
        "caseNature": "CIVIL",
        "caseTypeLabel": "Application",
        "caseStatus": "Disposed",
        "filingYear": 2020,
        "filingDate": "2020-07-08",
        "registrationDate": "2020-07-09",
        "nextHearingDate": null,
        "decisionDate": "2020-10-27",
        "natureOfDisposal": "Uncontested - DISMISSED AS WITHDRAWN",
        "bench": null,
        "petitioner": "Acme Traders Pvt Ltd",
        "respondent": "Jane Doe Realty Ltd",
        "orders": [
          {
            "number": 1,
            "orderDate": "2020-07-09",
            "judge": null,
            "documentUrl": "https://files.example.com/public/caseprimus/orders/file?token=EXAMPLE_TOKEN_1"
          },
          {
            "number": 2,
            "orderDate": "2020-08-06",
            "judge": null,
            "documentUrl": "https://files.example.com/public/caseprimus/orders/file?token=EXAMPLE_TOKEN_2"
          },
          {
            "number": 3,
            "orderDate": "2020-08-18",
            "judge": null,
            "documentUrl": "https://files.example.com/public/caseprimus/orders/file?token=EXAMPLE_TOKEN_3"
          }
        ]
      },
      "riskLevel": "MODERATE",
      "status": "ACTIVE",
      "reviewedAt": null,
      "backOfficeReviewReason": null,
      "disposed": false,
      "disposedAt": null,
      "sharedWith": [],
      "assignedTo": null,
      "summarizationStatus": "COMPLETE",
      "fullDetails": {
        "caseType": "APP - APPLICATION",
        "filingNumber": "1821/2020",
        "filingDate": "08-07-2020",
        "filingYear": "2020",
        "registrationNumber": "135/2020",
        "registrationDate": "09-07-2020",
        "cnrNumber": "HRFB010051662020",
        "state": "Haryana",
        "district": "Faridabad",
        "courtName": "District and Sessions Courts, Faridabad",
        "courtNumberAndJudge": "1-District and Sessions Judge",
        "courtEstablishment": "District and Sessions Court, Faridabad",
        "firstHearingDate": "09-July-2020",
        "nextHearingDate": null,
        "previousHearingDate": null,
        "caseStage": null,
        "decisionDate": "27-October-2020",
        "natureOfDisposal": "Uncontested - DISMISSED AS WITHDRAWN",
        "caseStatus": "Case Disposed",
        "coram": null,
        "judicial": null,
        "causeListName": null,
        "bench": null,
        "shortOrder": null,
        "petitioners": [
          {
            "petitionerName": "Acme Traders Pvt Ltd",
            "petitionerCounsel": "Advocate - Advocate A"
          }
        ],
        "petitionersText": "1) Acme Traders Pvt Ltd\n                 Advocate - Advocate A",
        "respondents": [
          {
            "respondentName": "Jane Doe Realty Ltd",
            "respondentCounsel": null
          }
        ],
        "respondentsText": "1) Jane Doe Realty Ltd",
        "acts": [
          {
            "act": "CODE OF CIVIL PROCEDURE",
            "sections": "APP"
          }
        ],
        "interlocutoryApplicationDetails": null,
        "caseHistory": [
          {
            "reg": "135/2020",
            "causeListType": null,
            "judge": "District and Sessions Judge",
            "purpose": "Appearance",
            "nextHearingDate": "06-08-2020",
            "businessDate": "09-07-2020"
          },
          {
            "reg": "135/2020",
            "causeListType": null,
            "judge": "District and Sessions Judge",
            "purpose": "Appearance",
            "nextHearingDate": "18-08-2020",
            "businessDate": "06-08-2020"
          },
          {
            "reg": "135/2020",
            "causeListType": null,
            "judge": "District and Sessions Judge",
            "purpose": "Appearance",
            "nextHearingDate": "16-09-2020",
            "businessDate": "18-08-2020"
          }
        ],
        "orders": [
          {
            "number": "1",
            "orderDate": "09-07-2020",
            "judge": null,
            "attachment": "AVAILABLE",
            "orderType": null
          },
          {
            "number": "2",
            "orderDate": "06-08-2020",
            "judge": null,
            "attachment": "AVAILABLE",
            "orderType": null
          },
          {
            "number": "3",
            "orderDate": "18-08-2020",
            "judge": null,
            "attachment": "AVAILABLE",
            "orderType": null
          }
        ],
        "objections": null,
        "category": null,
        "subCategory": null,
        "subSubCategory": null,
        "fir": null,
        "earlierCourts": null,
        "documents": null,
        "linkedCases": null,
        "transfers": []
      },
      "fullDetailsCourtType": "DC",
      "lastFetchedAt": 1757000012000,
      "caseSummary": "Application filed by Acme Traders Pvt Ltd in the District and Sessions Court, Faridabad; it was withdrawn and dismissed in October 2020.",
      "riskJustification": "The case is disposed and the application was withdrawn without any adverse finding, so the exposure is limited; it is kept at moderate because the dispute with the respondent is not otherwise resolved on the record.",
      "orderSummaries": [
        {
          "orderKey": "8acd04f57027fe8c8a318e95d0ca74a7",
          "orderNumber": "1",
          "orderDate": "09-07-2020",
          "judge": null,
          "orderType": null,
          "attachment": "AVAILABLE",
          "status": "COMPLETE",
          "summary": "Appearance recorded for the applicant; the matter was listed for the next date.",
          "detectedLanguage": "English",
          "error": null,
          "errorClass": null,
          "attempts": 1,
          "computedAt": 1757000050000
        },
        {
          "orderKey": "af2538a37a645f61a09c177924d3ecb5",
          "orderNumber": "2",
          "orderDate": "06-08-2020",
          "judge": null,
          "orderType": null,
          "attachment": "AVAILABLE",
          "status": "COMPLETE",
          "summary": "Appearance recorded again; the court adjourned the matter to the next listed date.",
          "detectedLanguage": "English",
          "error": null,
          "errorClass": null,
          "attempts": 1,
          "computedAt": 1757000054000
        },
        {
          "orderKey": "6e96db2dfa0d699908f8d5fed84af3ae",
          "orderNumber": "3",
          "orderDate": "18-08-2020",
          "judge": null,
          "orderType": null,
          "attachment": "AVAILABLE",
          "status": "COMPLETE",
          "summary": "Applicant withdrew the application and the court dismissed it as withdrawn.",
          "detectedLanguage": "English",
          "error": null,
          "errorClass": null,
          "attempts": 1,
          "computedAt": 1757000058000
        }
      ],
      "lawfulBasisNoticeVersion": "v1",
      "created": 1757000000000,
      "createdBy": "CPU0exampledemo0001",
      "updated": null,
      "updatedBy": null,
      "summarizationFailureReason": null,
      "summarizationUpdated": 1757000062000
    }
  ]
}
```

### Get a monitored case

Returns a single tracked case by its id, including its case identifier, status, risk level and the entities it is linked to. The record also carries the case details last fetched from the court (fullDetails, with lastFetchedAt), the AI case summary and risk justification, and a summary of each order. Order documents are not included: an order's attachment is "AVAILABLE" when a document exists, otherwise null. Requires case.read.

**Request URL**

`GET https://api.caseprimus.ai/api/caseprimus/v1/watchlist/cases/{id}`

**Request headers**

| Type | Name | Value | Optional |
| --- | --- | --- | --- |
| String | `X-CasePrimus-Api-Key` | Your API key | Required |

**Parameters**

| Name | In | Required | Description |
| --- | --- | --- | --- |
| `id` | path | Required |  |

**Sample request**

```bash
BASE="https://api.caseprimus.ai/api/caseprimus/v1"

curl "$BASE/watchlist/cases/CASE_ID" \
  -H "X-CasePrimus-Api-Key: $CASEPRIMUS_API_KEY"
```

**Responses**

- `200`: The case.
- `400`: Case does not exist (60401), or the id is malformed (60001).
- `403`: This case has not been shared with you (60403), or the caller lacks the case.read permission (60002).

**Response fields (HTTP 200)**

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `_id` | string |  | The case's id. |
| `number` | string |  | Human-readable case number, a string in the form NNNN-NNNNNN-NNNN. |
| `accountId` | string |  | Your account's id. |
| `watchlistEntityIds` | array of string |  | Every watchlist entity this case is linked to - the same real-world case can be tracked against more than one company. |
| `caseIdentifier` | object |  | Identifies one case. Which other fields you send depends on courtType - send exactly one of the alternatives listed for it. DC: cnr. SC: cnr, or caseType + registrationNumber, or diaryNumber. HC: cnr, or establishmentCode + caseType + registrationNumber. CC (consumer commission): registrationNumber (the e-Jagriti case number) only. NCLT, NCLAT, GSTAT: establishmentCode + filingNumber, or establishmentCode + caseType + registrationNumber. DRT, DRAT: establishmentCode + diaryNumber, or establishmentCode + caseType + registrationNumber. CESTAT: establishmentCode + diaryNumber, or establishmentCode + caseType + registrationNumber. NGT: establishmentCode (PB, EZ, CZ, WZ or SZ) + either caseType (OA, RA, MA, AP, EA, IA or TA) + registrationNumber (n/yyyy), or diaryNumber (the 12-digit diary number / year). SAT: establishmentCode (MUM) + either caseType (SEBI, IRDAI or PFRDA) + registrationNumber (the Appeal No., n/yyyy, at most 4 digits before the year), or filingNumber (the AL No. - Appeal Lodging number, n/yyyy). ITAT: establishmentCode (the bench's city in capitals, for example DELHI, MUMBAI or BANGALORE; Cochin is ERNAKULAM and Visakhapatnam is VISHAKHAPATNAM) + caseType (ITA, CO, ITSSA, ITTPA, ITITA, WTA, BMA, GTA, SA or MA) + registrationNumber (the Appeal No. and filing year, n/yyyy, at most 5 digits before the year); all three are required. APTEL: establishmentCode (DEL) + either caseType (APL, OP, EP, RP or CP) + registrationNumber (the Case No., n/yyyy), or diaryNumber (the DFR No., n/yyyy). The DFR number is the tribunal's diary number and every case has one from the day it is filed; a Case No. is allotted only on registration, so a recently filed case may be reachable by its DFR number alone. Note that the year means different things on the two: with a Case No. it is the year the case was registered, with a DFR No. the year it was filed, and for the same case these can differ.  |
| `caseIdentifier.courtType` | enum |  | One of: DC, SC, HC, CC, NCLT, NCLAT, GSTAT, DRT, DRAT, CESTAT, NGT, SAT, ITAT, APTEL |
| `caseIdentifier.cnr` | string |  | DC, SC, HC only. |
| `caseIdentifier.registrationNumber` | string |  | Format depends on courtType - see the description above. Usually number/year (for example 87/2018; at most 4 digits for SAT, 5 for ITAT); for HC the number/year is sent with caseType, and for CC it is the whole e-Jagriti case number. |
| `caseIdentifier.filingNumber` | string |  | NCLT/NCLAT/GSTAT only, and SAT (the AL No. - Appeal Lodging number - n/yyyy). |
| `caseIdentifier.diaryNumber` | string |  | SC, DRT, DRAT, CESTAT, NGT (the 12-digit diary number / year, e.g. 070111601768/2026) and APTEL (the DFR No., n/yyyy). |
| `caseIdentifier.establishmentCode` | string |  | Bench/tribunal code - required for HC (when not using cnr) and every tribunal court type. NGT: PB, EZ, CZ, WZ or SZ. SAT: MUM. APTEL: DEL. ITAT: the bench's city in capitals (DELHI, MUMBAI, BANGALORE ...; Cochin is ERNAKULAM, Visakhapatnam is VISHAKHAPATNAM). |
| `caseIdentifier.caseType` | string |  | Required alongside registrationNumber for most court types. The valid values depend on courtType, for example NGT: OA, RA, MA, AP, EA, IA, TA; SAT: SEBI, IRDAI, PFRDA; APTEL: APL, OP, EP, RP, CP; ITAT: ITA, CO, ITSSA, ITTPA, ITITA, WTA, BMA, GTA, SA, MA. |
| `snapshot` | object or null |  | The discovery record the case was added from, in CasePrimus's normalised form (null for a case added by identifier alone). Only the fields below are returned: provider references, provider documents and raw party structures are never included. Fields without a value are null. |
| `snapshot.cnrNumber` | string or null |  | Null for a consumer-commission or tribunal case, which is referenced by its case number instead. |
| `snapshot.caseNumber` | string or null |  |  |
| `snapshot.filingNumber` | string or null |  |  |
| `snapshot.registrationNumber` | string or null |  |  |
| `snapshot.court` | string or null |  |  |
| `snapshot.courtType` | string or null |  |  |
| `snapshot.state` | string or null |  |  |
| `snapshot.district` | string or null |  |  |
| `snapshot.caseType` | string or null |  |  |
| `snapshot.caseTypeName` | string or null |  | Full name of the case type. |
| `snapshot.caseNature` | string or null |  | Civil or criminal category, e.g. CIVIL. |
| `snapshot.caseTypeLabel` | string or null |  |  |
| `snapshot.caseStatus` | string or null |  |  |
| `snapshot.filingYear` | any or null |  | As the source reported it, an integer or a string. |
| `snapshot.filingDate` | string or null |  | As the source reported it, e.g. 2020-07-08. |
| `snapshot.registrationDate` | string or null |  |  |
| `snapshot.nextHearingDate` | string or null |  |  |
| `snapshot.decisionDate` | string or null |  |  |
| `snapshot.natureOfDisposal` | string or null |  |  |
| `snapshot.bench` | string or null |  |  |
| `snapshot.petitioner` | string or null |  | Petitioner names, comma-separated. |
| `snapshot.respondent` | string or null |  | Respondent names, comma-separated. |
| `snapshot.orders` | array of object |  |  |
| `riskLevel` | enum |  | One of: VERY_HIGH, HIGH, MODERATE, LOW, UNCLASSIFIED |
| `caseScore` | object or null |  | THE SCORE TO SHOW ON A ROW, on every case a search returns. 0-1000 where HIGHER IS BETTER, the same scale and direction as a company's `reputationScore` - and the same object `analysis.risk.caseScore` carries on the single case, computed the same way, so a list and a case page cannot print different numbers for one case.  It cannot contradict `riskLevel`: the level fixes the band (VERY_HIGH 0-199, HIGH 200-399, MODERATE 400-599, LOW 600-799, MINIMAL 800-1000) and the indicative scoring decides only the position inside it. Null where the level is UNCLASSIFIED - nothing has been analysed yet, and a case nobody has looked at must not read as the cleanest on the list. Filter on it with `$derived.scoreMin` / `$derived.scoreMax`. |
| `caseScore.value` | integer |  | 20 to 980 |
| `caseScore.scale` | enum |  | One of: 1000 |
| `caseScore.higherIsBetter` | enum |  | One of: true |
| `caseScore.band` | enum |  | Always equal to `riskLevel`. One of: VERY_HIGH, HIGH, MODERATE, LOW, MINIMAL |
| `status` | enum |  | One of: ACTIVE, PENDING_BACKOFFICE_REVIEW, REJECTED, ARCHIVED |
| `reviewedAt` | integer (int64) or null |  | Epoch ms the CasePrimus team reviewed the case; null until then. |
| `backOfficeReviewReason` | string or null |  | Why the case went to the CasePrimus team for review because of its identifier or add-time live lookup (for example COURT_TYPE_UNRESOLVED, CNR_LOOKS_INVALID, LOOKUP_FAILED); null otherwise. |
| `disposed` | boolean |  | true once the case is marked disposed. A disposed case stays ACTIVE and keeps using a case-quota slot until it is archived. |
| `disposedAt` | integer (int64) or null |  | Epoch ms the case was marked disposed. |
| `sharedWith` | array of object |  | Teams or users the case is shared with. |
| `sharedWith[].type` | enum |  | One of: team, user |
| `sharedWith[].id` | string |  | A team ID when type is 'team', a user ID otherwise. |
| `assignedTo` | string or null |  | User id of the person who owns following up on the case; null when unassigned. |
| `summarizationStatus` | enum or null |  | State of the AI analysis (case summary, risk level and per-order summaries). null until the analysis has started. One of: PENDING, COMPLETE, FAILED,  |
| `summarizationFailureReason` | string or null |  | Set when summarizationStatus is FAILED, for example NO_COURT_TYPE, INVALID_CNR, CAPTCHA_REQUIRED or FETCH_FAILED; null otherwise. |
| `summarizationUpdated` | integer (int64) or null |  | Epoch ms the analysis last ran or changed state. |
| `fullDetails` | object or null |  | The case details last fetched live from the court (same fields as the POST /case-lookup result, without searchId and latestSummary): caseType, filingNumber/Date/Year, registrationNumber/Date, cnrNumber, state, district, courtName, courtNumberAndJudge, courtEstablishment, first/next/previousHearingDate, caseStage, decisionDate, natureOfDisposal, caseStatus, petitioners/respondents (with counsel), acts, caseHistory, orders, linkedCases, transfers and more. null until a fetch has succeeded. |
| `fullDetails.orders` | array of object |  |  |
| `fullDetailsCourtType` | string or null |  | The court type the details were fetched for (DC, HC, SC, ...). |
| `lastFetchedAt` | integer (int64) or null |  | Epoch ms of the last successful live fetch of the case, even if nothing changed; null if none has succeeded. |
| `caseSummary` | string or null |  | AI-generated summary of the case; null until the analysis completes. |
| `riskJustification` | string or null |  | AI-generated reasoning behind riskLevel; null until the analysis completes. |
| `caseLabels` | array of string or null |  | What this case is ABOUT, from the same analysis call that wrote `caseSummary`. The same catalogue the litigation report uses, so the two products never disagree about what a case is. One or more ids, or `PROCEDURAL_ONLY` (neither the orders nor the court record reveal the subject matter) or `OTHERS` (the subject matter is clear but we have no id for it). Null until the analysis completes. |
| `caseLabelBasis` | enum or null |  | Which evidence the labels came from. `ORDER` - the case's own orders say so. `RECORD` - the case has no readable order and the label comes from the court's index entry, which is weaker and never reads HIGH. `BOTH` - they agree. `NEITHER` - `PROCEDURAL_ONLY`. One of: ORDER, RECORD, BOTH, NEITHER |
| `caseLabelConfidence` | enum or null |  | How good the evidence is, not how strongly we feel. A label alleging conduct requires an order to describe that conduct, never a statute name. One of: HIGH, MEDIUM, LOW |
| `caseLabelEvidence` | string or null |  | The words that decided the labels, quoted. Published so a label can be checked rather than taken on trust. |
| `casePartySide` | enum or null |  | Which side the monitored entity is on. The same outcome words mean opposite things depending on it. One of: PETITIONER, RESPONDENT, BOTH, UNCLEAR |
| `caseSuggestedLabel` | object or null |  | Set only where `caseLabels` is `OTHERS`: our own proposal for what this kind of case should be called, because a case we cannot categorise is still a case you need described. |
| `caseSuggestedLabel.id` | string |  |  |
| `caseSuggestedLabel.label` | string |  |  |
| `caseSuggestedLabel.why` | string |  |  |
| `orderSummaries` | array of object |  | One AI summary per order (up to 60), reused across refreshes while the order is unchanged. |
| `orderSummaries[].orderKey` | string |  | Stable key of the order. |
| `orderSummaries[].orderNumber` | string or null |  |  |
| `orderSummaries[].orderDate` | string or null |  |  |
| `orderSummaries[].judge` | string or null |  |  |
| `orderSummaries[].orderType` | string or null |  |  |
| `orderSummaries[].attachment` | string or null |  | "AVAILABLE" when a document is held for the order, otherwise null. |
| `orderSummaries[].status` | enum |  | SKIPPED: no readable document for the order. One of: PENDING, COMPLETE, FAILED, SKIPPED |
| `orderSummaries[].summary` | string or null |  |  |
| `orderSummaries[].detectedLanguage` | string or null |  | Language of the order document, e.g. English. |
| `orderSummaries[].error` | string or null |  | Why a FAILED or SKIPPED order has no summary. |
| `orderSummaries[].errorClass` | string or null |  | For a FAILED order: RATE_LIMIT, OVERLOADED, TIMEOUT, TOKEN_LIMIT, SERVER_ERROR, BAD_REQUEST or UNKNOWN. |
| `orderSummaries[].attempts` | integer |  |  |
| `orderSummaries[].computedAt` | integer (int64) or null |  |  |
| `analysis` | object |  | The fields a single case carries beyond the list, shared by the report's case detail and the watchlist's case analysis. |
| `analysis.caseRef` | string |  | The case's reference within this report. |
| `analysis.caseNumber` | string or null |  | The case number, or whichever of the registration, filing or CNR number the court gave instead. |
| `analysis.cnrNumber` | string or null |  |  |
| `analysis.court` | string or null |  |  |
| `analysis.courtType` | string |  | e.g. DC, HC, SC, NCLT, CESTAT. |
| `analysis.state` | string or null |  |  |
| `analysis.district` | string or null |  |  |
| `analysis.caseType` | string or null |  |  |
| `analysis.caseCategory` | string or null |  |  |
| `analysis.status` | enum |  | One of: PENDING, DISPOSED |
| `analysis.caseStatus` | string or null |  | The court's own words for where the case stands. |
| `analysis.caseStage` | string or null |  |  |
| `analysis.filingDate` | string or null |  |  |
| `analysis.filingYear` | integer or null |  |  |
| `analysis.registrationDate` | string or null |  |  |
| `analysis.decisionDate` | string or null |  |  |
| `analysis.nextHearingDate` | string or null |  |  |
| `analysis.natureOfDisposal` | string or null |  |  |
| `analysis.petitioners` | array of string |  |  |
| `analysis.respondents` | array of string |  |  |
| `analysis.matchedParty` | string or null |  | The party on the record that matched the company. |
| `analysis.companySide` | enum or null |  | One of: PETITIONER, RESPONDENT, BOTH |
| `analysis.acts` | array of string |  | The acts and sections as the court wrote them. |
| `analysis.counts` | object |  |  |
| `analysis.courtCategory` | string or null |  | The court's own category for the dispute, in the court's own coding, e.g. "14.02 Cheque Dishonour ( 1182 )". |
| `analysis.courtSubCategory` | string or null |  |  |
| `analysis.courtSubSubCategory` | string or null |  |  |
| `analysis.courtRegistrationNumber` | string or null |  | The number the court registered the case under, from the court's own record. `caseNumber` above is whichever identifying number the search result carried, which is not always this one - a case is frequently registered under a different number from the one it was filed under, and reconciling a report against a court's site needs both. |
| `analysis.courtFilingNumber` | string or null |  | The number the case was filed under |
| `analysis.previousHearingDate` | string or null |  | The last hearing the court held |
| `analysis.orderIds` | array of string |  | The ids of this case's orders on the court's record, in the order the court lists them. Computed from the order itself, so an id here is the same id a fresh lookup of the case returns - which is how an order named in a report is matched to the order a download can be asked for; the endpoint's own description gives the sequence. Present on the list and on the single case alike. Empty where the court's details could not be fetched or the court lists no order, and short of `counts.orders` on a case fetched before whose stored orders have no ids until it is fetched again. An id names an order on the court's RECORD, which is not the same as a document existing: several courts list orders they published nothing for. The orders' own numbers, dates and types are on the single-case response and in the JSON export, not here. |
| `analysis.category` | string |  | The kind of litigation, e.g. CRIMINAL_CHEQUE_BOUNCE, INSOLVENCY_RECOVERY. |
| `analysis.categoryLabel` | string |  |  |
| `analysis.risk` | object |  | What this case means on its own. The level and the score come from the kind of case, the company's side, how it stands and what the statute behind it allows - not from reading any order. |
| `analysis.orderRead` | object |  | What was read for this case, and what it said. Always present and always carrying a `status`, so a reader can tell "this is a Basic report" (`NOT_APPLICABLE`) from "the court published no document" (`NO_ORDER`, `NO_DOCUMENT`) and from "we could not read it" (`FAILED`). |
| `analysis.locationMatch` | object |  | How closely the case matched the company - whether it was filed where the company is registered or has an address. An indication, not a verification. |
| `analysis.details` | object |  | Whether the court's own record could be fetched for this case, and why not where it could not. |
| `analysis.lookupIdentifier` | object (free-form) or null |  | What to send to Live Case Lookup or an order download for this case. Null where the case carries nothing that court can be asked with, or where its only identifier is an internal one. Single-case response only. |
| `analysis.actsExplained` | object or null |  | What the acts and sections on this case's record mean. Single-case response only. A section the catalogue does not hold is simply absent; nothing is guessed. |
| `analysis.judges` | string or null |  | The bench as the court prints it, in one string - names, section and bench run together and pipe-separated, e.g. "HON'BLE MR. JUSTICE SANJEEV NARULA \| Original side \| High Court of Delhi". Not a list: the courts do not publish one, and splitting this reliably is not possible. Null where the court's details could not be fetched or it named nobody. |
| `analysis.courtEstablishment` | string or null |  |  |
| `analysis.firstHearingDate` | string or null |  |  |
| `analysis.liveParties` | object or null |  | The parties as the court recorded them, with addresses where it gave them. Null where the court's details could not be fetched. |
| `analysis.readOrderId` | string or null |  | The id of the order this report READ, which is the one order that downloads free - an Advanced report already fetched and stored that document in order to read it, so handing it back is not a fetch and is not charged. Every other order on the case is a fresh court fetch and is. Null on a Basic report, which reads no order at all, and null where the court gave a link rather than a document we could store, because fetching that one costs as much as any other. Single-case response only: matching it needs the orders' numbers and dates, which the list does not carry. |
| `analysis.courtRecord` | object (free-form) or null |  | THE COURT'S OWN RECORD OF THIS CASE, WHOLE - every field the court returned, in the court's own field names, exactly as Live Case Lookup returns them. The fields above are this report's reading of that record and are the ones to build on; this is here so that reading one case of a report never requires paying for a Live Case Lookup of the same case to see what the court actually said.  A High Court case carries 41 fields and a district one more, varying by court type, which is why nothing here is enumerated: among them `objections` (why the case has not moved), `category`/`subCategory`/`subSubCategory` (what the court itself calls the dispute), `caseHistory` (every hearing, with its purpose and judge), `documents` and `interlocutoryApplicationDetails` (the filings), `fir` (the police record), `linkedCases`, `transfers` and `earlierCourts` (where else the matter has been), `coram`, `bench`, `judicial`, `shortOrder`, `petitionersText`/`respondentsText` (the parties as one block of the court's own text, advocates included), `registrationNumber`, `filingNumber`, `cnrNumber`, and the court type's own additions - `assessmentYear` at ITAT, `impugnType`/`impugnNumber`/`impugnDate` at the appellate tribunals.  NOT IN IT - the orders, which are the `orders` array above: each of those carries the stable `orderId` the download endpoints take, and the court's own order does not.  NULL for a case fetched before. The court's answer was not stored then and is not backfilled, because recovering it means asking the court again - a paid lookup per case. Null here means "not kept for this case", never "the court said little".  ALWAYS NULL inside a watchlist case's `analysis`, and deliberately: that case publishes the very same record as its own `fullDetails`, one level up in the same response, so repeating it here would send it twice. |
| `analysis.orders` | object or null |  | Every order read for this case, summarised. Null where none has been read. |
| `lawfulBasisNoticeVersion` | string or null |  | Version of the lawful-basis notice in force when the case was added. |
| `created` | integer (int64) |  | When the case was added, in milliseconds since the Unix epoch. |
| `createdBy` | string or null |  |  |
| `updated` | integer (int64) or null |  | When the case was last updated, in milliseconds since the Unix epoch. |
| `updatedBy` | string or null |  |  |

**Example response (200)**

```json
{
  "_id": "CPWLC0exampledemo0001",
  "number": "4821-310045-8001",
  "accountId": "CPA0exampledemo0001",
  "watchlistEntityIds": [
    "CPWLE0exampledemo0001"
  ],
  "caseIdentifier": {
    "cnr": "HRFB010051662020",
    "courtType": "DC"
  },
  "snapshot": {
    "cnrNumber": "HRFB010051662020",
    "caseNumber": "135/2020",
    "filingNumber": "1821/2020",
    "registrationNumber": "135/2020",
    "court": "District and Sessions Courts, Faridabad",
    "courtType": "District Court",
    "state": "Haryana",
    "district": "Faridabad",
    "caseType": "APP",
    "caseTypeName": "Application",
    "caseNature": "CIVIL",
    "caseTypeLabel": "Application",
    "caseStatus": "Disposed",
    "filingYear": 2020,
    "filingDate": "2020-07-08",
    "registrationDate": "2020-07-09",
    "nextHearingDate": null,
    "decisionDate": "2020-10-27",
    "natureOfDisposal": "Uncontested - DISMISSED AS WITHDRAWN",
    "bench": null,
    "petitioner": "Acme Traders Pvt Ltd",
    "respondent": "Jane Doe Realty Ltd",
    "orders": [
      {
        "number": 1,
        "orderDate": "2020-07-09",
        "judge": null,
        "documentUrl": "https://files.example.com/public/caseprimus/orders/file?token=EXAMPLE_TOKEN_1"
      },
      {
        "number": 2,
        "orderDate": "2020-08-06",
        "judge": null,
        "documentUrl": "https://files.example.com/public/caseprimus/orders/file?token=EXAMPLE_TOKEN_2"
      },
      {
        "number": 3,
        "orderDate": "2020-08-18",
        "judge": null,
        "documentUrl": "https://files.example.com/public/caseprimus/orders/file?token=EXAMPLE_TOKEN_3"
      }
    ]
  },
  "riskLevel": "MODERATE",
  "status": "ACTIVE",
  "reviewedAt": null,
  "backOfficeReviewReason": null,
  "disposed": false,
  "disposedAt": null,
  "sharedWith": [],
  "assignedTo": null,
  "summarizationStatus": "COMPLETE",
  "fullDetails": {
    "caseType": "APP - APPLICATION",
    "filingNumber": "1821/2020",
    "filingDate": "08-07-2020",
    "filingYear": "2020",
    "registrationNumber": "135/2020",
    "registrationDate": "09-07-2020",
    "cnrNumber": "HRFB010051662020",
    "state": "Haryana",
    "district": "Faridabad",
    "courtName": "District and Sessions Courts, Faridabad",
    "courtNumberAndJudge": "1-District and Sessions Judge",
    "courtEstablishment": "District and Sessions Court, Faridabad",
    "firstHearingDate": "09-July-2020",
    "nextHearingDate": null,
    "previousHearingDate": null,
    "caseStage": null,
    "decisionDate": "27-October-2020",
    "natureOfDisposal": "Uncontested - DISMISSED AS WITHDRAWN",
    "caseStatus": "Case Disposed",
    "coram": null,
    "judicial": null,
    "causeListName": null,
    "bench": null,
    "shortOrder": null,
    "petitioners": [
      {
        "petitionerName": "Acme Traders Pvt Ltd",
        "petitionerCounsel": "Advocate - Advocate A"
      }
    ],
    "petitionersText": "1) Acme Traders Pvt Ltd\n                 Advocate - Advocate A",
    "respondents": [
      {
        "respondentName": "Jane Doe Realty Ltd",
        "respondentCounsel": null
      }
    ],
    "respondentsText": "1) Jane Doe Realty Ltd",
    "acts": [
      {
        "act": "CODE OF CIVIL PROCEDURE",
        "sections": "APP"
      }
    ],
    "interlocutoryApplicationDetails": null,
    "caseHistory": [
      {
        "reg": "135/2020",
        "causeListType": null,
        "judge": "District and Sessions Judge",
        "purpose": "Appearance",
        "nextHearingDate": "06-08-2020",
        "businessDate": "09-07-2020"
      },
      {
        "reg": "135/2020",
        "causeListType": null,
        "judge": "District and Sessions Judge",
        "purpose": "Appearance",
        "nextHearingDate": "18-08-2020",
        "businessDate": "06-08-2020"
      },
      {
        "reg": "135/2020",
        "causeListType": null,
        "judge": "District and Sessions Judge",
        "purpose": "Appearance",
        "nextHearingDate": "16-09-2020",
        "businessDate": "18-08-2020"
      }
    ],
    "orders": [
      {
        "number": "1",
        "orderDate": "09-07-2020",
        "judge": null,
        "attachment": "AVAILABLE",
        "orderType": null
      },
      {
        "number": "2",
        "orderDate": "06-08-2020",
        "judge": null,
        "attachment": "AVAILABLE",
        "orderType": null
      },
      {
        "number": "3",
        "orderDate": "18-08-2020",
        "judge": null,
        "attachment": "AVAILABLE",
        "orderType": null
      }
    ],
    "objections": null,
    "category": null,
    "subCategory": null,
    "subSubCategory": null,
    "fir": null,
    "earlierCourts": null,
    "documents": null,
    "linkedCases": null,
    "transfers": []
  },
  "fullDetailsCourtType": "DC",
  "lastFetchedAt": 1757000012000,
  "caseSummary": "Application filed by Acme Traders Pvt Ltd in the District and Sessions Court, Faridabad; it was withdrawn and dismissed in October 2020.",
  "riskJustification": "The case is disposed and the application was withdrawn without any adverse finding, so the exposure is limited; it is kept at moderate because the dispute with the respondent is not otherwise resolved on the record.",
  "orderSummaries": [
    {
      "orderKey": "8acd04f57027fe8c8a318e95d0ca74a7",
      "orderNumber": "1",
      "orderDate": "09-07-2020",
      "judge": null,
      "orderType": null,
      "attachment": "AVAILABLE",
      "status": "COMPLETE",
      "summary": "Appearance recorded for the applicant; the matter was listed for the next date.",
      "detectedLanguage": "English",
      "error": null,
      "errorClass": null,
      "attempts": 1,
      "computedAt": 1757000050000
    },
    {
      "orderKey": "af2538a37a645f61a09c177924d3ecb5",
      "orderNumber": "2",
      "orderDate": "06-08-2020",
      "judge": null,
      "orderType": null,
      "attachment": "AVAILABLE",
      "status": "COMPLETE",
      "summary": "Appearance recorded again; the court adjourned the matter to the next listed date.",
      "detectedLanguage": "English",
      "error": null,
      "errorClass": null,
      "attempts": 1,
      "computedAt": 1757000054000
    },
    {
      "orderKey": "6e96db2dfa0d699908f8d5fed84af3ae",
      "orderNumber": "3",
      "orderDate": "18-08-2020",
      "judge": null,
      "orderType": null,
      "attachment": "AVAILABLE",
      "status": "COMPLETE",
      "summary": "Applicant withdrew the application and the court dismissed it as withdrawn.",
      "detectedLanguage": "English",
      "error": null,
      "errorClass": null,
      "attempts": 1,
      "computedAt": 1757000058000
    }
  ],
  "lawfulBasisNoticeVersion": "v1",
  "created": 1757000000000,
  "createdBy": "CPU0exampledemo0001",
  "updated": null,
  "updatedBy": null,
  "summarizationFailureReason": null,
  "summarizationUpdated": 1757000062000
}
```

### Stop monitoring a case

Stops monitoring a case. The case is archived rather than physically removed, and it no longer counts against your monitored-case limit. The response is an empty object. Requires case.delete on the case.

**Request URL**

`DELETE https://api.caseprimus.ai/api/caseprimus/v1/watchlist/cases/{id}`

**Request headers**

| Type | Name | Value | Optional |
| --- | --- | --- | --- |
| String | `X-CasePrimus-Api-Key` | Your API key | Required |

**Parameters**

| Name | In | Required | Description |
| --- | --- | --- | --- |
| `id` | path | Required |  |

**Sample request**

```bash
BASE="https://api.caseprimus.ai/api/caseprimus/v1"

curl -X DELETE "$BASE/watchlist/cases/CASE_ID" \
  -H "X-CasePrimus-Api-Key: $CASEPRIMUS_API_KEY"
```

**Responses**

- `200`: Case archived (empty object).
- `400`: Case does not exist (60401), or the id is malformed (60001).
- `403`: This case has not been shared with you (60403), or the caller lacks the case.delete permission (60002).

**Example response (200)**

```json
{}
```

## Court types

Set `courtType` in the `caseIdentifier` to one of these codes. Send the `cnr` for District Courts, the Supreme Court and High Courts where you have it.

| Code | Court or tribunal |
| --- | --- |
| 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 |
| NGT | National Green Tribunal |
| SAT | Securities Appellate Tribunal |
| ITAT | Income Tax Appellate Tribunal |
| APTEL | Appellate Tribunal for Electricity |

## Limits and review

- **Monitored-case limit.** A new case counts against your monitored-case limit, and only active cases count. Over the limit you get `403` with code `60417`. Linking to a case you already track does not count again.
- **Disposed cases.** A case the court already shows as disposed is added only when you send `confirmDisposed` as `true`. Otherwise the call fails with code `60430` and nothing is added.
- **Cases awaiting review.** On accounts where the CasePrimus team reviews new cases, a new case starts as `PENDING_BACKOFFICE_REVIEW` until it is reviewed, and so does a case whose identifier the court cannot confirm. `backOfficeReviewReason` says why.
- **Stopping.** Stopping a case archives it. It no longer counts against your limit, and archived cases are not returned by a search unless your `$filter` names a status.

## Alerts and webhooks

Alerts appear in your dashboard. To have the data flow into a system you already run, subscribe a webhook to the events you care about.

| Event | What it tells you |
| --- | --- |
| `case.added` | A new case was detected and added to the watchlist without needing manual review. |
| `case.new_order_or_hearing` | A new order was uploaded, or a hearing date was added/changed, on a monitored case. |
| `case.status_changed` | A monitored case's status was updated (e.g. Active to Archived). |
| `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. |

## Errors

| Status | Code | Message |
| --- | --- | --- |
| 400 | 60400 | Watchlist entity does not exist |
| 400 | 60401 | Watchlist case does not exist |
| 400 | 60430 | This case already appears to be disposed - confirm you still want to add it to the watchlist |
| 403 | 60403 | This watchlist case has not been shared with you |
| 403 | 60417 | This account's monitored case limit has been reached - contact your account manager to increase it |

## Frequently asked questions

### How is this different from Live Case Lookup?

A lookup is one-time and on demand: you get the case as it stands and nothing keeps watching. Case Monitoring follows the case through the court, reads every new order and alerts you when something changes.

### Should I add a party or a case?

Add a party when you want to watch a company or person and have CasePrimus.ai find their cases. Add a case when you already know the case you care about.

### How often is a monitored case checked?

Every day. New hearings, orders and status changes are picked up and raise an alert.

### Is there a limit on how many cases I can monitor?

Yes. Your account has a monitored-case limit, and only active cases count. When it is reached, adding a new case returns 403 with code 60417. Stopping a case frees a slot.

### What happens if I add a case I already track?

It is linked to the existing record instead of being duplicated. The response has linkedExisting set to true, and it does not count against your limit again.

### Which courts and tribunals are covered?

District Courts, High Courts, the Supreme Court, Consumer Commissions, and tribunals including NCLT, NCLAT, DRT, DRAT, GSTAT, CESTAT, NGT, SAT, ITAT and APTEL.

### Can I get the court's order documents?

Use the Live Case Lookup API to download an order or all of them as a zip. Orders on a monitored case are read automatically, and each one is marked AVAILABLE when a document exists.
