Identity & KYC Verification APIs

PAN Advanced Verification API

Verify a PAN and also get its holder type and whether it is linked to Aadhaar.

What it verifies

Checks a PAN like the basic check, and also returns the holder type and whether the PAN is linked to Aadhaar, so you can decide whether it is usable for filing and KYC.

Who uses it

Lenders and NBFCs that need a PAN that is operative, not just valid
Brokerage and wealth platforms onboarding investors
Payroll and vendor-onboarding teams validating PAN before payouts

Request and response

POSThttps://verification.techinnoverz.com/api/v1/identity-kyc/pan-advanced

Verify a PAN and fetch its status, holder type and Aadhaar link status. This call is billed when it returns a successful result.

Request body

panstringrequired

10-character PAN.

consentstringrequired

Must be "Y". Records that the end customer consented to this check; logged against the transaction.

referenceIdstringoptional

Your own id, echoed back in the response for reconciliation.

Example requests

curl -X POST "https://verification.techinnoverz.com/api/v1/identity-kyc/pan-advanced" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "pan": "ABCPE1234F",
  "consent": "Y",
  "referenceId": "app_20915"
}'

const res = await fetch("https://verification.techinnoverz.com/api/v1/identity-kyc/pan-advanced", {
  method: "POST",
  headers: {
    "x-api-key": "YOUR_API_KEY",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "pan": "ABCPE1234F",
    "consent": "Y",
    "referenceId": "app_20915"
  }),
});
const result = await res.json();

import requests

res = requests.post(
    "https://verification.techinnoverz.com/api/v1/identity-kyc/pan-advanced",
    headers={"x-api-key": "YOUR_API_KEY"},
    json={
        "pan": "ABCPE1234F",
        "consent": "Y",
        "referenceId": "app_20915",
    },
    timeout=15,
)
result = res.json()

200 response — status "found"

Response

{
  "status": "found",
  "data": {
    "pan": "ABCPE1234F",
    "name": "Asha Sample",
    "panStatus": "VALID",
    "holderType": "Individual",
    "aadhaarLinked": true
  },
  "source": "provider",
  "dataAsOf": "2026-11-03T09:30:00.000Z",
  "referenceId": "app_20915",
  "billing": {
    "charged": true,
    "walletBalance": "12450.00"
  },
  "txnId": "txn_8c31ba90",
  "livemode": true
}

Fields returned in data

panstringoptional

The PAN that was verified.

namestringoptional

Name registered against the PAN.

panStatusstringoptional

Status of the PAN, for example VALID.

holderTypestringoptional

Type of holder: Individual, Company, Firm, Trust and so on.

aadhaarLinkedbooleanoptional

Whether the PAN is linked to an Aadhaar number.

Error codes

Errors return a non-200 HTTP status and the same envelope, so your retry logic and your reconciliation agree.

400 INVALID_INPUT

A field is missing or malformed. The details list each problem. Not charged.

401 INVALID_KEY

The key is missing, revoked, or not a key we issued.

402 WALLET_EMPTY

Your available balance is below the price of this call. Top up and retry. Not charged.

403 PRODUCTION_NOT_ENABLED

A live key was used before live access was enabled for your account. Use a test key, or ask us to enable live access.

403 TEST_NOT_ENABLED

A test key was used before test (UAT) access was enabled for your account. Ask us to enable it.

403 API_NOT_ENABLED

This check is switched off for your account, or is not available for live use yet.

403 IP_NOT_ALLOWED

The key is restricted to certain IP addresses and this call came from another.

403 ACCOUNT_SUSPENDED

The account is suspended. Contact support.

404 NO_DATA

A valid request, but no record was found. Not charged.

404 ROUTE_NOT_FOUND

There is no endpoint at that path.

405 METHOD_NOT_ALLOWED

Use the method shown in the Allow header.

409 IDEMPOTENCY_IN_PROGRESS

A call with the same Idempotency-Key is still being processed. Retry after the delay in Retry-After.

413 PAYLOAD_TOO_LARGE

The request body is too large. Not charged.

415 UNSUPPORTED_MEDIA_TYPE

Send the request with Content-Type: application/json.

422 IDEMPOTENCY_KEY_REUSED

This Idempotency-Key was already used with a different request body. Use a new key for a new request.

429 RATE_LIMITED

Too many requests or too many at once. Wait for the Retry-After delay.

500 INTERNAL_ERROR

Something went wrong on our side. Not charged. Quote the txnId if you contact support.

502 SOURCE_ERROR

The data source returned an error. Not charged.

503 SOURCE_DOWN

The data source is unavailable right now. Not charged. Retry after the delay in Retry-After.

504 SOURCE_TIMEOUT

The data source did not answer in time. Not charged.

Error response

{
  "status": "error",
  "error": {
    "code": "NO_DATA",
    "message": "No record found for the given input. Not charged."
  },
  "billing": {
    "charged": false
  },
  "txnId": "txn_8c31ba91",
  "livemode": true
}

Billing

You are charged only on successful hits. Failed, no-data and error calls are free.

Every response carries billing.charged and your remaining billing.walletBalance. Per-hit pricing is set on your rate card; book a demo to get yours.

Related checks

Aadhaar OTP Verification API — Consent-based Aadhaar verification with OTP delivered to the registered mobile number.
PAN Verification API — Verify PAN card details and status against Income Tax Department records.
Voter ID Verification API — Verify EPIC (Voter ID) details against Election Commission of India records.
Driving Licence Verification API — Verify driving licence number, validity and vehicle class against Parivahan records.
Face Match API — Compare two photos and get a match score, for example a selfie against an ID photo.
Face Match with Liveness API — Check that a selfie is of a live person and matches the photo on their ID, in one call.
DigiLocker Verification API — Consent-based fetch of a person's verified documents from DigiLocker.

All API documentation · OpenAPI specification · Docs as plain text