Sub-second JSON response APIs for PAN, Driving Licence, Vehicle RC, and institutional registry verification with dual-key isolation and whitelisted IP protection.
curl -X POST "https://api.oodixindia.com/srv2/validation/pan/father-details" \ -H "Content-Type: application/json" \ -H "api-id: APID1001" \ -H "api-key: 6d02ba4b-95ee-4cb1-8041-0f72365cb76e" \ -d '{"pan_number": "ABCDE1234F"}'
$ch = curl_init("https://api.oodixindia.com/srv2/validation/pan/father-details"); curl_setopt_array($ch, [ CURLOPT_POST => true, CURLOPT_RETURNTRANSFER => true, CURLOPT_HTTPHEADER => [ "Content-Type: application/json", "api-id: APID1001", "api-key: 6d02ba4b-95ee-4cb1-8041-0f72365cb76e" ], CURLOPT_POSTFIELDS => json_encode(["pan_number" => "ABCDE1234F"]) ]); $response = curl_exec($ch);
const axios = require('axios'); const res = await axios.post("https://api.oodixindia.com/srv2/validation/pan/father-details", { pan_number: "ABCDE1234F" }, { headers: { "api-id": "APID1001", "api-key": "6d02ba4b-95ee-4cb1-8041-0f72365cb76e" } }); console.log(res.data);
{
"status": {
"code": 200,
"type": "success",
"message": "Request processed successfully."
},
"data": {
"pan": "ABCDE1234F",
"fullname": "RAHUL SHARMA",
"father_name": "RAMESH SHARMA",
"aadhaar_linked": true
}
}
High-throughput enterprise verification endpoint with normalized response schema.
High-throughput enterprise verification endpoint with normalized response schema.
Synchronous PAN verification returning registered full name, father name, category, and Aadhaar link status.
Synchronous demographic and active validity check through direct registry validation.
High-throughput enterprise verification endpoint with normalized response schema.
High-throughput enterprise verification endpoint with normalized response schema.
High-throughput enterprise verification endpoint with normalized response schema.
High-throughput enterprise verification endpoint with normalized response schema.
High-throughput enterprise verification endpoint with normalized response schema.
High-throughput enterprise verification endpoint with normalized response schema.
High-throughput enterprise verification endpoint with normalized response schema.
High-throughput enterprise verification endpoint with normalized response schema.
High-throughput enterprise verification endpoint with normalized response schema.
High-throughput enterprise verification endpoint with normalized response schema.
| Parameter | Gateway Specification |
|---|---|
| Protocol & Transport | RESTful HTTPS over TLS 1.3 / TLS 1.2 with strict SNI validation |
| Authentication Model | Dual-Header Authentication: api-id + api-key (UUID) |
| Content Encoding | application/json; charset=UTF-8 (Synchronous POST) |
| Network Security | Static Caller IP whitelisting supported per user account |
| Balance Execution | Atomic prepaid wallet debiting; automatic rollback on upstream error |
Every API execution strictly verifies the caller client identifier and secret token hash, isolating balance pools across retailers.
Persistent connection pooling minimizes TLS handshakes, yielding consistent sub-second registry response times.
Configure authorized server IP boundaries to prevent credential hijacking and unauthorized API access attempts.
Create your profile to generate instant Client API ID and Secret Key credentials.
Scan the dynamic UPI QR in your console to fund your prepaid verification balance.
Point your backend applications to live REST endpoints with JSON payloads.