ORIG LEADS SUITE
Powered By
Real-Time Case Status Updates For Actionable Legal Insights
Get structured, daily-refreshed case update data from every level of the Indian judiciary system. Whether you're building a legal case management platform, a litigation tracker for law firms, a compliance screening tool for enterprises, or an automated alert system for litigants, our product delivers court hearing dates, case status changes, next hearing schedules, order updates data in clean JSON - ready to integrate in minutes. Covering all District Courts, Talukas, High Courts, Supreme Court and Tribunals including NCLT, NCLAT, GSTAT, DRT, DRAT, Consumer Courts, this is the most comprehensive daily court case update feed available for India's legal tech ecosystem.
Key Features
- Asynchronous API: Documents are processed sequentially and made available as soon as they’re ready.
- CDN Hosting via Attestr: Ensures fast, stable, and secure access to documents.
- Webhook Support: Get notified automatically when document processing is complete.
- Seamless Integration: Ideal for legal tech platforms, compliance engines, and litigation monitoring tools.
Supported Courts & Query Parameters
| Type | Name | Description |
|---|---|---|
| String | courtType | Supported court types are - DC - District Courts HC - High Courts SC - Supreme Court CC - eJagriti Consumer Court NCLT - National Company Law Tribunal NCLAT - National Company Law Appellate Tribunal GSTAT - GST Appellate Tribunal DRT - Debt Recovery Tribunal DRAT - Debt Recovery Appellate Tribunal |
| String | cnr | 16 digit alphanumeric CNR. Use this to track case updates using CNR Number. |
| String | establishmentCode | Bench code. Values vary depending on courtType provided. For allowed values, refer to Unified Case Types And Court Establishments API This is used in combination with caseType and registrationNumber fields to track case updates by case number. |
| String | caseType | Case type code. Value vary depending on courtType provided. For allowed values, refer to Unified Case Types And Court Establishments API |
| String | registrationNumber | Case registration number. Accepted format is caseNumber/caseYear. Eg 121/2024 |
| String | diaryNumber | Diary number as applicable for few court types. Accepted format is diaryNumber/diaryYear. Eg 10/2026 |
| String | filingNumber | Use this field to search by filing number. Applicable depending on the courtType selected. Eg. 1023400763 |
Sample Queries
xxxxxxxxxx---- For District Courts - Search Case By CNR{ "courtType": "DC", "cnr": "RJJS010001272025"} -- For High Court - Search Case By CNR{ "courtType": "HC", "cnr": "SKHC010001342025"} -- For High Court - Search Case By Case Number{ "courtType": "HC", "establishmentCode": "TRHC01", // High Court of Tripura "caseType": "Arb.A.", // Arb.A. - Appeals under Indian Arbitration Act. "registrationNumber": "1/2025"} -- For Supreme Court - Search By CNR{ "courtType": "SC", "cnr": "SCIN010089602025"} -- For Supreme Court - Search By Case Number{ "courtType": "SC", "caseType": "Crl.A.", // Criminal Appeal "registrationNumber": "1/2025"} -- For Supreme Court - Search By Diary Number{ "courtType": "SC", "diaryNumber": "14/2025"} -- For Consumer Court - eJagriti - Search By Registration Number{ "courtType": "CC", "registrationNumber": "<registrationNumber>" // See below for registrationNumberFormat}For National Commision - NC/CaseType/CaseNumber/Year Eg. NC/EA/1/2024For State Commission - SC/StateLGDCode/CaseType/CaseNumber/Year Eg. SC/28/EA/1/2024For District Commission - DC/DistrictLGDCode/CaseType/CaseNumber/Year Eg DC/632/CC/1/2024 -- For National Company Law Tribunal - Search By Filing Number{ "courtType": "NCLT", "establishmentCode": "ND", // New Delhi Bench "filingNumber": "23469028908"} -- For National Company Law Tribunal - Search By Case Number{ "courtType": "NCLT", "establishmentCode": "ND", // New Delhi Bench "caseType": "CP", // Company Petition(Company Act) "registrationNumber": "1/2024"} -- For National Company Law Appellate Tribunal - Search By Filing Number{ "courtType": "NCLAT", "establishmentCode": "CH", // Chennai Bench "filingNumber": "23469028908"} -- For National Company Law Appellate Tribunal - Search By Case Number{ "courtType": "NCLAT", "establishmentCode": "CH", // Chennai Bench "caseType": "Company Appeal(AT)", // Company Appeal(AT) "registrationNumber": "1/2024"} -- For GST Appellate Tribunal - Search By Filing Number{ "courtType": "GSTAT", "establishmentCode": "PB", // Delhi (PB) Bench "filingNumber": "23469028908"} -- For GST Appellate Tribunal - Search By Case Number{ "courtType": "GSTAT", "establishmentCode": "PB", // Delhi (PB) Bench "caseType": "Rect.M", //Rectification of Mistake "registrationNumber": "1/2024"} -- For Debt Recovery Tribunal - Search By Diary Number{ "courtType": "DRT", "establishmentCode": "DA1", // DEBTS RECOVERY TRIBUNAL AHMEDABAD(DRT 1) "diaryNumber": "1/2024"} -- For Debt Recovery Tribunal - Search By Case Number{ "courtType": "DRT", "establishmentCode": "DA1", // DEBTS RECOVERY TRIBUNAL AHMEDABAD(DRT 1) "caseType": "APPEAL", //APPEAL "registrationNumber": "1/2024"} -- For Debt Recovery Appellate Tribunal - Search By Diary Number{ "courtType": "DRAT", "establishmentCode": "DCE", // DEBT RECOVERY APPELLATE TRIBUNAL - CHENNAI "diaryNumber": "1/2024"} -- For Debt Recovery Appellate Tribunal - Search By Case Number{ "courtType": "DRAT", "establishmentCode": "DCE", // DEBT RECOVERY APPELLATE TRIBUNAL - CHENNAI "caseType": "REGULAR APPEAL", //REGULAR APPEAL "registrationNumber": "1/2024"}Response Format & Data Fields
| Key | Description |
|---|---|
| caseType | Case type as registered |
| filingNumber | File number assigned to the case eg 362/2018 |
| filingDate | Case filing date |
| filingYear | Filing year if available |
| registrationNumber | Case registration number eg 362/2018 |
| registrationDate | Date of registration of the case |
| cnrNumber | Unique case identification number |
| state | Court state where case is registered |
| district | Court district where case is registered |
| courtName | Name of the court eg Junior Civil Judge Court |
| courtNumberAndJudge | Court number and judge info if available. Eg. 2-Additional Junior Civil Judge |
| courtEstablishment | Court complex / establishment name where the case is being contested |
| firstHearingDate | Date of first hearing of the case |
| nextHearingDate | Next hearing date if case is in pending state. For disposed cases this could be empty. |
| previousHearingDate | Date of last hearing |
| caseStage | Current stage of the case. Eg. BAIL HEARING etc. |
| decisionDate | Date of decision if the case stands disposed. |
| natureOfDisposal | Type of disposal, contested, uncontested etc if the case is disposed. |
| caseStatus | Case status - Pending, Disposed etc. |
| coram | Generally applies to Hon'able High courts, indicates the number of judges on the bench Eg, 1760 HONOURABLE MR. JUSTICE KALYAN RAI SURANA |
| judicial | Judicial section information generally available for higher courts only e.g Criminal Section |
| causeListName | Name of the cause list if available |
| bench | Applicable for higher courts. Name of the bench that heard the case. eg Single Bench |
| shortOrder | Short order if put up for hearing on another date |
| petitioners | List of petitioners as mentioned in the case. Each petitioner has the following fields. petitionerName - Name of the petitioner petitionerCounsel- Name of the advocate / counsel if available |
| petitionersText | All the petitioners's information combined in one long text format. |
| respondents | List of respondents as mentioned in the case. Each respondent in the list has the following fields. respondentName - Name of the respondent respondentCounsel - Counsel or the advocate name for the respondent |
| respondentsText | All the respondent's information combined in one long text format |
| acts | List of Acts and corresponding sections as applicable to this case. Each entry in the list has the following structure. act - Name of the act as applied to the case sections - Applied sections from the corresponding act. |
| interlocutoryApplicationDetails | List of any interlocutory petitions/applications (IA) filed. An IA is generally filed in existing legal proceedings to request interim relief. Each item in the list has the following structure. number IA file number party Party name and counsel that filed IA filingDate Date of filing of the IA application nextDate Next date as applicable status Status of the application - approved, rejected, in hearing etc. caseNumber - case number if available particulars - particulars of the case if available Null if the details are not available |
| caseHistory | History of case hearings. This is a list, each item in the list has the following structure. reg - Registration number if available causeListType - Cause list name generally applicable for higher courts only judge - Judge / bench that heard the case. purpose - Purpose of hearing nextHearingDate - Date of next hearing as assigned businessDate - Date of hearing businessDescription - A brief description of what happened during this hearing adjournmentReason - Reason if the hearing was adjourned. |
| orders | List of order and judgements if available. Each order in the list has the following structure - number - Order number orderDate - Date on which the order was issued judge - Judge / bench that issued the order attachment - Order documents pdf links. These are public links hosted on Attestr CDN details - Order details if available orderType - orderType such as interim, final if available |
| objections | List of any objections raised by either of the parties during the trial. Each objection has the following structure. number - Objection number objection - Objection title / description scrutinyDate - Date of scrutiny as assigned for the object complianceDate - Compliance date if any receiptDate - Date of receipt of the scrutiny |
| category | Category of the case generally applies to the higher courts. Eg. 10266 - Bail Application Under section 439 Cr. P. C ( 308 ) |
| subCategory | Sub category if applicable |
| subSubCategory | Further division under the sub category if applicable |
| fir | Details of FIR if any mapped to this case. The FIR object has the following structure. state - State where the police station is located district - District where the police station is located policeStation - Name of the police station number - FIR number year - Date or year in which FIR is filed |
| earlierCourts | Lower court information if applicable. It has the following structure - courtNumberAndName - Name of the lower court caseNumberAndYear - Case number as year as registered in the lower court state - State where lower court is located district - District where lower court is located |
| documents | List of documents as filed by the counsels in the case. Each document object has the following structure. docNumber - Document number as assigned at the time of filing docName - Name of the document filed advocate - Counsel name who filed the document receivingDate - Date of receiving as registered in the court records filedBy - Party name |
| linkedCases | Case linked to the provided case. Each linked case object has the following structure. filingNumber - Linked case filing number caseNumber - Linked case number status - Linked case status caseTitle - Title of the case if available petitioner - Petitioner party name if available respondent - Respondent party name if available statusDescription - description of the status if available |
| transfers | List of transfers to other courts if any. Each transfer object has the following structure. reg - Registration no transferred - Date of transfer from - Source court name to - Destination court name |
Sample JSON Response
{ "caseType": "BA - BAIL APPLICATION", "filingNumber": "761/2017", "filingDate": "16-05-2017", "filingYear": "2017", "registrationNumber": "126/2017", "registrationDate": "16-05-2017", "cnrNumber": "PBBTA10007652017", "state": "Punjab", "district": "Bathinda", "courtName": "Criminal Courts, Talwandi Sabo", "courtNumberAndJudge": "1-Sub Divisional Judicial Magistrate", "courtEstablishment": "Chief Judicial Magistrate, Taluka Court, Talwandi Sabo", "firstHearingDate": "16-May-2017", "nextHearingDate": null, "caseStage": null, "decisionDate": "20-May-2017", "natureOfDisposal": "Contested - ALLOWED", "caseStatus": "Case Disposed", "coram": null, "judicial": null, "causeListName": null, "bench": null, "shortOrder": null, "petitioners": [ { "petitionerName": "STATE OF PUNJAB", "petitionerCounsel": "Advocate - APP" } ], "petitionersText": "1) STATE OF PUNJAB\n Advocate - APP", "respondents": [ { "respondentName": "AMRXXXXXXXXX @ AMRIT", "respondentCounsel": "Advocate - Parveen Kumar Ranga" } ], "respondentsText": "1) AMRXXXXXXX @ AMRIT\n Advocate - Parveen Kumar Ranga", "acts": [ { "act": "Code of Criminal Procedure, 1973", "sections": "61, 1, 14EXCISEACT" } ], "interlocutoryApplicationDetails": null, "caseHistory": [ { "reg": "126/2017", "causeListType": null, "judge": "Sub Divisional Judicial Magistrate", "purpose": "Consideration", "nextHearingDate": "20-05-2017", "businessDate": "16-05-2017" }, { "reg": "126/2017", "causeListType": null, "judge": "Sub Divisional Judicial Magistrate", "purpose": "Disposed", "nextHearingDate": null, "businessDate": "20-05-2017" } ], "orders": [ { "number": "1", "orderDate": "16-05-2017", "judge": null, "attachment": "https://cdn.attestr.com/public/courtx/pbbta10007652017-fba39d0fe4d32b75b14ca1e9a7e0e4b514066e61c06516a53ee1c914b41c667f.pdf" }, { "number": "2", "orderDate": "20-05-2017", "judge": null, "attachment": "https://cdn.attestr.com/public/courtx/pbbta10007652017-452edff89531dde3789e03217955559582d07502d42dd5968a0d9d32a9c24602.pdf" } ], "objections": null, "category": null, "subCategory": null, "subSubCategory": null, "fir": { "state": null, "district": null, "policeStation": "Talwandi Sabo", "number": "94", "year": "2017" }, "earlierCourts": null, "documents": null, "linkedCases": null, "transfers": []}Beyond Case Tracking - AI-Powered Legal Intelligence Built In
- Case Order Summarization: Generates concise summaries of each order or judgment, regardless of language, for quick understanding.
- Order Document Translation: Translate court orders across Indian languages in real time
- Combined Order Summary: Provides a unified summary of all orders to give a complete picture of case history.
- Case Summary: Produces an easy-to-read narrative explaining what the case is about, the sequence of events, and key parties involved.
- Risk Assessment: Assigns a Risk Level (Very High to No Risk) and a Risk Score (0–1000 scale) similar to a credit score, where a lower score indicates higher risk.
- Risk Summary: Explains the reasoning behind the risk score and classification to support decision-making.
This helps lenders such as banks, NBFCs, insurers, legal tech firms, compliance systems, and enterprises instantly understand the nature, intensity, and risk exposure of any court case - without needing to read hundreds of pages of orders or judgments.
Sample Summaries JSON
"riskScore": 650, "riskLevel": 2, "riskSummary": "Rating: 2\nReasoning: The case was allowed due to the accused being in custody since 03-05-2017 and nothing needing to be recovered from them, indicating that there is sufficient evidence against the accused. However, the bail application was still granted on a relatively low bond of Rs.50,000/- with one surety, suggesting that the risk associated with the case is moderate rather than high.", "caseSummary": "On May 16, 2017, a bail application was presented on behalf of an accused individual, citing their detention since May 3, 2017. The application was subsequently registered and a notice was sent to the state authorities on May 20, 2017.\n\nFollowing this, the court deliberated on the matter, ultimately concluding that the accused did not require further custody as no recovery was needed from them. As such, their bail application was allowed.\n\nTo secure their release, the accused furnished bail bonds worth Rs.50,000/- along with one surety, which were accepted by the authorities. Consequently, a release warrant was issued on May 20, 2017, allowing the accused to be freed from custody.\n\nThis decision was made within a contested proceedings, resulting in the case being disposed of with an outcome of ALLOWED under Section 61 of the Code of Criminal Procedure, 1973, specifically Sections 1 and 14.", "orders": [ { "number": "1", "orderDate": "16-05-2017", "judge": null, "attachment": "https://cdn.attestr.com/public/courtx/pbbta10007652017-fba39d0fe4d32b75b14ca1e9a7e0e4b514066e61c06516a53ee1c914b41c667f.pdf", "orderSummary": "Bail application was presented, registered and notice sent to state on 20-05-2017." }, { "number": "2", "orderDate": "20-05-2017", "judge": null, "attachment": "https://cdn.attestr.com/public/courtx/pbbta10007652017-452edff89531dde3789e03217955559582d07502d42dd5968a0d9d32a9c24602.pdf", "orderSummary": "The accused's bail application was allowed due to them being in custody since 03-05-2017 and nothing needing to be recovered from them. Bail bonds of Rs.50,000/- with one surety were furnished and accepted, resulting in the release warrant being issued." }] On This Page
Monitor Daily Court Case Updates - All Indian Courts, One IntegrationReal-Time Case Status Updates For Actionable Legal InsightsBeyond Case Tracking - AI-Powered Legal Intelligence Built InSupported Courts & Query ParametersResponse Format & Data FieldsSample QueriesSample JSON ResponseSample Summaries JSON