Court Records API in India: What It Is and How It Works

Explainer · Legal Data & APIs

Updated for 2026 · Claw Editorial

If you need to check the status of one case, the eCourts website works fine. If you need to check the status of five hundred cases every day, or screen every new borrower and vendor for pending litigation, a human clicking through court websites does not scale. That is the problem a court records API solves. This page explains what a court records API is, how it actually works in the Indian context, and who ends up needing one.

01Why court records are hard to access at scale

India does not have one single, queryable database of every pending case. It has the eCourts Services portal run by the National Informatics Centre, the National Judicial Data Grid (NJDG) that shows pendency and disposal statistics, and dozens of individual High Court and tribunal websites, each with its own search screen. None of this was built for a computer program to call. It was built for a person to type a CNR number or a party name into a search box and read the result.

That is fine for one case, not for hundreds

A single advocate checking one client’s case can do that manually. It breaks down the moment a business needs to check litigation status for a large number of people or companies at once, and keep those checks current every day. A bank screening loan applicants, an NBFC doing pre-disbursement checks, or a law firm tracking a docket of a few hundred matters cannot afford someone refreshing court websites by hand.

Data is scattered and inconsistently formatted

Case data that does exist online is split across the Supreme Court, 25 High Courts, district courts, and tribunals such as NCLT, NCLAT, CAT, and ITAT, each publishing in its own format. Party names are transliterated differently court to court, case numbers follow different conventions, and orders are often scanned PDFs rather than structured text. Pulling all of this into one usable, current record is the real engineering problem.

02What a court records API is

A court records API is a programmatic interface, usually a REST API, that lets a piece of software request court data (case status, orders, hearing dates, cause lists, or judgements) and get back a structured, machine-readable answer, instead of a human reading a web page.

In practice, most court records APIs available in India today are not run by the government itself. The official eCourts Services portal is a public search tool for people, not a general-purpose developer API. What exists instead is a layer of private vendors and legaltech platforms that source data from eCourts, the NJDG, and individual court websites, clean and structure it, and expose it as an API that a bank, insurer, law firm, or software product can call directly.

The output of a good court records API typically includes case status and stage, parties and advocates on record, the next hearing date, orders and judgements (often as a certified or scanned document), and case history. Some APIs also return cause list entries, so a system can flag which of its tracked matters are listed for hearing on a given day.

03How a court records API actually works

Four things happen behind a single API call, and the quality of each one decides whether the data you get back is actually usable.

1. Sourcing the data

The provider pulls data from the eCourts Services portal, the NJDG, and, where needed, individual High Court, Supreme Court, and tribunal websites, since coverage and update frequency vary by court. This has to run continuously, because a case that was “pending” yesterday can be disposed, adjourned, or transferred today.

2. Matching and normalising

Indian names get transliterated inconsistently (a party might appear as three different spellings across three courts), and case numbering conventions differ by court. A usable API has to apply name-tolerant matching, meaning it can still find the right case even when the spelling is slightly off, and normalise everything into one consistent format.

3. Structuring the output

Raw court data, especially orders, often exists only as a scanned PDF. Turning that into something a system can act on, such as the next hearing date, the outcome of an order, or a searchable case history, is where AI-based reading of documents adds real value over a plain database lookup.

4. Delivering it

The finished data is served back over a REST API, typically queryable by CNR number, case number, party name, or advocate name, with structured JSON as the response. Some providers also support webhooks or scheduled alerts, so a subscribing system is notified automatically when a tracked case has a new order or hearing, rather than having to poll for updates.

A court records API is only as reliable as its weakest data source and its name matching. Anyone can return a JSON response. Returning the right case, every time, is the hard part.

04Who actually uses a court records API

A court records API is infrastructure, not a finished product, so it tends to sit quietly inside someone else’s workflow. The main users are:

• Legal tech and litigation tracking platforms: case tracking software needs a live data feed under the hood to show auto-updated case status, cause lists, and hearing alerts instead of asking a paralegal to check manually.
• Banks and NBFCs: pre-loan and pre-disbursement checks often include a litigation or criminal background scan on the borrower or guarantor, run through an API rather than a manual search, so it can happen at loan-application speed.
• Background verification and legal due-diligence providers: firms in this space build litigation checks into employee and vendor screening. For example, Perfios describes aggregating data from thousands of courts and tribunals into a single litigation background-check report for exactly this use case.
• Insurance underwriters and claims teams: litigation history can be a relevant input at underwriting or during a claims investigation.
• Corporate legal and compliance teams: a company with matters spread across several entities and states needs one automated feed to know when any of them moves, rather than checking dozens of court websites.

05What to check before you pick one

Not all court records APIs cover the same ground, and the differences matter more than they first appear.

• Court and tribunal coverage: does it reach the Supreme Court, the specific High Courts, district courts, and tribunals (NCLT, NCLAT, CAT, ITAT, and so on) you actually need, or only a subset?
• How current the data is: daily refresh is very different from real-time, and for pre-hearing alerts or credit decisions, staleness is a real risk.
• Name-matching quality: a system that misses a case because of a spelling variation gives you false confidence, which is worse than an obvious gap.
• Depth of output: case status alone is not the same as structured orders, judgement text, or an AI summary of what an order actually says.
• Data handling and compliance: since these checks often involve personal data on borrowers, employees, or vendors, understand how the provider stores and handles data under India’s DPDP framework before integrating.
• Whether it is free or paid: the official government sources are free but built for manual, one-case-at-a-time lookups, not scale or integration. The tradeoffs between free government access and a paid vendor API are covered in our guide to free versus paid legal software in India.

It is also worth checking whether a platform’s underlying data is actually built for India. A generic case-management or legal-workflow tool built for another country’s court system usually cannot plug into Indian court data at all. See how international legal software compares to India-built platforms if you are weighing that choice.

06Where 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.

Claw has a live API for programmatic access to court and litigation data, so a team can pull case and court information into its own systems rather than only using Claw’s own interface. This sits on top of Claw’s existing data: case search across 25 High Courts (1980 to 2026) and the Supreme Court (1950 to 2026), covering 1.5 billion plus case records, and case tracking across 8200 plus courts including tribunals and district courts nationwide.

For a business deciding whether to build a court-data integration on eCourts data directly or plug into a provider that has already solved sourcing, matching, and structuring, that combination of broad court coverage plus an API is the relevant starting point to evaluate.

07Sources and further reading

Official and reference sources used for this explainer:

• eCourts Services (NIC), the official Indian court case-status portal: ecourts.gov.in
• National Judicial Data Grid (NJDG), the official pendency and disposal data grid: njdg.ecourts.gov.in
• Claw: clawlaw.in

This page describes the category in general terms. Any specific vendor’s coverage, pricing, or technical specifications should be confirmed directly with that vendor before you rely on them.

08Frequently asked questions