Bulk ValidationsCIN

Bulk CIN Verification — Company Batch Check

Verify multiple Corporate Identification Numbers in one batch. Get company names, registration status, and details at scale.

curl -X POST "https://production.deepvue.tech/v1/verification/mca/cin/batch?webhook_url=example_string" \
  -H "Authorization: Bearer YOUR_API_TOKEN (JWT)" \
  -H "x-api-key: YOUR_API_KEY" \
  --form batch_file=example_string
{
  "transaction_id": "51cd8b6ab36d46a98afb2f01e856e89a",
  "timestamp": 1732088933797,
  "code": 200,
  "message": "Batch Upload status fetched successfully",
  "sub_code": "SUCCESS",
  "data": {
    "request_id": "06d0d7c340ed460d96103aaa0b26f0de",
    "status": 200,
    "product_id": "",
    "message": "batch processing completed",
    "batch_output_file_url": "https://bulk-data-processing.s3.ap-south-1.amazonaws.com/upi-basic-batch-output-files/06d0d7c340ed460d96103aaa0b26f0de.csv"
  }
}
POST
/v1/verification/mca/cin/batch
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: multipart/form-data
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.

Query Parameters

Body

multipart/form-data

Responses

Overview

This API enables bulk verification of Corporate Identity Numbers (CIN) through an asynchronous processing model. You submit a CSV batch file containing CIN data, receive a request ID for tracking, and processing occurs in the background. Upon completion, verified results are sent to your configured webhook URL.

You can optionally specify a webhook_url parameter to override the default registered endpoint for a specific request.

Input files must contain fewer than 1,000 records.

The batch can return in two states: Completed (results available at the provided batch output file URL) or In Progress (still processing -- retry later or monitor the webhook).