Virtual number API and SMM panel API for resellers
Sell our numbers and boosting from your own platform.
Two APIs, one balance. Numbers speak the SMS-Activate protocol and boosting speaks the standard SMM panel protocol, so most of the time you point code you already have at us and it works. Add funds once, resell at your own prices.
Getting started
Three steps, and none of them needs us to approve you.
- Get your keys. Create an account and open API keys. Both keys are already there: one for numbers, one for boosting.
- Add funds. Pay by Mobile Money, card or crypto. API orders spend the same balance as the website.
- Call it. One HTTPS request. No SDK to install, no OAuth, no sandbox key to swap out later.
curl "https://kamiverify.com/api/v2" \ -d "key=YOUR_SMM_KEY" \ -d "action=balance" # {"balance":"12.4400","currency":"USD"}
<?php $ch = curl_init('https://kamiverify.com/api/v2'); curl_setopt($ch, CURLOPT_POST, true); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query([ 'key' => 'YOUR_SMM_KEY', 'action' => 'balance', ])); $res = json_decode(curl_exec($ch), true); echo $res['balance'];
import requests r = requests.post('https://kamiverify.com/api/v2', data={ 'key': 'YOUR_SMM_KEY', 'action': 'balance', }) print(r.json()['balance'])
Authentication
You have two keys, not one. Each key opens one API:
api_keyv1, SMS numbers. Your numbers key. Works on /api/v1 and /stubs/handler_api.php.keyv2, SMM services. Your boosting key. Works on /api/v2.They are separate on purpose. You can give a developer or a child panel your boosting catalogue without letting them spend your balance on numbers, and you can replace one key after a leak without breaking the other integration.
A key only opens its own API. The boosting key sent to /api/v1 fails exactly like an unknown key, and the other way round too.
Both keys are on your API keys page, with a button to replace either one. There is no signature and no token to refresh.
v2 expects a POST form field. v1 accepts GET or POST: the SMS-Activate habit is GET, and most client libraries use it. A key in a URL ends up in server logs, browser history and referrer headers, so use POST wherever your library allows it.
Balance and pricing
API orders and website orders spend the same balance. There is no separate developer wallet and no minimum monthly spend.
Balances are kept in US dollars, and both APIs quote and charge in USD. The price the API gives you is the price you are charged.
You set your own prices for your own customers. We bill you the API price and nothing else: no revenue share, no fee per call.
v1 SMS numbers
Get a real number in one of 200+ countries, read the code it receives, and release it. The whole thing usually takes less than two minutes.
https://kamiverify.com/api/v1The usual path https://kamiverify.com/stubs/handler_api.php reaches the same handler. Most SMS-Activate libraries hard-code that path, so switching one to KamiVerify is usually a one-line change of host name.
Country ids follow the SMS-Activate list: 41 Cameroon, 19 Nigeria, 187 United States, 12 United States (virtual). getCountries returns all of them.
action=getBalanceWhat is on the account| Parameter | Type | What it is |
|---|---|---|
api_key required | string | Your numbers key. |
action required | string | The word getBalance. |
Replies ACCESS_BALANCE:12.44.
action=getCountriesCountries with numbers in stock| Parameter | Type | What it is |
|---|---|---|
api_key required | string | Your numbers key. |
action required | string | The word getCountries. |
Replies in JSON: {"41":{"id":41,"eng":"Cameroon"}}.
action=getNumbersStatusHow many numbers are free| Parameter | Type | What it is |
|---|---|---|
api_key required | string | Your numbers key. |
action required | string | The word getNumbersStatus. |
country | integer | Only this country. |
Replies in JSON, keyed service_country: {"wa_41":"12"}.
action=getPricesPrices and stock| Parameter | Type | What it is |
|---|---|---|
api_key required | string | Your numbers key. |
action required | string | The word getPrices. |
country | integer | Only this country. |
service | string | Only this service. |
Replies in JSON: {"41":{"wa":{"cost":0.31,"count":12}}}.
action=getNumberRent a number| Parameter | Type | What it is |
|---|---|---|
api_key required | string | Your numbers key. |
action required | string | The word getNumber. |
service required | string | Service code, for example wa for WhatsApp, tg for Telegram. |
country | integer | Country id. Leave it out, empty, or send any for the cheapest anywhere. |
maxPrice | decimal | Refuse a number above this price. |
Replies ACCESS_NUMBER:880412:237650112233: the id first, then the number. Keep the id, every later call needs it.
action=getStatusHas the code arrived?| Parameter | Type | What it is |
|---|---|---|
api_key required | string | Your numbers key. |
action required | string | The word getStatus. |
id required | integer | The id from getNumber. |
Replies STATUS_WAIT_CODE, then STATUS_OK:438201 when the code arrives, or STATUS_CANCEL if the rental ended.
action=setStatusMove the rental on| Parameter | Type | What it is |
|---|---|---|
api_key required | string | Your numbers key. |
action required | string | The word setStatus. |
id required | integer | The id from getNumber. |
status required | integer | 1 ready, 3 ask for another code, 6 finish, 8 cancel and refund. |
Replies ACCESS_READY, ACCESS_RETRY_GET, ACCESS_ACTIVATION or ACCESS_CANCEL.
A full rental, start to finish
# 1. get a number curl "https://kamiverify.com/api/v1?api_key=KEY&action=getNumber&service=wa&country=41" # ACCESS_NUMBER:880412:237650112233 # 2. ask every 5 seconds curl "https://kamiverify.com/api/v1?api_key=KEY&action=getStatus&id=880412" # STATUS_WAIT_CODE # STATUS_OK:438201 # 3. finish (or status=8 to cancel and be refunded) curl "https://kamiverify.com/api/v1?api_key=KEY&action=setStatus&id=880412&status=6" # ACCESS_ACTIVATION
<?php function kv1($q) { $q['api_key'] = 'YOUR_NUMBERS_KEY'; return trim(file_get_contents( 'https://kamiverify.com/api/v1?' . http_build_query($q))); } $res = kv1(['action'=>'getNumber', 'service'=>'wa', 'country'=>41]); if (strpos($res, 'ACCESS_NUMBER') !== 0) { throw new RuntimeException($res); // NO_NUMBERS, NO_BALANCE, BAD_KEY } list(, $id, $phone) = explode(':', $res); do { sleep(5); $st = kv1(['action'=>'getStatus', 'id'=>$id]); } while ($st === 'STATUS_WAIT_CODE'); if (strpos($st, 'STATUS_OK:') === 0) { echo substr($st, 10); // the code kv1(['action'=>'setStatus', 'id'=>$id, 'status'=>6]); }
import requests, time API = 'https://kamiverify.com/api/v1' KEY = 'YOUR_NUMBERS_KEY' def kv1(**q): return requests.get(API, params={'api_key': KEY, **q}).text.strip() res = kv1(action='getNumber', service='wa', country=41) if not res.startswith('ACCESS_NUMBER'): raise RuntimeError(res) _, oid, phone = res.split(':') while True: time.sleep(5) st = kv1(action='getStatus', id=oid) if st != 'STATUS_WAIT_CODE': break if st.startswith('STATUS_OK:'): print(st[10:]) kv1(action='setStatus', id=oid, status=6)
Every reply v1 can give
ACCESS_NUMBER:id:phoneNumber issued. The id comes first.STATUS_WAIT_CODENo code yet. Keep asking.STATUS_OK:codeThe code arrived. Stop asking.STATUS_CANCELCancelled, expired, or already finished.ACCESS_READYstatus=1 accepted.ACCESS_RETRY_GETstatus=3 accepted: another code requested.ACCESS_ACTIVATIONstatus=6 accepted: rental closed.ACCESS_CANCELstatus=8 accepted: refunded to your balance.And every error
BAD_KEYMissing or wrong key, or the account is suspended.BAD_ACTIONNo such action.BAD_SERVICENo service was sent.BAD_STATUSNot 1, 3, 6 or 8, or the rental has already ended.NO_NUMBERSNothing in stock for that pair. Try another country.NO_BALANCEAdd funds. Nothing was charged.NO_ACTIVATIONThat id is not yours, or does not exist.EARLY_CANCEL_DENIEDCancelled in the first two minutes. Wait, then try again.ERROR_SQLWe could not record it. Nothing was charged.v2 SMM services
Followers, views, likes and comments on the big platforms. You order by link and quantity, and you can read the progress while it runs.
https://kamiverify.com/api/v2always POSTaction=servicesThe full catalogue with prices| Parameter | Type | What it is |
|---|---|---|
key required | string | Your boosting key. |
action required | string | The word services. |
action=addPlace an order| Parameter | Type | What it is |
|---|---|---|
key required | string | Your boosting key. |
action required | string | The word add. |
service required | integer | Service id from services. |
link required | string | The post or profile link the order is for. |
quantity required | integer | How many. Between the service minimum and maximum. |
action=statusProgress of one order| Parameter | Type | What it is |
|---|---|---|
key required | string | Your boosting key. |
action required | string | The word status. |
order required | integer | The order id returned by add. |
action=ordersYour recent orders| Parameter | Type | What it is |
|---|---|---|
key required | string | Your boosting key. |
action required | string | The word orders. |
limit | integer | How many, newest first. 100 by default, 300 at most. |
action=multistatusUp to 100 orders in one call| Parameter | Type | What it is |
|---|---|---|
key required | string | Your boosting key. |
action required | string | The word multistatus. |
orders required | string | Order ids separated by commas, 100 at most. status accepts this too. The reply is keyed by order id, and an unknown id gets its own error instead of failing the whole call. |
# place it curl "https://kamiverify.com/api/v2" \ -d "key=YOUR_SMM_KEY" -d "action=add" \ -d "service=1043" \ -d "link=https://instagram.com/p/Cx1y2z3" \ -d "quantity=1000" # {"order":238104} # read it back curl "https://kamiverify.com/api/v2" \ -d "key=YOUR_SMM_KEY" -d "action=status" -d "order=238104" # {"charge":"0.2700","start_count":"1240","status":"In progress","remains":"320","currency":"USD"}
<?php function kv2($fields) { $ch = curl_init('https://kamiverify.com/api/v2'); curl_setopt_array($ch, [CURLOPT_POST => true, CURLOPT_RETURNTRANSFER => true, CURLOPT_POSTFIELDS => http_build_query($fields + ['key' => 'YOUR_SMM_KEY'])]); return json_decode(curl_exec($ch), true); } $r = kv2([ 'action' => 'add', 'service' => 1043, 'link' => 'https://instagram.com/p/Cx1y2z3', 'quantity' => 1000, ]); if (isset($r['error'])) { throw new RuntimeException($r['error']); } echo 'order ' . $r['order'];
import requests API = 'https://kamiverify.com/api/v2' KEY = 'YOUR_SMM_KEY' def kv2(**f): return requests.post(API, data={'key': KEY, **f}).json() r = kv2(action='add', service=1043, link='https://instagram.com/p/Cx1y2z3', quantity=1000) if 'error' in r: raise RuntimeError(r['error']) print('order', r['order'])
Order statuses
PendingAccepted, not started yet.In progressRunning. remains counts down.CompletedDelivered in full.PartialPart delivered. The rest is refunded to your balance automatically.CanceledNot delivered. Refunded in full.ProcessingBeing passed to the provider.Errors
The two protocols report problems differently, each following its own standard. v1 replies with a bare word such as BAD_KEY: every one is listed in the v1 section. v2 replies in JSON, as below.
v2 errors come back as 200 OK with an error key, which is what panel software expects. Check for the key, not the HTTP status.
{ "error": "Not enough balance" }Incorrect API keyMissing, mistyped, or replaced since you saved it.Not enough balanceAdd funds. Nothing was charged and no order was made.Incorrect service IDThe service does not exist or is no longer sold.Incorrect quantityBelow the service minimum or above its maximum.Incorrect order IDNo such order, or it belongs to someone else.The account is inactiveThe account is suspended. Contact support.Rate limits
| Action | Guidance | Why |
|---|---|---|
| getStatus, status | 1 per second per order | Ask every 5 seconds. Faster does not bring codes sooner. |
| multistatus | 100 ids per call | Use it instead of looping over single orders. |
| add, getNumber | 10 per second | Per account. |
| services | 1 per minute | The catalogue barely moves. Keep a copy for an hour. |
Reseller rules
Short, and we mean them.
- Set your own prices. We bill you the API price. What you charge your customers is your business.
- Your customers are yours. We never contact them and never see who they are, only the orders you place.
- Support your own users first. If the problem turns out to be ours, bring it to us with the order id.
- Lawful use only. Numbers are for receiving codes on accounts the user is entitled to open. Using them to impersonate people, take over accounts or commit fraud ends the account: yours, not only theirs.
- Do not resell the key. One key, one business. Give your customers your own interface, not our credentials.
No contract, no minimum volume, no monthly fee. Stop whenever you like: what is left on your balance stays yours to spend.
Get your keys and start
Create an account, add funds, and place your first API order in a few minutes.