Developers
First call in
five minutes.
One base URL, bearer auth, JSON in and out. The reference below covers every live endpoint in the stack.
2 live API families · 7 endpoints · one API key
# 1. Grab sandbox keys from your dashboard
# 2. Verify a PAN in one call
curl -X POST https://sandbox.neetix.in/v1/kyc/pan/verify \
-H "Authorization: Bearer sk_test_..." \
-d '{ "pan": "ABCPE1234F", "name": "Rohan Malhotra" }'{ "valid": true, "name_match": 0.97 }Platform behavior
The same conventions, every family.
How you authenticate, where sandbox lives, how events come back, and what a retry does — identical from KYC to bureau pulls, and for every family that follows.
Authentication
Bearer keys per environment: sk_test for sandbox, sk_live for production. Rotate keys from the dashboard without downtime.
Environments
sandbox.neetix.in mirrors production behavior with stubbed rails. Same schemas, no live traffic.
Webhooks
Every async event ships as a signature-verified webhook. Verify with your webhook secret, respond 2xx, done.
Idempotency
Send an Idempotency-Key header on any POST. Retries return the original result instead of firing twice.
Reference
Every live endpoint in the stack.
The complete surface across the two live families — bureau pulls and KYC. Providers, capabilities, and full code samples live on each family page.
/v1/bureau/pullPull report (soft or hard)/v1/bureau/reports/{id}Fetch parsed report/v1/kyc/pan/verifyVerify PAN/v1/kyc/aadhaar/initiateStart Aadhaar OTP eKYC/v1/kyc/aadhaar/verifyVerify Aadhaar OTP/v1/kyc/facematchFace match/v1/kyc/digilocker/authorizeDigiLocker consent redirectMore families in development
Coming soonBank verification, eNACH mandates, eSign & agreements, Payments are on the way — same base URL, same key, same conventions as the live families. Planned scope lives on each family page; nothing below is callable yet.
Get notified when they shipSandbox
Start in the sandbox.
Sandbox keys and a Postman collection, with an engineer on the other side of the line.