> ## Documentation Index
> Fetch the complete documentation index at: https://docs.didit.me/llms.txt
> Use this file to discover all available pages before exploring further.

# India Aadhaar (UIDAI)

> Verifies the input Aadhaar number against UIDAI identity records. Authoritative real-time identity lookup for India. Real-time lookup, pay-per-call.

<div hidden data-didit-db-validation-defaults="{&#x22;issuing_state&#x22;:&#x22;IND&#x22;,&#x22;services&#x22;:&#x22;ind_aadhaar&#x22;,&#x22;consent&#x22;:&#x22;true&#x22;,&#x22;full_name&#x22;:&#x22;John Doe&#x22;,&#x22;date_of_birth&#x22;:&#x22;1990-01-01&#x22;,&#x22;personal_number&#x22;:&#x22;111111111111&#x22;,&#x22;pan&#x22;:&#x22;ABCDE1234F&#x22;,&#x22;vendor_data&#x22;:&#x22;user-1234&#x22;}" />

Verifies the input Aadhaar number against UIDAI identity records. Didit exposes this service through `POST /v3/database-validation/` so you can verify the submitted data against the authoritative source and receive normalized match results.

## Coverage

* **Coverage:** \~ 100%
* **Country:** India
* **Service ID:** `ind_aadhaar`
* **Data domain:** Identity
* **Category:** NationalIDRegistry

## Inputs

| Field             | Required | Example        |
| ----------------- | -------: | -------------- |
| `full_name`       |      Yes | `John Doe`     |
| `date_of_birth`   |      Yes | `1990-01-01`   |
| `personal_number` |      Yes | `111111111111` |
| `pan`             |      Yes | `ABCDE1234F`   |
| `vendor_data`     |       No | `user-1234`    |

* **Required inputs:** `full_name`, `date_of_birth`, `personal_number`, `pan`
* **Optional inputs:** `vendor_data`
* **Consent:** Required
* **Workflow availability:** Available in workflow
* **Coverage:** \~ 100%
* **Price:** \$0.25 per successful query

## Body parameters

<ParamField body="issuing_state" type="string" required default="IND" placeholder="IND">
  ISO 3166-1 alpha-3 country code for this database service.

  Example: `IND`
</ParamField>

<ParamField body="services" type="string" required default="ind_aadhaar" placeholder="ind_aadhaar">
  Array containing this service ID. Pinning the service keeps the request scoped to this exact database.

  Example: `ind_aadhaar`
</ParamField>

<ParamField body="consent" type="boolean" required default="true" placeholder="true">
  Explicit end-user consent for this service.

  Example: `true`
</ParamField>

<ParamField body="full_name" type="string" required default="John Doe" placeholder="John Doe">
  Full legal name to validate.

  Example: `John Doe`
</ParamField>

<ParamField body="date_of_birth" type="string" required default="1990-01-01" placeholder="1990-01-01">
  Date of birth in `YYYY-MM-DD` format.

  Example: `1990-01-01`
</ParamField>

<ParamField body="personal_number" type="string" required default="111111111111" placeholder="111111111111">
  Country-specific personal identity number.

  Example: `111111111111`
</ParamField>

<ParamField body="pan" type="string" required default="ABCDE1234F" placeholder="ABCDE1234F">
  Permanent Account Number.

  Example: `ABCDE1234F`
</ParamField>

<ParamField body="vendor_data" type="string" default="user-1234" placeholder="user-1234">
  Your stable user reference for this person, such as your internal user ID. Didit uses it to link standalone checks to the same end user and reduce duplicate-detection noise.

  Example: `user-1234`
</ParamField>

## Input rules & validation notes

* `pan` must use uppercase letters.
* `pan` must match `[A-Z]{5}\d{4}[A-Z]`.
* `personal_number` must contain digits only; remove spaces, hyphens, and punctuation before sending the request.
* `personal_number` must be exactly 12 characters long.

