curl -X POST "https://api.sinhcoms.com/aadhaar/start"
-H "Authorization: Bearer YOUR_API_KEY"
-H "Content-Type: application/x-www-form-urlencoded"
--data-urlencode "aadhaar=YOUR_AADHAAR_VALUE"
# Continue the same session
curl -X POST "https://api.sinhcoms.com/aadhaar/captcha"
-H "Authorization: Bearer YOUR_API_KEY"
--data-urlencode "sessionId=SESSION_ID"
--data-urlencode "captcha=CAPTCHA_CODE"
curl -X POST "https://api.sinhcoms.com/aadhaar/otp"
-H "Authorization: Bearer YOUR_API_KEY"
--data-urlencode "sessionId=SESSION_ID"
--data-urlencode "otp=OTP_VALUE"Aadhaar API
The Aadhaar API exposes the multi-step flow already represented by the active API controller catalogue: start a workflow, work through captcha handling and continue to the OTP stage. It is intended as a developer integration building block inside an authorised application workflow rather than a standalone customer interface.
What this API is designed to do
Multi-step Aadhaar workflow API with session, captcha and OTP stages.
Where it can fit
These are common integration scenarios; the exact implementation depends on your application, data-handling requirements and subscription tier.
Published routes and methods
The endpoint list below is read from the existing API controller catalogue. Website Management can explain the API, but it cannot invent or replace live endpoint routes.
/aadhaarIndex/aadhaar/captchaCaptcha/aadhaar/otpOtp/aadhaar/startStartAuthentication, request shape and response handling
These examples are presentation content managed by Website Management. Always compare them with the live API documentation and endpoint catalogue before production integration.
Send the API key as Authorization: Bearer YOUR_API_KEY or X-API-Key: YOUR_API_KEY. The key must be active, assigned to the Aadhaar API product, backed by an active subscription and allowed by your whitelist settings.
{
"status": "captcha",
"message": "Enter captcha code",
"sessionId": "SESSION_ID",
"captcha_base64": "..."
}
# After captcha
{
"status": "otp",
"message": "Captcha accepted. Submit OTP.",
"sessionId": "SESSION_ID"
}Documented error states
400Aadhaar, sessionId, captcha or OTP input is missing401API key authentication or product authorization failed429Daily request limit exceeded504Upstream WebSocket timed outFrom subscription to first request
Use the customer dashboard as the control point for keys, whitelist rules and plan limits.
Choose an active subscription tier
Generate or assign an API key from API Access
Configure whitelist restrictions where required
Integrate the published /aadhaar routes in sequence
Track request usage and errors from the API dashboard
Choose the request capacity you need
Pricing and limits below are read from the active subscription tiers in the API system.
- 4,000 requests/day
- 120,000 requests/month
Before you go live
Aadhaar and identity data can be sensitive and regulated. Use this API only for lawful, authorised purposes and apply appropriate consent, data-minimisation, security and retention controls.
Already a customer? Continue from your dashboard.
Sign in to keep purchases, licenses, API keys, downloads, invoices and project requests connected to one account.