Court Record CheckCreate

Court Record Check — Background Screening

Screen individuals against court records across Indian courts. Check for civil, criminal, and tribunal cases by name and address.

curl -X POST "https://production.deepvue.tech/v1/background-verification/court-record-check" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN (JWT)" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
  "name": "John Doe",
  "father_name": "John Doe",
  "dob": "example_string",
  "type": "example_string",
  "address": "123 Main St"
}'
{
  "code": 201,
  "timestamp": 1766168439528,
  "transaction_id": "f0be2d85823e46e38b5784340a36881d",
  "sub_code": "IN_PROGRESS",
  "message": "Request processing is in progress."
}
POST
/v1/background-verification/court-record-check
POST
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.
Content-Typestring
Required

The media type of the request body

Options: application/json
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.

Responses

Overview

This API enables you to submit background verification requests against court records. You can use this endpoint for compliance and due diligence purposes by screening individuals against court case databases.

The API operates asynchronously. When you submit a request, you receive an immediate acknowledgment with a transaction ID and an IN_PROGRESS status (HTTP 201). Verification results are processed in the background and can be retrieved separately using the transaction ID.

The request requires the individual's name and address as mandatory fields. You can optionally include the father's name, date of birth, and case type to refine the search.