SMS Verification API

Buy numbers and read verification codes over a JSON API. No KYC, crypto only.

REST · JSONOpenAPI 3.1 OpenAPI spec →

How does the API fit together?

1. Create an account and store the seed it returns. It is the only credential and cannot be reset.
2. Create a top-up, send the crypto, and wait for it to be credited.
3. Buy a number for the service and country you need — the balance is debited instantly.
4. Poll for the SMS code. No code before the order expires means an automatic refund.

Fund once, buy many: a single top-up covers as many numbers as its balance allows, so only the first purchase waits on a confirmation.

Authentication

Send the account seed as a bearer token. There is no separate API key, and no login call — the seed is the credential.

Authorization: Bearer YOUR-SEED-PHRASE

The catalog endpoints need no authentication at all, so you can browse services, countries and prices before an account exists. Everything that touches money or orders requires the header.

Base URL

All endpoints are relative to:

https://www.otpdrop.com/api/v1

Responses are JSON. POST bodies are accepted as application/json or application/x-www-form-urlencoded.

Errors

Failures return a non-2xx status and a single error object.

{
  "error": {
    "code": "invalid_request",
    "message": "unknown service: \"whatsap\""
  }
}

Common 422 messages:

Are there rate limits?

There is no published quota and no API key to throttle, but the endpoints are not free to call in a loop. Two of them are polling endpoints and deserve particular care.

Traffic that looks like an attack will be blocked at the edge without a courtesy 429. If you have a legitimate reason to poll harder, ask on the contact page first.

What does a complete integration look like?

Account to code in six calls. Everything below is real: paste it and it runs.

# 1. Create an account and keep the seed
SEED=$(curl -s -X POST https://www.otpdrop.com/api/v1/accounts | jq -r .seed)

# 2. Fund it — send the coin_amount to the address returned
curl -s -X POST https://www.otpdrop.com/api/v1/topups \
  -H "Authorization: Bearer $SEED" \
  -H 'content-type: application/json' \
  -d '{"amount_usd": 25, "coin": "USDT"}'

# 3. Poll until the deposit is credited
curl -s https://www.otpdrop.com/api/v1/topups/TOPUP_ID \
  -H "Authorization: Bearer $SEED" | jq .status

# 4. Check the price before committing
curl -s 'https://www.otpdrop.com/api/v1/quote?service=telegram&country=us'

# 5. Buy — the balance is debited and the number issued at once
ORDER=$(curl -s -X POST https://www.otpdrop.com/api/v1/orders \
  -H "Authorization: Bearer $SEED" \
  -H 'content-type: application/json' \
  -d '{"service": "telegram", "country": "us"}' | jq -r .order_id)

# 6. Poll for the code
until curl -s https://www.otpdrop.com/api/v1/orders/$ORDER/sms \
  -H "Authorization: Bearer $SEED" | jq -e .code; do sleep 4; done

The same sequence in Python, without the shell:

import time, requests

API = "https://www.otpdrop.com/api/v1"
seed = requests.post(f"{API}/accounts").json()["seed"]
auth = {"Authorization": f"Bearer {seed}"}

topup = requests.post(f"{API}/topups", headers=auth,
                      json={"amount_usd": 25, "coin": "USDT"}).json()
print("send", topup["coin_amount"], topup["coin"], "to", topup["address"])

while requests.get(f"{API}/topups/{topup['topup_id']}",
                   headers=auth).json()["status"] != "credited":
    time.sleep(15)

order = requests.post(f"{API}/orders", headers=auth,
                      json={"service": "telegram", "country": "us"}).json()
print("number:", order["phone"])

while True:
    sms = requests.get(f"{API}/orders/{order['order_id']}/sms",
                       headers=auth).json()
    if sms["arrived"]:
        print("code:", sms["code"])
        break
    time.sleep(4)

MCP server

The same operations are available over the Model Context Protocol at https://www.otpdrop.com/mcp, as eleven tools. Add it to Claude Code with:

claude mcp add --transport http otpdrop https://www.otpdrop.com/mcp

Setup and the full tool list are on the Agents page.

Discovery files

Machine-readable descriptions of the service, all served without authentication.

Frequently asked questions

Does the OTPDrop API need an API key?

No. There is nothing to apply for and no approval step. The account seed is the credential, sent as a bearer token, and the catalogue endpoints need no credential at all.

What does the OTPDrop API cost?

Nothing beyond the numbers you buy. There is no subscription, no per-call charge and no minimum volume — you pay the same prices as anyone using the website.

Which programming languages work with the API?

Any language that can make an HTTPS request. It is plain JSON over HTTP with a bearer header, so there is no SDK to install and nothing to keep in step with our releases.

What happens if the SMS code never arrives?

The order refunds itself to your balance when it expires, and you can cancel earlier through the website. You are charged for delivered codes, not for attempts.

Is the REST API the same as the MCP server?

Yes, deliberately. Each REST endpoint is a translation of one MCP tool call, so the two cannot drift apart: a fix to one is a fix to both. Pick whichever suits your client.

Can you test the API without spending anything?

The catalogue, quotes and account creation are free, so you can build and test most of an integration before funding a balance. Only buying costs money.