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"
import requests
import json
url = "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"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN (JWT)",
"x-api-key": "YOUR_API_KEY"
}
response = requests.get(url, headers=headers)
print(response.json())
const response = await fetch("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", {
method: "GET",
headers: {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN (JWT)",
"x-api-key": "YOUR_API_KEY"
}
});
const data = await response.json();
console.log(data);
package main
import (
"fmt"
"net/http"
)
func main() {
req, err := http.NewRequest("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", nil)
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("Authorization", "Bearer YOUR_API_TOKEN (JWT)")
req.Header.Set("x-api-key", "YOUR_API_KEY")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
fmt.Println("Response Status:", resp.Status)
}
require 'net/http'
require 'json'
uri = URI('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')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Get.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN (JWT)'
request['x-api-key'] = 'YOUR_API_KEY'
response = http.request(request)
puts response.body
{
"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"
}
]
}
{
"code": 200,
"timestamp": 1767173627936,
"transaction_id": "b10ead4473ff4283ac9ea40464fbb6c0",
"sub_code": "IN_PROGRESS",
"message": "Request processing is in progress."
}
{
"detail": "Inactive client_id"
}
{
"detail": "Not authenticated"
}
{
"detail": "Not a valid token"
}
{
"code": 422,
"timestamp": 1767177410430,
"transaction_id": "0acca1189f4e4a729d2edf8077e529e2",
"sub_code": "INVALID_REQUEST_ID",
"message": "Invalid Request ID"
}
{
"detail": "Internal Server Error"
}
/v1/background-verification/court-record-check/{transaction_id}ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .
The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.
Transaction ID returned while creating the court/FIR record check request
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.
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.
Party type in the case. Allowed values: RESPONDENT, PETITIONER. Multiple values can be passed as a comma-separated string.
Category of court case. Allowed values: CIVIL, CRIMINAL. Multiple values can be passed as a comma-separated string.
Current status of the case. Allowed values: PENDING, DISPOSED. Multiple values can be passed as a comma-separated string.
Whether state-level matching is applied. Allowed values: true or false.
Whether district-level matching is applied. Allowed values: true or false.
Jurisdiction coverage for search. Allowed values: NEAREST_DISTRICTS, STATE, DISTRICT, PAN_INDIA. Multiple values can be passed as a comma-separated string.
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
Bearer token (JWT). ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .
API Key for authentication. The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.
Path Parameters
Transaction ID returned while creating the court/FIR record check request
Query Parameters
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.
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.
Party type in the case. Allowed values: RESPONDENT, PETITIONER. Multiple values can be passed as a comma-separated string.
Category of court case. Allowed values: CIVIL, CRIMINAL. Multiple values can be passed as a comma-separated string.
Current status of the case. Allowed values: PENDING, DISPOSED. Multiple values can be passed as a comma-separated string.
Whether state-level matching is applied. Allowed values: true or false.
Whether district-level matching is applied. Allowed values: true or false.
Jurisdiction coverage for search. Allowed values: NEAREST_DISTRICTS, STATE, DISTRICT, PAN_INDIA. Multiple values can be passed as a comma-separated string.
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
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.
Last updated 4 weeks ago
Built with Documentation.AI