OTP SMS: the verification code doesn't wait in line.
Send one-time verification codes by SMS for actions such as sign-up, login, password reset and payment confirmation. OTP messages don't wait in line behind bulk sends; they go out right away. Buluthat can generate the code or you can provide it; verification is a single API call.
OTP SMS packages
Choose your credits and we will set them up with your application. Prices include taxes.
Packages exclusive to new subscribers are for customers just starting with the SMS service; they can be purchased in the first days after your SMS account is opened.
Credits of monthly packages are used until the end of the month you purchased.
Credits of yearly packages can be used for 1 year from the purchase date.
Notes
- Prices include 20% KDV and 10% ÖİV. Monthly packages are valid until month end, yearly packages for 1 year. The credit for an undelivered message is refunded.
- 1 credits = 1 SMS (160 characters; 155 in a message containing Ş ş Ğ ğ ç ı İ, 70 characters in a message containing emoji). A long message uses more than one credit.
- OTP packages are only for verification codes and are used first; when OTP credits run out, usage continues from SMS credits.
- An approved SMS sender ID is required for sending; once your sender ID documents are complete it is approved within 1-3 business days.
Features
Send without waiting
An OTP message does not enter the bulk campaign queue; it goes through a separate, priority path.
Ready-made verification
the code is sent with otp_send and the code the user entered is checked with otp_verify; you don't need to keep a separate code table.
The code is stored hashed
The code we generate is returned only once in the send response; in the database it is stored not as plain text but as a hash.
Duration and trial limit
The code's validity period and wrong-attempt allowance are limited; an expired or repeatedly wrong code is rejected.
Your own text
Edit the message template with the {kod}, {firma} and {sure} fields; you can also provide the 4-10 digit code yourself.
Separate OTP credits
OTP packages are separate and are used first; if OTP credits run out, sending continues from SMS credits, so no code goes unsent.
Limit against abuse
Repeated sends to the same number in a short time are limited; automated attacks do not drain your credits.
Delivery status
The delivered / not delivered status of each code appears in the report and reaches your system via webhook.
Voice fallback
Voice Verification, which reads the code by phone for users who can't receive SMS, is on the same infrastructure.
Start sending SMS in 4 steps
You upload your documents from the panel; we follow up the sender ID approval.
Your application
Fill in the form and choose the package you want. When your account is opened, your panel password arrives in your email.
Upload the documents
Send the company details, tax certificate, authorized person's ID, signature circular and undertaking from the panel.
Sender ID approval
Your SMS sender ID (3-11 characters) is approved within 1-3 business days if the documents are complete.
Send
Send in bulk from the panel with Excel or the directory, or connect to your software with the SMS API.
About OTP SMS
OTP is deducted from OTP credits first; when they run out, it continues from SMS credits. If both run out, nothing is sent and the API returns an error.
Credits of monthly SMS packages are valid until the end of the month you purchased; credits of yearly packages are valid for 1 year.
No. The credit for a message the carrier could not deliver is refunded to your account automatically.
No. A verification code is not a commercial message; an approved SMS sender ID is enough.
By default 3 minutes and 5 wrong attempts. The number of codes that can be sent to the same number within 10 minutes is also limited.
Stronger together
Bulk SMS, verification codes, inbound SMS and API — with your approved sender ID.