Mobile To Prefill
Auto-fill a verified customer profile from just a mobile number to cut onboarding drop-off.
What is the Mobile To Prefill?
The BILAPI Mobile to Prefill API returns a consolidated identity profile for a customer from their mobile number alone — name, address history, age and linked identifiers — so you can prefill your signup form and dramatically cut drop-off.
It is used by lenders, fintechs and onboarding teams to turn a single phone number into a ready-to-review KYC profile, reducing the number of fields a customer has to type and giving you a verified data point before approval.
Pass a 10-digit mobile number (with consent) and receive a structured prefill profile as JSON. Billed only on a successful lookup.
What the Mobile To Prefill returns
Every successful call returns a clean, predictable JSON envelope. The data object includes the fields below (exact fields vary by record availability).
| Field | Description |
|---|---|
name | Full name associated with the mobile number. |
addresses | Array of known addresses with city, state and pincode. |
age_or_dob | Age or date of birth where available. |
gender | Gender signal where available. |
emails | Linked email addresses, where available. |
identifiers | Masked linked identifiers (e.g. masked PAN) where available. |
Sample request & response
Call the endpoint with your API key in the X-Bilapi-Api-Key header. The same request shape works in the free sandbox and in production.
POST https://api.bilapi.com/v1/mobile-to-prefill
X-Bilapi-Api-Key: <your_api_key>
Content-Type: application/json
{
"mobile": "9876543210",
"consent": "Y"
}{
"status_code": 200,
"success": true,
"message": "Profile found",
"data": {
"name": "RAHUL SHARMA",
"age_or_dob": "1992-04-18",
"gender": "M",
"addresses": [
{ "address": "12 MG Road", "city": "Pune", "state": "Maharashtra", "pincode": "411001" }
]
}
}Key features
Real-time results
Sub-300ms median response so mobile checks never slow your onboarding funnel.
Predictable JSON
The same clean response envelope as every BILAPI endpoint — parse once, reuse everywhere.
Only pay for hits
Invalid inputs and failed lookups are never charged to your wallet.
Secure by design
TLS 1.3 in transit, PII tokenisation at rest and a full audit log on every request.
One key, every API
Sandbox to production on a single key — no per-vendor contracts or integrations.
Built to scale
99.9% uptime target with bulk and webhook-friendly workflows for high volume.
Where it's used
Customer onboarding
Auto-fill and validate identity during signup to cut drop-off and manual review.
Lending & underwriting
Add a verified data point to credit decisions and reduce first-party fraud.
Fraud & risk
Flag mismatches and synthetic identities before they enter your system.
Compliance & audit
Keep a tamper-evident trail of every verification for KYC/AML reviews.
How it works
Create a free account
Sign up on the BILAPI console and get a live API key instantly.
Send a request
POST the required mobile fields to the endpoint with your API key in the header.
Get structured JSON
Receive a clean, predictable JSON response in milliseconds.
Plug into your flow
Drop the result straight into onboarding, underwriting or risk decisioning.
Frequently asked questions
What does the Mobile to Prefill API return?
From a mobile number it returns a consolidated profile — name, address history, age/DOB, gender and masked linked identifiers — that you can use to prefill a KYC or signup form.
Is consent required?
Yes. This is a consent-first, DPDP-aligned API — you must capture and pass customer consent before enriching their profile.
How does it reduce drop-off?
Instead of asking the customer to type every field, you prefill the form from the phone number and ask them only to confirm, which measurably reduces onboarding abandonment.
What is the input?
A 10-digit Indian mobile number along with captured consent.
Do failed lookups cost money?
No — you are billed only for successful responses from your wallet balance.
Related Mobile Related API
Start verifying with BILAPI
One key, a free sandbox and a predictable JSON envelope across every endpoint.