Two calls
Send a code, check a code
SMS verification is two requests. POST /api/Verify sends a code that the platform generates and returns a verification_id; POST /api/VerifyStatus takes that id and the code the user typed and answers V for verified or F for not.
The code is created and stored on our side, so it never has to pass through your database.
- SMS codes generated, sent and checked by the platform
- Viber OTP from an approved template, carrying a code your system generates
- Telegram codes through Telegram's Gateway, with SMS after them in the same campaign
- OTP statistics on the dashboard, separate from campaign volume
For developers
Verification in two requests
Send the code, then check what the user typed against the verification id. Field names are spelled exactly as the API spells them.
# 1. send the code — the response carries a verification_id
curl -X POST https://api.veloconnect.me/api/Verify \
-H "Content-Type: application/json" \
-d '{
"api_id": "YOUR_API_ID",
"phonenumber": "37412345678",
"sender_id": "VeloConnect"
}'
# 2. check what the user typed — status V or F
curl -X POST https://api.veloconnect.me/api/VerifyStatus \
-H "Content-Type: application/json" \
-d '{
"api_id": "YOUR_API_ID",
"verfication_id": 123456,
"verfication_code": 4829
}'
import os, requests
BASE = "https://api.veloconnect.me"
API_ID = os.environ["VELO_API_ID"]
sent = requests.post(
f"{BASE}/api/Verify",
json={"api_id": API_ID, "phonenumber": "37412345678",
"sender_id": "VeloConnect"},
timeout=15,
).json()
checked = requests.post(
f"{BASE}/api/VerifyStatus",
json={"api_id": API_ID,
"verfication_id": sent["verification_id"],
"verfication_code": int(user_input)},
timeout=15,
).json()
verified = checked["status"] == "V"
Three routes
Ways to send a code
-
SMS, generated for you
/api/Verify creates the code, sends it from your sender ID, and /api/VerifyStatus checks it.
-
Viber, from a template
/api/partners/viber-otp sends your code through an approved Viber OTP template, with parameters and a language.
-
Telegram, through its Gateway
The Telegram step of an OTP campaign delivers the code inside Telegram, checks the reply against a stored hash, and passes numbers Telegram cannot reach to the next channel.
-
Reported separately
OTP statistics on the dashboard, apart from campaign traffic, so a spike in one does not hide a problem in the other.
Verification questions
Which channels can carry a code?
SMS through /api/Verify, Viber through /api/partners/viber-otp using an approved template, and Telegram as a step in an OTP campaign.
Is there automatic fallback?
Inside a campaign, yes: with Telegram first and SMS second, a recipient Telegram cannot reach gets the SMS. The standalone SMS and Viber OTP calls each send on one channel, so a second attempt on another channel is a second call from your application.
Do I store the code?
Not for SMS: /api/Verify generates and stores it, and you submit the verification_id with whatever the user typed. For Viber OTP and Telegram codes your system supplies the code; Telegram codes are then stored hashed and checked by the platform.
Can I see verification volume separately?
Yes — the dashboard reports OTP statistics as their own series, which matters because verification traffic and campaign traffic fail for completely different reasons.
Add verification in an afternoon
Two endpoints, an API ID and a registered sender.