CDSL CAS Fetch - Step 1 (Request OTP)

Step 1 of 2: Request OTP for CDSL CAS fetch.

This endpoint:

1. Solves reCAPTCHA automatically (~15-20 seconds)
2. Submits login credentials to CDSL portal
3. Triggers OTP to user’s registered mobile number

After user receives OTP, call /v4/cdsl/fetch/{session_id}/verify to complete.

POST /v4/cdsl/fetch

CDSL CAS Fetch - Step 1 (Request OTP)

cURL

curl --request POST \
  --url https://api.casparser.in/v4/cdsl/fetch \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '
{
  "pan": "ABCDE1234F",
  "bo_id": "1234567890123456",
  "dob": "1990-01-15"
}
'

200

{
  "status": "success",
  "session_id": "550e8400-e29b-41d4-a716-446655440000",
  "msg": "OTP sent to registered mobile"
}

Authorizations

x-api-key · string · header · required

Your API key for authentication. Use sandbox-with-json-responses as Sandbox key.

Body

application/json

pan · string · required

PAN number

Example:

"ABCDE1234F"

bo_id · string · required

CDSL BO ID (16 digits)

Example:

"1234567890123456"

dob · string · required

Date of birth (YYYY-MM-DD)

Example:

"1990-01-15"

Response

200

application/json

OTP sent to registered mobile

status · string

Example:

"success"

session_id · string

Session ID for verify step

Example:

"550e8400-e29b-41d4-a716-446655440000"

msg · string

Example:

"OTP sent to registered mobile"