API Documentation
v4.0https://webapi.ecourtsindia.com|JSON|Bearer Token Auth|11 EndpointsAuthentication
All API requests (except Court Structure) require Bearer token authentication. Include your API token in the Authorization header.
eci_live_All successful responses follow this structure:
{
"data": { ... },
"meta": {
"requestId": "req_abc123xyz"
}
}Security Warning
- Keep your API token confidential. Do not expose it in client-side code.
- Never commit tokens to version control or share in public repositories.
- If compromised, contact us immediately to regenerate your token.
Connect AI agents directly via Model Context Protocol:
GET /api/CauseList/court-structure/*— States, districts, complexes, courtsGET /api/partner/enums— Live enum reference
Free but auth required: GET /api/partner/causelist/available-dates — No credits charged, but Bearer token is required.
Core Concepts
Key concepts for working with the eCourts API.
A CNR is the unique 16-character identifier for every case in the eCourts system.
[A-Z]{4}\d{12}DLHC010351552024 → Delhi HC, case 035155, filed 2024HCBM050012342023 → Bombay HC (Kolhapur), case 001234, filed 2023Supreme Court of India (SC)
├── High Courts (37 across states/UTs)
│ ├── Original Jurisdiction
│ └── Appellate Jurisdiction
├── District Courts
├── National Company Law Tribunal (NCLT)
├── National Company Law Appellate Tribunal (NCLAT)
└── Specialized TribunalsA cause list is the daily schedule of cases to be heard in a specific courtroom. Each entry shows the case number, parties, assigned judge, expected hearing time, and case status. Use the Cause List Search endpoint to query schedules across courts.
Most authenticated endpoints consume credits per request. Court structure endpoints and enum reference are free. Check your account balance and see the pricing page for details.
API Endpoints
11 endpoints covering case data, orders, cause lists, and court structure across all Indian courts.