Ecourts CNR Search

Endpoint Overview

POST /api/v1/ecourts/ecourt-cnr-search

Description

The Ecourts CNR Search API allows you to retrieve comprehensive case information from the Indian eCourts system using a CNR (Case Number Record) number. This API provides detailed information about court cases including case details, current status, involved parties, hearing dates, and case history. It serves as a digital gateway to access court case information efficiently without manual court visits.

Key Benefits

Instant access to comprehensive case information using just the CNR number

Detailed visibility into case status, history, and scheduled hearings

Access to petitioner, respondent, and advocate information for complete case context

Retrieve official court records including interim orders and judgments

Use Cases

Legal Services

Financial Services

Corporate Compliance

Law firms can quickly retrieve case details for client consultations

Legal research teams can access case information for precedent analysis

Case management systems can be updated with latest hearing information

Technical Implementation

Authentication

All API requests require authentication using a JWT Bearer token. Authentication follows these steps:

Obtain API Credentials: Register with Surepass to receive your API key.

Generate JWT Token: Use your API key to generate a JWT token.

Include in Requests: Add the token to the Authorization header as Bearer TOKEN.

Different authentication tokens are used for sandbox and production environments:

Sandbox: https://sandbox.surepass.io

Production: https://kyc-api.surepass.io

Request Parameters

Request Headers

Header	Required	Description
Authorization	Yes	Bearer token for authentication (JWT format)
Content-Type	Yes	Must be set to `application/json`

Request Body

Parameter	Type	Required	Description
cnr_number	String	Yes	The CNR (Case Number Record) number of the court case to search for

Example Request

{
    "cnr_number": "CHCH010050522023"
}

Process Response

Response Parameters

Parameter	Type	Description
data	Object	Contains the response data
data.client_id	String	Unique identifier for the client request
data.cnr_number	String	The CNR number that was searched
data.cnr_details	Object	Comprehensive details about the case
status_code	Integer	HTTP status code of the response
success	Boolean	Indicates if the request was successful
message	String	Response message
message_code	String	Code indicating the response status

CNR Details Object Structure

Field	Type	Description
case_details	Object	Basic case information including type, filing and registration details
case_status	Object	Current status of the case including hearing dates and stage
petitioner_and_advocate_details	Object	Information about the petitioner and their advocate
respondent_and_advocate_details	Array	List of respondents in the case
act_details	Array	Legal acts and sections under which the case is filed
subordinate_court_information_details	Object	Information about lower court proceedings if applicable
case_history_details	Array	Historical record of case hearings and proceedings
interim_orders_details	Array	Details of any interim orders issued
final_orders_and_judgements_details	Array	Details of final judgments if available
case_transfer_and_establishment_details	Array	Information about case transfers between courts
process_details	Array	Details about various processes in the case lifecycle

Example Successful Response