## How to call it

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://verification.didit.me/v3/database-validation/" \
    -H "x-api-key: YOUR_API_KEY" \
    -F "issuing_state=IND" \
    -F "services=ind_aadhaar" \
    -F "vendor_data=user-1234" \
    -F "consent=true" \
    -F "full_name=John Doe" \
    -F "date_of_birth=1990-01-01" \
    -F "personal_number=111111111111" \
    -F "pan=ABCDE1234F"
  ```
</RequestExample>

<ResponseExample>
  Every successful call returns HTTP `200`. The **`outcome_code`** field tells you what actually happened — distinguishing, for example, a real biometric mismatch (`BIOMETRIC_NO_MATCH`) from a selfie that could not be read (`BIOMETRIC_IMAGE_UNUSABLE`). The `status` shown is the default feature status; your configured [Partial Match / No Match actions](/core-technology/database-validation/database-validation-warnings) can override it.

  **`MATCH`** — The registry confirmed the identity and every checked field matched.

  ```json 200 OK — MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "Approved",
    "issuing_state": "IND",
    "match_type": "full_match",
    "validations": [
      {
        "outcome_code": "MATCH",
        "service_id": "ind_aadhaar",
        "service_name": "India Aadhaar (UIDAI)",
        "source_data": {
          "date_of_birth": "1990-01-01",
          "full_name": "John Doe",
          "identification_number": "SAMPLE-ID-12345"
        },
        "validation": {
          "date_of_birth": "full_match",
          "full_name": "full_match",
          "identification_number": "full_match"
        }
      }
    ]
  }
  ```

  **`PARTIAL_MATCH`** — The identification number was found but one or more personal fields (usually name or date of birth) did not fully match.

  ```json 200 OK — PARTIAL_MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "In Review",
    "issuing_state": "IND",
    "match_type": "partial_match",
    "validations": [
      {
        "outcome_code": "PARTIAL_MATCH",
        "service_id": "ind_aadhaar",
        "service_name": "India Aadhaar (UIDAI)",
        "source_data": {
          "date_of_birth": "1990-01-01",
          "full_name": "John Doe",
          "identification_number": "SAMPLE-ID-12345"
        },
        "validation": {
          "date_of_birth": "full_match",
          "full_name": "no_match",
          "identification_number": "full_match"
        }
      }
    ]
  }
  ```

  **`NO_MATCH`** — The registry returned no match for the submitted data.

  ```json 200 OK — NO_MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "Declined",
    "issuing_state": "IND",
    "match_type": "no_match",
    "validations": [
      {
        "outcome_code": "NO_MATCH",
        "service_id": "ind_aadhaar",
        "service_name": "India Aadhaar (UIDAI)",
        "source_data": {
          "date_of_birth": "NO_MATCH",
          "full_name": "NO_MATCH",
          "identification_number": "NO_MATCH"
        },
        "validation": {
          "date_of_birth": "no_match",
          "full_name": "no_match",
          "identification_number": "no_match"
        }
      }
    ]
  }
  ```
</ResponseExample>

## Returned data

The exact fields surfaced in `source_data` depend on what the registry returns. The generated example for `ind_aadhaar` currently documents this normalized shape:

* `date_of_birth`
* `full_name`
* `identification_number`

## Pricing & SLAs

India Aadhaar (UIDAI) queries are billed only when Didit receives a conclusive result from the validation source.

* **Per-call price:** \$0.25 USD.
* **Billing:** per successful query. You are not charged when the registry is unreachable, when required fields are missing, or when the request is rejected before reaching the source.
* **Latency:** typical p95 \< 2 s.
* **Availability:** 99.9% per quarter on Didit's side; downstream source availability varies by country and dataset.

## Continue reading

* [India Database Validation overview](/api-reference/database-validation/india)
* [Database Validation overview](/core-technology/database-validation/overview)
* [Outcome Codes](/core-technology/database-validation/database-validation-outcome-codes)