Court Data APIs in India: What They Are and What They Can Pull (2026)
What a court data API is in India, what eCourts and NJDG expose, what case status, cause lists and orders you can pull, how often the data updates, and the legitimate uses for enterprises. Last verified October 2026.
Explainer · Court Data
A court data API is a way to pull Indian court information into your own software automatically, instead of opening court websites and copying details by hand. It can return things like the status of a case, the next hearing date, the cause list, and the orders passed, in a structured form your systems can read. This guide explains what the official sources, eCourts and NJDG, expose, what an API can actually pull, how current the data is, and the legitimate ways enterprises use it. Last verified October 2026.
- What it is: a structured, automatic way to pull Indian court information into your own software.
- Official sources: eCourts Services and the NJDG, run under NIC, covering district and High Courts; the Supreme Court runs its own system.
- What it pulls: case status, next hearing date, cause lists, orders and case history, matched reliably by the 16-character CNR.
- Official API access: restricted to government and institutional litigants; businesses use private providers built on public data.
01What a court data API is
API stands for application programming interface. In plain terms, it is a doorway that lets one piece of software ask another for information and get a clean, structured answer back. A court data API is that doorway for Indian court information.
Instead of a person visiting the eCourts website, typing a case number, and reading the result off the screen, a system sends a request to the API with the case details and gets back a structured record: the parties, the stage, the next date, the orders, and so on. That record can then flow straight into a case management tool, a compliance dashboard, or an alert.
02eCourts and NJDG, the official sources
Most Indian court data traces back to two official systems run under the National Informatics Centre and the Department of Justice:
- eCourts Services: the portal and apps that let you look up case status, cause lists and orders for the computerised district and subordinate courts and the High Courts.
- National Judicial Data Grid (NJDG): a national database of cases, orders and judgments from the computerised courts, built mainly to monitor pendency and disposal.
The Supreme Court sits apart
The Supreme Court is not part of the eCourts project in the same way as the district and High Courts; it runs its own case information system. So a single court data source may not cover the Supreme Court the same way it covers the subordinate courts. For how different providers compare, see the best court data and case-tracking APIs in India.
03What an API can pull
A court data API built on these sources can typically expose:
- Case status: the parties, the court, the stage, the filing and registration details, and whether the case is pending or disposed.
- Next hearing date: the date the case is next listed.
- Cause lists: the daily list of cases set down before a court or judge.
- Orders and judgments: links to or text of the orders passed in the case.
- History: the record of past hearings and what happened on each date.
The key to using any of this is the CNR, the Case Number Record, a unique 16-character number that identifies a case across the eCourts system. Matching the right case by CNR, rather than by a common party name alone, is what keeps the data reliable.
04How current the data is
Court data is only as useful as it is fresh. The underlying court records update as courts enter data: a new filing, a hearing marked, an order uploaded. An API that mirrors this can be close to current, but there is always some lag between what happens in court and what appears in the record, and between the record and any copy an API keeps.
For enterprise use this matters. A check run on stale data can miss a case filed last week or a hearing listed tomorrow. A serious court data source should be transparent about where its data comes from and how often it refreshes, rather than implying it is always perfectly live.
05Who can access the official APIs
The official NJDG open APIs are not a free public developer service. They were introduced in 2020 and access is restricted, mainly to central and state government bodies and institutional litigants, who are given a department identifier and an access key, in line with India’s National Data Sharing and Accessibility Policy. The aim is monitoring pendency and compliance, not general commercial resale.
For everyone else, the public routes are the eCourts portal, its mobile apps, court kiosks, and the SMS and email alert services. Private court data APIs fill the gap for businesses by building their own structured access on top of the public information, which is why coverage, freshness and matching quality vary so much between providers.
06Legitimate enterprise uses
Used responsibly, court data APIs power several real business needs:
- Litigation monitoring: watching a portfolio of cases for new hearings and orders, so legal teams are not caught out. See litigation monitoring by API.
- Onboarding and underwriting checks: banks and NBFCs screening a borrower or vendor for pending litigation before a decision.
- Case management: pulling status and next dates straight into a firm’s own system instead of checking court sites by hand.
- Research and analytics: studying pendency, outcomes and timelines across courts.
For the developer side of wiring one of these into your systems, see how to integrate a case status API, and for the broader court records angle, what a court records API does.
07Where Claw fits
Claw is an all-in-one legaltech platform for Indian advocates, law firms, and corporate legal teams, combining AI-based case search, an AI legal assistant (Legal GPT), case management, and compliance automation across all Indian courts and tribunals.
For court data specifically, Claw works at scale. Its case tracking covers 9,102 courts, benches and forums, including district courts and tribunals, so a portfolio of matters can be followed in one place rather than across dozens of court websites. Its case search covers 30 crore+ judgments, with Supreme Court decisions from 1950 and High Court decisions from 1990, returning results in under 5 seconds. Claw does not use your case documents to train its AI models, which matters when sensitive litigation data flows through an API.
Create a FREE Claw account to try case search across Indian courts before you evaluate any API. To compare providers, see the best court data and case-tracking APIs in India.
08Sources and further reading
- eCourts (official court data portal): ecourts.gov.in
- National Judicial Data Grid: njdg.ecourts.gov.in
- Open Government Data Platform India: data.gov.in
- Claw: clawlaw.in
This is general information, not legal or technical advice. API coverage, fields and access rules change, so confirm them with the official sources and each provider before you build against them.
09Frequently asked questions
What is a court data API in India?
It is a structured way to pull Indian court information, such as case status, next hearing dates, cause lists and orders, into your own software automatically, instead of reading it off court websites by hand.
What data do eCourts and NJDG expose?
eCourts Services exposes case status, cause lists and orders for the computerised district and subordinate courts and High Courts. The National Judicial Data Grid is a national database of cases, orders and judgments built mainly to monitor pendency and disposal.
Can anyone use the official NJDG API?
No. The official NJDG open APIs introduced in 2020 are restricted, mainly to central and state government bodies and institutional litigants, who get a department identifier and access key. Everyone else uses the public eCourts portal, apps, kiosks and alerts, or a private court data provider built on public information.
What is a CNR number?
The CNR, or Case Number Record, is a unique 16-character number that identifies a case across the eCourts system. Matching cases by CNR, rather than by a common party name alone, is what keeps court data reliable.
How current is court data from an API?
It depends on the provider. The underlying records update as courts enter data, but there is always some lag between what happens in court and what appears in the record, and between the record and any copy an API keeps. A good provider is transparent about its source and refresh cadence.
What do enterprises use court data APIs for?
Litigation monitoring across a portfolio, onboarding and underwriting checks for pending cases, feeding case status and next dates into case management tools, and research into pendency and outcomes. The Supreme Court sits outside the main eCourts system, so confirm coverage for it separately.