Browse the knowledgebase
Category: Court Data Infrastructure
The data layer beneath Indian legal technology: APIs, government digitisation, NJDG, eCourts Mission Mode, and the structured datasets powering the next wave of legal products.
-
From Scrape to SLA: Why Your Team Should Move Off services.ecourts.gov.in to the eCourtsIndia API
Move off services.ecourts.gov.in scrapers: a migration guide to the eCourtsIndia API for BGV, fintech, KYC and CLM teams, with a five-step switch plan.
-
Building on Indian Court Data: A Developer’s Quickstart to the eCourtsIndia API
eCourtsIndia API quickstart for developers: auth, the first endpoints to call, page size, MCP OAuth and clean JSON over 32 crore+ Indian court records.
-
We Read 80 Delhi District Cause-List Items Over Two Days. Only One Was Listed for a Substantive Stage.
Delhi district court cause lists studied: of 80 items over two days, only one was listed for a substantive stage. What that says about hearing time.
-
MCP 101 for Legal Teams: The New Plumbing Between Claude, ChatGPT, and Indian Court Data
MCP for legal teams: connect Claude or ChatGPT to 32 crore+ Indian court records, cause lists, the statute book and the electoral roll through OAuth.
-
From PDFs to APIs: Why Indian Court Data Is Finally a Dataset, Not a Document
Indian court data as a dataset, not a document: how scanned PDFs and portal HTML become structured, queryable records behind an API for builders.
-
eCourts Phase III: What ₹7,210 Crore Will Build, and Where the Private Sector Steps In
eCourts Phase III: what the Rs 7,210 crore budget builds, from digitised records to cloud and virtual courts, and where private builders step in.
-
How India Digitised Its Courts, and What eCourts Was Never Built to Do
How India’s eCourts project computerised 18,735 district and subordinate courts in three phases, where Phase III stands in 2026, and what the official portal was never…