{
    "data": {
        "client_id": "ecourt_cnr_search_hRguiuMgammwvWcqpuom",
        "cnr_number": "CHCH0100123456789",
        "cnr_details": {
            "case_details": {
                "case_type": "CRA",
                "filing_number": "192/2000",
                "filing_date": "2000-00-06",
                "registration_number": "3000/2000",
                "registration_date": "2000-00-07"
            },
            "case_status": {
                "first_hearing_date": "2000-00-07",
                "next_hearing_date": "2000-11-02",
                "case_stage": "Defence evidence ",
                "court_number_and_judge": "District Judge",
                "decision_date": null,
                "nature_of_disposal": ""
            },
            "petitioner_and_advocate_details": {
                "petitioner": "K AGGARWAL",
                "advocate": "V Jain"
            },
            "respondent_and_advocate_details": [
                "INCOME  OFFICER",
                "UNION TERRITORY",
                "CORPORATION ITD",
                "N AGGARWAL",
                "P AGGARWAL",
                "P SINGH"
            ],
            "act_details": [
                {
                    "under_act": "Cr. P.C.",
                    "under_section": "374"
                }
            ],
            "subordinate_court_information_details": {
                "case_number_and_year": "0001000 -  2019",
                "case_decision_date": "2000-00-08"
            },
            "case_history_details": [
                {
                    "judge": "District Judge",
                    "business_on_date": "2000-00-07",
                    "hearing_date": "2000-00-02",
                    "purpose_of_hearing": "Defence evidence"
                }
            ],
            "interim_orders_details": [
                {
                    "order_number": "1",
                    "order_date": "2000-00-07"
                }
            ],
            "final_orders_and_judgements_details": [],
            "case_transfer_and_establishment_details": [],
            "process_details": [
                {
                    "process_id": "PCHCH01000987654000_1_1",
                    "process_data": "2000-07-00",
                    "process_title": "Notice to Respondent."
                },
                {
                    "process_id": "PCHCH01000987654000_1_2",
                    "process_data": "2000-07-00",
                    "process_title": "Notice to Respondent."
                },
                {
                    "process_id": "PCHCH01000987654000_1_3",
                    "process_data": "2000-07-00",
                    "process_title": "Notice to Respondent."
                },
                {
                    "process_id": "PCHCH01000987654000_1_4",
                    "process_data": "2000-07-00",
                    "process_title": "Notice to Respondent."
                },
                {
                    "process_id": "PCHCH01000987654000_1_5",
                    "process_data": "2000-07-00",
                    "process_title": "Notice to Respondent."
                },
                {
                    "process_id": "PCHCH01000987654000_1_6",
                    "process_data": "2000-07-00",
                    "process_title": "Notice to Respondent."
                },
                {
                    "process_id": "PCHCH01000987654000_2_1",
                    "process_data": "2000-07-00",
                    "process_title": "Docket Calling."
                }
            ]
        }
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Invalid CNR Number

CNR Not Found

Authentication Error

{
    "status_code": 400,
    "success": false,
    "message": "Invalid CNR number format",
    "message_code": "invalid_cnr_format"
}

The CNR number provided doesn't match the required format or pattern.

Integration Best Practices

Security Recommendations

Store JWT tokens securely and never expose them in client-side code

Implement proper error handling to avoid exposing sensitive information

Set appropriate request timeouts to handle potential delays in court system responses

Implement rate limiting in your application to prevent abuse of the API

User Experience Guidelines

Provide clear validation for CNR number format before submission

Display a loading indicator during API calls as court data retrieval may take time

Format dates in a user-friendly manner (the API returns YYYY-MM-DD format)

Implement proper pagination when displaying multiple records (like case history)

Provide contextual help for legal terminology to assist non-legal users

Code Samples

cURL

Python

Node.js

Related APIs

Ecourts Case Status API - Retrieve case status information using different parameters

Ecourts Cause List API - Get court schedules and case listings for specific dates

Ecourts Judge Information API - Access information about judges presiding over cases

Compliance and Legal Considerations

The data retrieved through this API is sourced from public court records. However, usage of this data may be subject to legal restrictions in certain jurisdictions. Ensure compliance with local data protection laws when storing or processing case information, especially when it contains personal data of involved parties. The information should be used for legitimate legal, business, or research purposes only.

{ "data": { "client_id": "ecourt_cnr_search_hRguiuMgammwvWcqpuom", "cnr_number": "CHCH0100123456789", "cnr_details": { "case_details": { "case_type": "CRA", "filing_number": "192/2000", "filing_date": "2000-00-06", "registration_number": "3000/2000", "registration_date": "2000-00-07" }, "case_status": { "first_hearing_date": "2000-00-07", "next_hearing_date": "2000-11-02", "case_stage": "Defence evidence ", "court_number_and_judge": "District Judge", "decision_date": null, "nature_of_disposal": "" }, "petitioner_and_advocate_details": { "petitioner": "K AGGARWAL", "advocate": "V Jain" }, "respondent_and_advocate_details": [ "INCOME OFFICER", "UNION TERRITORY", "CORPORATION ITD", "N AGGARWAL", "P AGGARWAL", "P SINGH" ], "act_details": [ { "under_act": "Cr. P.C.", "under_section": "374" } ], "subordinate_court_information_details": { "case_number_and_year": "0001000 - 2019", "case_decision_date": "2000-00-08" }, "case_history_details": [ { "judge": "District Judge", "business_on_date": "2000-00-07", "hearing_date": "2000-00-02", "purpose_of_hearing": "Defence evidence" } ], "interim_orders_details": [ { "order_number": "1", "order_date": "2000-00-07" } ], "final_orders_and_judgements_details": [], "case_transfer_and_establishment_details": [], "process_details": [ { "process_id": "PCHCH01000987654000_1_1", "process_data": "2000-07-00", "process_title": "Notice to Respondent." }, { "process_id": "PCHCH01000987654000_1_2", "process_data": "2000-07-00", "process_title": "Notice to Respondent." }, { "process_id": "PCHCH01000987654000_1_3", "process_data": "2000-07-00", "process_title": "Notice to Respondent." }, { "process_id": "PCHCH01000987654000_1_4", "process_data": "2000-07-00", "process_title": "Notice to Respondent." }, { "process_id": "PCHCH01000987654000_1_5", "process_data": "2000-07-00", "process_title": "Notice to Respondent." }, { "process_id": "PCHCH01000987654000_1_6", "process_data": "2000-07-00", "process_title": "Notice to Respondent." }, { "process_id": "PCHCH01000987654000_2_1", "process_data": "2000-07-00", "process_title": "Docket Calling." } ] } }, "status_code": 200, "success": true, "message": "Success", "message_code": "success" }

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Ecourts CNR Search

Ecourts CNR Search#

Description#

Use Cases#

Technical Implementation#

Request Headers#

Request Body#

Example Request#

Response Parameters#

CNR Details Object Structure#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses

Ecourts CNR Search

Description

Use Cases

Technical Implementation

Request Headers

Request Body

Example Request

Response Parameters

CNR Details Object Structure

Example Successful Response

Possible Error Responses

Integration Best Practices

Code Samples