One-time codes
Sign-in, registration, password reset, payment confirmation.
OTP and notifications
Codes and notifications your customers are waiting for.
Login and payment codes, order statuses, appointment reminders: your system sends the request, Messedo delivers the SMS and reports the result.
What it is used for
Messages triggered by an event, not by a campaign.
Order and payment statuses
Order accepted, shipped, ready for pickup; payment received.
Reminders
Appointments, visits, payment due dates, the end of a subscription.
Service alerts
A new sign-in to the account, changed details, important account events.
How it works
A request from your system — a report back.
- POST /sms/send with the sender, the numbers and the text; the answer has the message ID for each number
- lifetime: how long the operator keeps trying — useful for codes that expire
- The final status comes to your URL (repeated if your server did not answer) or by POST /sms/status
- Up to 50 requests per second and up to 500 numbers in one request
- The token can be limited to your servers' IP addresses
{
"originator": "YourBrand",
"phones": ["380501234567"],
"text": "Your code: 4821",
"lifetime": 300
}
HTTP 200
{"success_request":{"info":{"380501234567":391876210}}}
Getting started
From registration to the first code.
01
Account and token
Register and copy the API token: dashboard → Integrations → SMS API.
02
Test request
Send the first request to your own number from the test sender created at registration, using the test balance.
03
Your Sender ID
Submit your brand name in the dashboard; in Ukraine approval usually takes up to 7 business days. New texts may go through moderation first.
Connect codes and notifications.
Need SMPP, a high volume or help with the integration? Write to us.