ECourts Case Number Search

Overview

The eCourts Case Number Search category provides a structured suite of APIs that enable developers to search and retrieve detailed court case information from India's eCourts platform using case numbers. These APIs follow a hierarchical lookup workflow — guiding users through the Indian judicial structure from state to district to court complex to case type — before performing a precise case search. This systematic approach ensures accurate jurisdiction targeting and returns comprehensive case records including filing details, hearing history, party information, FIR details, applicable laws, and judicial orders.

Whether you are building legal tech platforms, compliance verification systems, or due diligence tools, this category offers a complete, end-to-end solution for programmatic access to India's vast district court case database.

Category Details

Parent Category: eCourts
APIs in this category: Get State List, Get District List, Get Court Complex List, Get Case Type List, Case Number Search

Key Capabilities

Main Functionality

This category enables programmatic access to India's eCourts district court system through a structured, cascading lookup workflow. Developers can enumerate all supported jurisdictions (states, districts, court complexes, case types) and then perform targeted case searches that return rich, structured data — including case status, parties, advocates, acts & sections, FIR details, complete hearing chronology, interim orders, final orders, and transfer details.

Jurisdiction Enumeration

Retrieve the full hierarchy of Indian judicial jurisdictions — from states and union territories, down to individual districts, court complexes, and case types. These lookup APIs provide the exact, validated input values required for the case search, eliminating guesswork and ensuring request accuracy.

Precise Case Retrieval

Search for a specific court case by providing the case type, case number, and year within a defined court complex. The API returns a comprehensive case record with filing and registration details, CNR number, current status, nature of disposal, and the presiding judge information.

Deep Case Intelligence

Go beyond basic case metadata to access the full hearing history with dates and purposes, all applicable acts and sections, linked FIR details (number, police station, year), interim and final court orders, and any case transfer records — all in a single API response.

Common Use Cases

Legal & LegalTech

Banking & Financial Services

HR & Background Verification

Case Tracking & Monitoring: Law firms and legal departments can automate the tracking of active cases across multiple courts, receiving structured data on hearing dates, case status changes, and judicial orders without manual eCourts portal visits.

Litigation Analytics: Legal analytics platforms can aggregate case data across jurisdictions to identify trends in case disposal times, common acts invoked, and judge-wise hearing patterns for strategic legal planning.

Client Case Portfolio Management: Build client dashboards that display real-time status of all ongoing cases, upcoming hearing dates, and historical case progression timelines.

Integration Considerations

Best Practices

Always use the lookup APIs sequentially: Follow the State → District → Court Complex → Case Type workflow. Use the exact values returned by each lookup API as inputs for the next step and the final search. Do not hardcode or guess jurisdiction values.

Cache lookup responses appropriately: State and district lists change infrequently. Cache these responses locally (with a reasonable TTL of 24–48 hours) to reduce API calls and improve application performance. Court complex and case type lists may change more frequently and should be refreshed periodically.

Implement robust error handling: Handle all possible error responses (401, 404, 422, 500) gracefully. Provide clear user feedback when a case is not found or when input parameters are invalid.

Trim and validate user inputs: Ensure that parameters like case_number and year do not contain leading/trailing whitespace or non-numeric characters before sending requests to the API.

Store the client_id from search responses: The client_id returned in the case search response serves as a unique transaction identifier. Store it for audit trails, debugging, and support inquiries.

Important Limitations

District Courts Only: This API suite covers Indian district and subordinate courts available on the eCourts platform. High Court and Supreme Court cases are not included in this category.

Data Availability: Case data availability depends on the digitization status of the respective court complex on the eCourts platform. Some older cases or courts with delayed digitization may not return results.

Exact Match Required: The case search requires an exact match of case type, case number, and year. Partial or fuzzy searches are not supported.

Rate Limits Apply: API calls are subject to rate limits based on your subscription plan. Implement appropriate throttling and retry logic with exponential backoff.

Real-Time Dependency: Case data is sourced from the eCourts platform and reflects the latest available information at the time of the query. There may be a slight delay between court proceedings and data availability on eCourts.

How APIs in this Category Work Together

The five APIs in this category are designed to work as a sequential, cascading pipeline. Each lookup API feeds validated input values into the next, culminating in a precise case search. This architecture mirrors the hierarchical structure of India's judicial system and ensures that every search request targets an exact, valid court jurisdiction.

Key Integration Patterns:

Get State List + Get District List: First retrieve the list of all available states, then pass the selected state name to fetch all districts within that state. This powers the first two levels of a jurisdiction selection UI.

Get District List + Get Court Complex List + Get Case Type List: After selecting a district, fetch the court complexes within it, and then retrieve the available case types for the selected court complex. This three-step chain completes the full jurisdiction and case categorization setup.

Get Case Type List + Case Number Search: Once all jurisdiction parameters and the case type are established, combine them with the user-provided case number and year to execute the final case search and retrieve comprehensive case details.

In a typical end-to-end workflow, a developer would first call Get State List to populate a state dropdown. Upon state selection, Get District List is called to populate the district dropdown. Selecting a district triggers Get Court Complex List to display available courts. Choosing a court complex fires Get Case Type List to show all case categories handled by that court. Finally, the user enters a case number and year, and the application calls Case Number Search with all collected parameters to retrieve the full case record — including filing dates, CNR number, case status, party and advocate details, applicable acts, FIR information, complete hearing history, and all judicial orders.

The eCourts Case Number Search category is part of the broader eCourts parent category, which encompasses multiple approaches to searching and retrieving court case information from India's district court system. Depending on the available case identifiers, developers may choose different search strategies offered by sibling categories.

Related Categories include:

eCourts CNR Search: Search for court cases using the unique CNR (Case Number Record) number, which is a universal identifier assigned to every case in the eCourts system. Ideal when the CNR number is already known, bypassing the need for jurisdiction-based lookups.

eCourts Party Name Search: Search for court cases by the name of a petitioner or respondent within a specified jurisdiction. Useful for background verification and due diligence when only the individual's or entity's name is available.

eCourts FIR Search: Search for court cases linked to a specific FIR (First Information Report) number. Valuable when tracking the judicial progression of a police-filed case from FIR to court proceedings.

Together, these related categories provide a comprehensive toolkit for court case discovery and retrieval. A legal tech platform might use Party Name Search for initial screening, Case Number Search or CNR Search for detailed case tracking, and FIR Search to connect police records with court proceedings — delivering a complete litigation intelligence solution across India's district court system.

Overview#

Key Capabilities#

Common Use Cases#

Integration Considerations#

How APIs in this Category Work Together#

Related Categories#

Overview

Key Capabilities

Common Use Cases

Integration Considerations

How APIs in this Category Work Together

Related Categories