Verify DL Basic

API reference

curl -X POST "https://__mock__/verification/v1/idverification/dl/basic" \  -H "Content-Type: application/json" \  -d '{    "consent": "Y"  }'

{
  "captcha_tries": 0,
  "cov": [
    "string"
  ],
  "cov_category": [
    "string"
  ],
  "date_of_birth": "string",
  "expiry_date": "string",
  "issue_date": "string",
  "licence_number": "string",
  "name": "string",
  "rto_name": "string",
  "status": "string"
}

{
  "detail": {},
  "message": "string"
}

{
  "detail": {},
  "message": "string"
}

Overview

Call POST /verification/v1/idverification/dl/basic from your backend with Authorization: Bearer <token> and JSON consent (Y only in schema enum), dl_no, and dob (date string). The 200 response includes licence fields such as licence_number, name, status, dates, and RTO metadata as listed in OpenAPI.

Key features

• Official-record style fields for underwriting and identity checks.
• Explicit consent required in consent.

Implementation

Step 1: Call from your backend

POST /verification/v1/idverification/dl/basic HTTP/1.1
Host: <verification-api-base-url>
Authorization: Bearer <token>
Content-Type: application/json

{
  "consent": "Y",
  "dl_no": "HR-0619850001234",
  "dob": "1990-01-15"
}

Step 2: Use the response

Validate status and map name, cov, and dates into your records.

Error handling

Benefits

• Reduces fake DL uploads by matching against structured RTO-style data.

Next steps

• Authenticate
• Verification API index