Recharge · PAN · KYC · WhatsApp

One API for every
service you sell.

Mobile recharge, NSDL PAN, Aadhaar KYC and WhatsApp messaging — behind a single wallet, a single key and a console that shows exactly what happened on every call.

Prepaid wallet, no surprises Per-client access control Every request logged
POST /api/v1/mobile-recharge
$ curl -X POST https://kdapi.in/api/v1/mobile-recharge \ -H "X-API-Key: kd_live_••••••" \ -H "X-API-Secret: ••••••" \ -d '{"mobile":"98••••••••","operator":"AIRTEL","amount":199}' { "success": true, "request_id": "req_8f2a19c4", "charged": 196.40, "data": { "status": "pending" } }
one key · one wallet● logged & traceable
Wallet debitAutomatic, per request
Access grantedMethod by method
What you can build

Everything behind one integration.

Add a service, get access, and call it like the last one. The request shape stays the same, so new endpoints don't mean new plumbing.

Verification & KYC

PAN authorisation through NSDL, Aadhaar OTP KYC, bank and IFSC checks — with the application state and provider response kept together.

NSDL PANAadhaar OTPBank / IFSCKYC status
See verification methods →

Recharge & bills

Mobile recharge with operator lookup, unique references and status checks. Pending orders are monitored so you don't have to poll blindly.

Mobile rechargeOperatorsStatus checkRefunds
See recharge methods →

Messaging & WhatsApp

Send text, images and documents from a WhatsApp number paired inside the console. Inbound replies can answer with balance or report data.

TextMediaDevice pairingAuto-reply
See messaging methods →

The console around it

Wallet top-ups, per-method pricing, access control, request logs and reports — the operational layer that turns an API into a business.

WalletPricingAccess controlLogs
Open your workspace →
Why teams stay

Built for the part after the demo.

Integrations are easy to start and hard to operate. KDAPI ships the operating layer — money, permission and evidence — in the same place as the API.

01

One wallet, every service

Top up once and let each call debit the price configured for your account. No separate vendor balances to chase, no end-of-month reconciliation exercise.

02

Decide who can call what

Access is granted per method, per client. Switch a service off and it is unavailable at the edge — before a single request reaches a provider.

03

Every request on record

Each call carries a reference, a request log and a wallet entry. When a client asks what happened, the answer is a filter away.

Go live

Three steps to your first call.

01

Create your account

Register, complete onboarding and your workspace is created with its own credentials section.

02

Fund the wallet

Add balance through the console. Every enabled method shows its price before you call it.

03

Send the request

One POST to https://kdapi.in/api/v1/{method} with your key and secret. Response, debit and log are recorded together.

your-server.jsNode · fetch
// One shape for every service const res = await fetch( 'https://kdapi.in/api/v1/mobile-recharge', { method: 'POST', headers: { 'Content-Type': 'application/json', 'X-API-Key': process.env.KDAPI_KEY, 'X-API-Secret': process.env.KDAPI_SECRET, }, body: JSON.stringify({ mobile: '98xxxxxxxx', operator: 'AIRTEL', amount: 199, }), } ); const data = await res.json(); // → { success, request_id, charged, data }
Operational basics

The boring parts, handled.

Prepaid walletBalance gates every call.
Per-method pricingYour rate, set per client.
Access controlEnable methods individually.
Auditable logsRequest, response and debit.
Questions

Before you integrate.

Where do I get my API key and secret?

They are issued inside your client console under Credentials once your account is active. Keep the secret on your server — never in browser code or a mobile app bundle.

How does billing work?

Billing is prepaid. Each method has a price on your account, and the wallet is debited per processed request. Your wallet history and request log show the same reference, so reconciliation is a filter, not a spreadsheet.

Which services are available?

Availability depends on your account and provider access. The public API reference lists every method currently active, and your console lists exactly the methods enabled for you.

Can I control what a client of mine can call?

Yes. Access is granted per method and per client, with per-client pricing. Revoking a method takes effect at the edge immediately.

What happens if a recharge or PAN application stays pending?

Pending orders are monitored at a configured interval. Status checks confirm the provider result before any credit or refund is posted, so the wallet always matches reality.

Your next service is one API call away.

Create an account, pick a method, and make your first request today.

Docs & support