SaaS
You were going to build this, and it was going to take longer than you thought
Verification looks like a weekend. Then it is code generation and storage, a second channel for the numbers the first cannot reach, sender IDs per country, and delivery evidence when support asks why a customer never got the code.
The platform carries the sending side of that — SMS codes it generates and checks, Viber and Telegram as further channels, registered senders and per-message records — so your team owns the product logic around it.
- SMS verification in two API calls, with the code generated and stored on our side
- One API for SMS, WhatsApp, Viber and email, plus Telegram for codes
- Delivery reports to your callback URL, and link-event webhooks with recorded deliveries
- Idempotency keys on short-link creation, so a retried request does not duplicate a link
Use cases
What product teams use it for
-
Signup verification
Confirm a phone number at registration with an SMS code, or a Telegram code with SMS after it.
-
Login and step-up authentication
One-time codes for sensitive actions, generated and checked by the platform.
-
Lifecycle and onboarding messaging
Activation nudges on the channel a user actually reads, triggered by your own events.
-
Product and incident notifications
Reach affected users quickly, with delivery evidence per recipient.
-
Support conversations
Replies on WhatsApp, Viber or two-way SMS land in one inbox your support team works.
-
Trial and billing reminders
Messages with short links, and clicks attributed per user.
Channels
Which channels tend to matter here
Most product teams start with verification and add channels as the use cases arrive.
SaaS questions
How long does integration take?
SMS verification is two endpoints and an API ID — most teams have it working the same day. Sending a message is one POST. The longer items are the ones outside the code: sender ID registration and, for WhatsApp, business verification.
Is there an API key model separate from user logins?
Yes. Programmatic access uses an API ID, with an IP allowlist you set, separate from the JWT-based access your team uses in the dashboard.
Can we get events back out?
Delivery reports for SMS sent through the API are posted to your callback URL, and webhook subscriptions push short-link events with every delivery attempt recorded. Inbound messages are read from the API rather than pushed.
Ship the messaging feature this sprint
Verification, notifications and a shared inbox behind one API.