Court Record CheckResult

Get Court Record Check Result

Retrieve the result of an asynchronous court record check.

curl -X GET "https://production.deepvue.tech/v1/background-verification/court-record-check/example_string?name_match_type=EXACT_MATCH,EXACT_FUZZY&father_match_type=example_string&type=example_string&case_category=example_string&case_status=example_string&state_match=true&dist_match=true&jurisdiction_type=example_string&algo_risk=example_string" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN (JWT)" \
  -H "x-api-key: YOUR_API_KEY"
{
  "code": 200,
  "timestamp": 1767173359430,
  "transaction_id": "6b65f29500aa4ec0967581ff8dedd097",
  "sub_code": "SUCCESS",
  "message": "Processing done",
  "data": [
    {
      "live_case_url": "https://services.ecourts.gov.in/ecourtindia_v6/",
      "archive_case_url": "https://production.deepvue.tech/v1/background-verification/court-record-check/archive?token=gAAAAABpgLrCpv_eD00etRG5jxh38ISU3Yf4SYySdYuVy2_x5uW_zE8pneoCwnKxmFRtpN2MFxU6AMiXd8ynnY6g_Kohx-0BfbCvHrTEPGD-ZB6Tn-Q-wdyUZ0fAh2eMTTZEKbTX7s0PtUro5ombKqzuMFiuKit0JVsytdAH6cW3arqXoE4_VQPVFmNXrma0eV_Uyv9EriGQIbtq5Gf3GnYFZ1kXV_lH-2IiY9_nPxEkw05RApz872jkrpw6ELV3wTarv1rtdxtZ&exp=1772636098&sig=4a6f5403303cd9c94ce9efc89b1fc0747580a241d80904b5f693f0205b0d83f9",
      "case_no": "202300001112019",
      "case_year": "2019",
      "case_status": "Disposed",
      "case_category": "criminal",
      "court_name": "District and session Court, Bilaspur",
      "state_name": "Chhattisgarh",
      "district_name": "Bilaspur",
      "name": "VIJAY KUMAR MAHAN",
      "father_name": "",
      "score": 95,
      "source": "ecourt"
    }
  ]
}
GET
/v1/background-verification/court-record-check/{transaction_id}
GET
Bearer Token (JWT)
Bearer Tokenstring
Required

ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .

ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .
API Key (header: x-api-key)
x-api-keystring
Required

The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.

The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.
path
transaction_idstring
Required

Transaction ID returned while creating the court/FIR record check request

query
name_match_typestring

Matching logic used for name comparison. Allowed values: EXACT_MATCH, EXACT_FUZZY, PARTIAL_EXACT, PARTIAL_FUZZY, NO_MATCH. Multiple values can be passed as a comma-separated string.

query
father_match_typestring

Matching logic used for father’s name comparison. Allowed values are the same as name_match_type. Multiple values can be passed as a comma-separated string.

query
typestring

Party type in the case. Allowed values: RESPONDENT, PETITIONER. Multiple values can be passed as a comma-separated string.

query
case_categorystring

Category of court case. Allowed values: CIVIL, CRIMINAL. Multiple values can be passed as a comma-separated string.

query
case_statusstring

Current status of the case. Allowed values: PENDING, DISPOSED. Multiple values can be passed as a comma-separated string.

query
state_matchboolean

Whether state-level matching is applied. Allowed values: true or false.

query
dist_matchboolean

Whether district-level matching is applied. Allowed values: true or false.

query
jurisdiction_typestring

Jurisdiction coverage for search. Allowed values: NEAREST_DISTRICTS, STATE, DISTRICT, PAN_INDIA. Multiple values can be passed as a comma-separated string.

query
algo_riskstring

Risk levels returned by algorithm. Allowed values: VERY_HIGH_RISK, HIGH_RISK, MEDIUM_RISK, LOW_RISK, VERY_LOW_RISK. Multiple values can be passed as a comma-separated string.

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token (JWT). ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .

header
x-api-keystring
Required

API Key for authentication. The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.

Path Parameters

transaction_idstring
Required

Transaction ID returned while creating the court/FIR record check request

Query Parameters

name_match_typestring

Matching logic used for name comparison. Allowed values: EXACT_MATCH, EXACT_FUZZY, PARTIAL_EXACT, PARTIAL_FUZZY, NO_MATCH. Multiple values can be passed as a comma-separated string.

father_match_typestring

Matching logic used for father’s name comparison. Allowed values are the same as name_match_type. Multiple values can be passed as a comma-separated string.

typestring

Party type in the case. Allowed values: RESPONDENT, PETITIONER. Multiple values can be passed as a comma-separated string.

case_categorystring

Category of court case. Allowed values: CIVIL, CRIMINAL. Multiple values can be passed as a comma-separated string.

case_statusstring

Current status of the case. Allowed values: PENDING, DISPOSED. Multiple values can be passed as a comma-separated string.

state_matchboolean

Whether state-level matching is applied. Allowed values: true or false.

dist_matchboolean

Whether district-level matching is applied. Allowed values: true or false.

jurisdiction_typestring

Jurisdiction coverage for search. Allowed values: NEAREST_DISTRICTS, STATE, DISTRICT, PAN_INDIA. Multiple values can be passed as a comma-separated string.

algo_riskstring

Risk levels returned by algorithm. Allowed values: VERY_HIGH_RISK, HIGH_RISK, MEDIUM_RISK, LOW_RISK, VERY_LOW_RISK. Multiple values can be passed as a comma-separated string.

Responses

codeinteger
timestampinteger
transaction_idstring
sub_codestring
messagestring
dataarray

Overview

This API retrieves the status and results of a court record verification using the transaction ID obtained when you created the check request.

When processing is complete, the response includes matching court case records with details such as case number, year, status, category, court name, jurisdiction, and a confidence score indicating name match quality. If processing is still underway, the API returns an intermediate status, allowing you to retry later.

Filtering capabilities

You can filter results by multiple criteria:

  • Name matching logic -- exact, fuzzy, or partial variants
  • Father's name comparison -- various matching methods
  • Party type -- respondent or petitioner
  • Case classification -- civil or criminal
  • Disposition status -- pending or disposed
  • Geographic jurisdiction -- district, state, or nationwide
  • Risk assessment levels

The API accesses court records from eCourts infrastructure, providing both live case portals and archived case documentation through secure, tokenized URLs.

Was this page helpful?

Last updated 4 weeks ago

Built with Documentation.AI