Verification API
Integrate Aadhaar, PAN, GSTIN, vehicle and FASTag checks through Boni. Test sandbox responses, control endpoint access and keep verification outcomes with your workflow.
For: Product and platform teams adding Indian-record verification to onboarding, business checks and vehicle operations.
Shared context · Clear responsibility · Review where it matters
How it works
Choose the check your workflow actually needs, collect the required input and permission, then handle each returned outcome explicitly. A response is evidence for your process—not an automatic instruction to approve an account, lend money or release a vehicle.
Agree the intended use, enabled checks and environment. Your subscription determines endpoint access and the request limits assigned to it.
Use the documented synthetic inputs to exercise verified, no-record and error branches before introducing real personal or business records.
Keep the client ID and secret server-side. Send the documented inputs and a unique idempotency key; reuse a key only for the exact same request body.
Read the status and request reference. Continue an OTP challenge where required, distinguish no record from a service failure, and keep a human review path for your business decision.
Product scope
Aadhaar and PAN verification inputs with the document owner’s consent and the production OTP flow where required.
GSTIN checks for the business-registration input your application supplies.
Vehicle-registration checks using the vehicle identifier and the approved response contract.
FASTag observations using a vehicle number or chassis number, with exactly one identifier per request.
Separate authenticated sandbox and production subscriptions and credentials.
Endpoint access, configurable quota windows, request references and usage reads.
Operating areas
Collect only what the selected operation needs. Aadhaar and PAN requests require the document owner’s consent; production may require the owner to complete an OTP challenge.
Attach the returned status and request reference to the correct business record. A no-record result is different from a successful match or an unavailable data source.
Treat invalid input, disabled access, quota exhaustion and temporary provider failure as different operating conditions. Respect Retry-After and retain the original request key when recovering the same body.
Connect the right people, records and systems around your workflow, with clear ownership and the controls your team needs.
Do not put client secrets in browser code, a mobile bundle or a public URL. Sandbox and production use their own credentials and enabled subscriptions.
FASTag returns sparse toll observations within its documented rolling window, not continuous GPS tracking. It does not provide wallet balances, recharge or debit transactions; an empty observation result is valid.
Verification supports your approved workflow. It is not a universal trust score, a credit decision or a guarantee that every input has a matching record.
Connected products
Use the exact endpoints, inputs, sandbox examples, OTP lifecycle, error conditions and usage contract.
Read the integration guideImport the existing public specification for schemas and client generation instead of guessing the request shape.
Download OpenAPIKeep customer records, operating context and the next action in your wider business workflow.
Explore platform integrationsQuestions
The published API covers Aadhaar, PAN, GSTIN, vehicle registration and FASTag observations. The checks enabled for your subscription determine what your application can call.
Use the separately authenticated sandbox and documented synthetic values. It returns deterministic test records and does not call production data sources. Build the no-record and error paths as well as the verified path.
Use the original idempotency key only with the original request body. A different body needs a new key. Follow the documented response and Retry-After rather than submit new requests blindly.
It provides sparse toll observations within the documented rolling window, not continuous GPS, balances, recharge or debit transactions. An empty observation result is a valid outcome.
Discuss the intended use, required endpoints and integration responsibilities with Boni. Production access is activated for the agreed organization, environment and subscription.
See it working for your business
