Verification methods and pricing
Verificahub supports several ways to verify a number. They all use the same endpoint, POST /v1/verify — only the method field changes.
Method comparison
| Method | method | How it verifies | Price per verification |
|---|---|---|---|
| Reverse flash-call | reverse_flash_call | The user calls our number; we confirm by Caller ID — no code | ₽0.25 |
| Flash Call | flash_call | A drop-call to the user's number; the code is the last digits of the incoming number | ₽0.80 |
| Telegram | telegram_otp | The code arrives in Telegram via the official bot | ₽1.20 |
| MAX Bot | max_bot | The code arrives in MAX after the user shares their number in the bot | ₽0.30 |
| MAX | max_otp | The code goes straight to the number in MAX, no bot | ₽2.00 |
| SMS | sms | A classic code over SMS — works on any phone | ₽3.00 |
| MTS ID | mts_id | MTS confirms on the SIM (no code entry); on fallback — a code over SMS | ₽2.00 |
| Voice code | pass_call | A robot calls and dictates the code | ₽2.40 |
Prices are indicative; see current rates at verificahub.ru.
Two integration patterns
Methods split into two types by how verification happens.
Automatic — no code entry
Only reverse_flash_call. You show the user a number (number_to_call), they call it, and you poll the session status until verified.
Code entry
telegram_otp, sms, flash_call, max_bot (and voice in the future). The user receives or reads a code, enters it, and you confirm it via POST /v1/verify/check.
:::tip Which method to choose Reverse flash-call is the cheapest and needs no code entry. SMS is the most expensive but works on any phone without messengers — a good fallback channel. :::