CAS Fetch

CDSL CAS Fetch - Step 1 (Request OTP)

Changed on

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

Request

  • Base URL
    https://api.casparser.in
  • Auth
    API key in header x-api-key

Request body

panstring required

PAN number

bo_idstring required

CDSL BO ID (16 digits)

dobstring required

Date of birth (YYYY-MM-DD)

Example request

{
  "pan": "ABCDE1234F",
  "bo_id": "1234567890123456",
  "dob": "1990-01-15"
}

Response

OTP sent to registered mobile

statusstring
session_idstring

Session ID for verify step

msgstring

Example response

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

Changes

    • warning

      the optional response header X-Request-ID removed for the status 401

    • warning

      the optional response header X-Request-ID removed for the status 500

    • warning

      added the new failed enum value to the response property for the response status