Skip to content
Api-King

v2 liveOTP · Room codes · KYC

Ship OTP delivery in one integration.

Production-grade OTP delivery for teams building in India. Prepaid, auditable, and documented well enough that you will not need to email us.

Uptime
99.9%
p95 latency
<100ms
Daily requests
1M+
Developers
5k+

What your users see, end to end.

Number in, code out, verified — the whole round trip is two calls to one endpoint. This is the flow running at the speed it actually runs.

Get your API key

An animation of the verification flow: a mobile number is entered and submitted, a confirmation reads "OTP sent successfully!", a six-digit code is entered on the next screen, and verifying it reads "OTP verified successfully!".

From signup to first response in three steps.

No SDK to install and no sandbox to request. Create a key, send a JSON body to one endpoint, and read a response shape that does not change between providers.

  1. Create your key

    Sign up and generate a scoped API key from the dashboard.

    // Store this server-side.// Never ship a key to the browser.API_KEY="ak_live_****************"
  2. Call the endpoint

    Send a JSON body with your key in the x-api-key header.

    POST/api/v1/otp/send
    {  "number": "9876543210",  "template": "login"}
  3. Handle the response

    Every response carries a request_id you can trace in your usage log.

    {  "success": true,  "request_id": "req_8Kd2mQ",  "status": "delivered"}

Built for people who read the docs first.

Everything that matters when an integration goes to production: how fast you get a key, what happens when you lose one, and whether the bill at the end of the month matches the log.

POST/api/v1/otp/send
{  "number": "9876543210",  "template": "login"}// 200 OK - 84ms{  "success": true,  "request_id": "req_8Kd2mQ",  "status": "delivered"}
  • Keys in under a minute

    Register, generate a key, and make your first authenticated call without talking to sales.

  • Scoped, revocable keys

    Every key is scoped to a service and can be rotated or revoked instantly from the dashboard.

  • Usage you can audit

    Every request is logged with latency, status, and cost so billing is never a surprise.

  • Prepaid, no lock-in

    Top up a wallet and draw down per request. No seats, no minimums, no annual contract.

Three things that never surprise you.

The parts of an API integration that usually go wrong quietly, and what Api-King does about each of them.

Nothing you have to take on trust.

Every claim on this page is something you can check from inside your own account on the first day.

Create an account
  1. Documentation that answers first

    Every endpoint ships with its parameters, a copyable request, and the exact body of each response code — including the failures.

  2. One response shape, whatever happens upstream

    When a provider goes down, delivery fails over and you still parse the same JSON. Your integration never learns which vendor handled the message.

  3. The bill reconciles against the log

    Each call is recorded with its status, latency and cost. The number on the invoice is a sum you can reproduce from your own usage page.

Prepaid, and auditable to the request.

Top up a wallet, draw it down per call, and read back exactly what you spent it on.

  • Every request, with latency

    Status, endpoint, response time and cost for each call, searchable from the dashboard.

  • Traceable by request id

    Every response carries a request_id. Paste it into your usage log to find the exact call.

  • Keys stored hashed

    A key is shown once at creation. Lose it and you revoke it — nobody can read it back, including us.

Recent activity

Live
Example of the request log shown in your dashboard
StatusEndpointLatency
200/api/v1/otp/send84ms
200/api/v1/otp/send91ms
401/api/v1/account12ms
200/api/v1/roomcode/checkroom118ms

Three services. One key.

Plain HTTP with JSON in and JSON out. No SDK required, and no endpoint that needs a support ticket to unlock.

OTP

  • POST/api/v1/otp/send
  • POST/api/v1/account
  • GET/api/v1/gateway-info

Room codes

  • POST/api/v1/roomcode/checkroom
  • POST/api/v1/roomcode/gamestatus
  • POST/api/v2/roomcode/checkroom

KYC

  • POST/api/v1/kyc/request
  • POST/api/v1/kyc/status

Frequently asked questions

Answers about keys, pricing, failover and language support.

Still have questions?

Support answers from the same inbox the engineers read.

How quickly can I start sending requests?

Register an account, generate a key from the dashboard, and your first authenticated request will work immediately. There is no manual approval step.

How is pricing calculated?

Every service is prepaid per request against your wallet balance. You top up the wallet, and each successful call draws down from it. There are no seat fees or monthly minimums.

What happens if an SMS provider goes down?

OTP delivery automatically fails over to a secondary provider. You receive a single consistent response shape regardless of which provider handled the message.

Can I use this from PHP, Node.js, or Python?

Yes. Every endpoint is plain HTTP with JSON request and response bodies, so any language with an HTTP client works. The documentation includes copyable examples.

Are my API keys recoverable if I lose them?

No — keys are shown once at creation and stored hashed. If you lose a key, revoke it from the dashboard and generate a replacement.

Do you sell cPanel and hosting add-on licences as well?

Yes. cPanel, Plesk, DirectAdmin, CloudLinux, LiteSpeed, Imunify360, KernelCare, JetBackup, Softaculous, WHMCS and more, from ₹95 a month on the same account as the APIs. They are billed monthly with no term, issued against your server IP in minutes, and installed either with a one-line SSH command or by us for free.