Product Channels Pricing Documentation
ENRU
Log inGet test access
Available now: VK · Telegram · email

Connect OTP through VK, Telegram, and email with one API.

OTPilot selects an available channel, records delivery statuses, and shows the cost of every verification in one place.

Get test access→ View API

0 ₽ · No card · No charges · No real delivery

1 API

One contract for every channel

3 channels

VK, Telegram, and email

0 ₽

Test mode

One integration

One API connects all three delivery channels.

Create and check a verification through one predictable REST contract instead of maintaining a separate integration for each channel.

POST /v1/verifications 
1curl https://otpilot.ru/v1/verifications \
2  -H 'Authorization: Bearer $OTPILOT_API_KEY' \
3  -H 'Idempotency-Key: login-4921' \
4  -H 'Content-Type: application/json' \
5  -d '{
6    "external_user_id": "user_123",
7    "phone": "+79991234567",
8    "channels": { "allowed": ["telegram", "vk", "email"] }
9  }'
channelslive
Telegram VK Email
✱✱✱✱
Test mode

Check approved, expired, and error states before the first real message.

The test mode uses the production API contract with synthetic delivery. Rehearse success, expiration, an invalid code, an unavailable channel, and rate limiting without charges.

Verification resulttest mode
statusapproved
channeltelegram
latency1.2s
attempts1 of 5
Sandbox key delivers nothing and charges nothing: the code is always 000000, the API contract matches production.
Get test access Open docs
Visible operations

See verification outcomes and which channels deliver codes to users.

The dashboard brings delivery attempts, verification results, cost, and the selected channel into one operational view. The channel mix shows the business which channels actually deliver codes to its audience without claiming to know user preferences.

Verifiable foundation

Inspect how OTPilot works before you integrate it.

No customer logos or promised SLA numbers: use the live technical artifacts to evaluate the API contract, request safeguards, and event authenticity.

API

API documentation

Review ready-to-run requests, responses, error models, and integration guidance in one readable guide.

Open API docs → HMAC

Signed webhooks

Verifiable events, hash-only codes and keys, rate limits, and explicit responsibility boundaries.

Review security → ID

Safe retries

Repeat a request without creating a duplicate, then inspect documented states and ready-to-run REST examples.

Read documentation →

Run your first OTP flow in test mode.

Create an account, get test access, and send the first API request without a card, charges, or real messages. When you are ready for live delivery, enable production in the dashboard.

Get test access→ Dashboard