judgments.ecourts.gov.in APIjudgments.ecourts.gov.in ↗
Search Indian court judgments from the eCourts platform. Filter by keyword, court type, and state. Returns case titles, judges, dates, and PDF paths.
curl -X GET 'https://api.parse.bot/scraper/31ab4ecd-705a-430c-822f-4066a14f34f0/search_judgments?query=property&start=0&court_type=2' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for judgments by keyword and court type. Handles captcha solving internally with multiple retry attempts. Returns paginated results with case details including case title, court, judge, dates, and PDF path. Due to image captcha solving, requests may occasionally fail and should be retried.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword (e.g. 'CGST', 'property', 'tax') |
| start | integer | Pagination offset (results returned in batches of 10) |
| court_code | string | High Court state code to filter results by state (e.g. 'DEL' for Delhi) |
| court_type | string | Court type: '1' for Supreme Court, '2' for High Court, '3' for SCR |
{
"type": "object",
"fields": {
"start": "integer current pagination offset",
"total": "integer total number of matching results",
"results": "array of judgment objects with case_title, judge, court, cnr, registration_date, judgment_date, disposal_nature, pdf_path",
"app_token": "string session token"
},
"sample": {
"data": {
"start": 0,
"total": 18500,
"results": [
{
"cnr": "JKHC010019192026",
"court": "High Court of Jammu and Kashmir",
"judge": "HON'BLE MR. JUSTICE SANJEEV KUMAR,HON'BLE MR. JUSTICE SANJAY PARIHAR",
"pdf_path": "court/cnrorders/kashmirhc/orders/JKHC010019192026_1_2026-05-05.pdf#page=&search=%20",
"case_title": "WP(C)/940/2026 of MANZOOR AHMAD BHAT Vs UNION TERRITORY OF J AND K AND OTHERS (FINANCE)",
"judgment_date": "05-05-2026",
"disposal_nature": "Dismised",
"registration_date": "28-04-2026"
}
],
"app_token": "REDACTED_SECRET"
},
"status": "success"
}
}About the judgments.ecourts.gov.in API
The eCourts Judgments API exposes a single search_judgments endpoint that queries the National Judicial Data Grid's judgments portal across Supreme Court, High Courts, and SCR courts. Each response returns up to 10 results per page with 8 structured fields per judgment, including case title, presiding judge, court name, CNR number, registration date, judgment date, disposal nature, and a direct PDF path to the full ruling.
What the API Returns
The search_judgments endpoint accepts a keyword query and returns paginated judgment records from judgments.ecourts.gov.in. Each result object includes case_title, judge, court, cnr (the unique Case Number Record identifier), registration_date, judgment_date, disposal_nature, and pdf_path. The total field in every response tells you the full result count so you can calculate how many pages exist before iterating.
Filtering and Pagination
You can narrow results by passing court_type — '1' for the Supreme Court, '2' for High Courts, or '3' for SCR — and court_code for a specific state (for example, 'DEL' for Delhi High Court). Pagination is controlled via the start offset; the platform returns results in batches of 10, so set start=10 for the second page, start=20 for the third, and so on. The response also returns an app_token session string that is used internally across paginated calls.
Reliability Considerations
The eCourts judgments platform uses image-based CAPTCHAs to gate search access. The API handles solving these automatically with multiple retry attempts, but individual requests can occasionally fail because of CAPTCHA variance. Build retry logic into any pipeline that needs consistent throughput, especially for bulk keyword searches or large offset ranges.
Official API Availability
The eCourts platform does not publish an official developer API for judgment search. Access through this Parse API is the practical way to integrate structured judgment data into applications without building and maintaining your own access layer.
- Pull all judgments mentioning 'CGST' to track GST-related High Court rulings for a tax compliance dashboard
- Aggregate case outcomes by
disposal_natureacross multiple keywords to analyze litigation trends in a practice area - Build a CNR-based case tracker by storing the
cnrfield and monitoring for new judgment dates on known cases - Download the full text of rulings via
pdf_pathto feed a legal research or document summarization pipeline - Filter by
court_codeandcourt_typeto scope alerts to a specific state High Court for regional legal monitoring - Extract
judgefield data across many search queries to map which judges are ruling on specific subject matters
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does judgments.ecourts.gov.in have an official developer API?+
What does the `search_judgments` endpoint return for each result?+
case_title, judge, court, cnr, registration_date, judgment_date, disposal_nature, and pdf_path. The pdf_path points to the actual ruling document. The top-level response also includes total (the full match count) and start (the current pagination offset).How should I handle occasional request failures?+
Can I retrieve the full text of a judgment through this API?+
pdf_path for each judgment but does not return extracted text content. The current endpoint covers structured case metadata and a link to the PDF. You can fork this API on Parse and revise it to add a document-fetch endpoint that retrieves and parses the PDF content.Can I filter results by a specific district court or tribunal?+
court_type parameter covers Supreme Court, High Courts, and SCR, and court_code filters to a state-level High Court. District courts and tribunal-level filtering are not exposed. You can fork this API on Parse and revise it to add those filtering parameters if your use case requires sub-High Court coverage.