Introduction
The SMSUP Plus API lets your system send SMS and OTP and manage recipient data directly over HTTPS. This page covers the overview, request/response conventions and your first request.
What the API offers
| Group | Path | Purpose |
|---|---|---|
| SMS | /sms/send, /sms/preview, /sms/senderlist, /sms/loginfo | Send SMS, calculate credit before sending, list approved sender names, search send history |
| OTP | /OTP/requestotp, /OTP/verifyotp, /OTP/resendotp | Send an OTP, verify it, resend it |
| URL Shortener | /shorten/create, /shorten/list, /shorten/stats/:code, /s/:code | Create short links, list them and view click stats |
| Contacts | /Person/... | Create/update/delete/search contacts and their destinations |
| Tags | /Tag/... | Group contacts with tags |
| Blacklist | /Blacklist/... | Manage numbers that must not be messaged |
| Consent | /Consent/... | Record and check consent (PDPA) |
| LINE | /line/send, /line/dashboard | Send messages through LINE tokens configured on your account |
| Callback | notifyUrl in /sms/send | Receive delivery status (Delivery Report) |
Base URL
https://public-api.smsup-plus.comEvery endpoint uses HTTPS and requires authentication (except the /s/:code redirect). See Authentication.
Request / Response conventions
| Topic | Details |
|---|---|
| Request body | POST endpoints take JSON — send Content-Type: application/json |
| Query / Path | GET endpoints take query-string or path values, e.g. /sms/loginfo?bulkId=..., /Consent/checkconsent/{mobile} |
| Response | JSON (UTF-8) on every endpoint except /s/:code, which answers an HTTP 302 redirect |
| Path case | Paths are case-sensitive (/OTP/..., /Person/... must be written as documented) |
| Thai text | Send as plain UTF-8, no extra encoding needed |
Phone numbers (SMS / OTP)
The system strips every non-digit character, then converts the number to 66XXXXXXXXX.
| Input | After normalisation | Result |
|---|---|---|
0812345678 | 66812345678 | Accepted |
+66 81-234-5678 | 66812345678 | Accepted |
66812345678 | 66812345678 | Accepted |
812345678 (9 digits) | 66812345678 | Accepted |
02123456 | 662123456 | Rejected (must be 11 digits starting with 66) |
A rejected number is answered REJECTED in that number's result and is neither sent nor charged.
TIP
The Blacklist and Consent APIs use their own number check (spaces, dashes and parentheses removed, 10–15 digits). See each endpoint page.
Message length and credit
| Message type | 1 credit | Long message (per credit) |
|---|---|---|
| Contains non-ASCII characters (e.g. Thai) | Up to 70 characters | 67 characters (71–134 characters = 2 credits) |
| ASCII only | Up to 160 characters | 153 characters (161–306 characters = 2 credits) |
Maximum message length is 1,600 characters and at most 1,000 destinations per request. Use /sms/preview to calculate credit before sending.
Quick start
- Sign in to the customer portal and create an API key in the customer portal.
- Copy the key starting with
smsk_and store it safely (the full key is shown only once). - Make sure your sender name is approved — check with
GET /sms/senderlist. - Send your first request as shown below.
First request: send an SMS
curl -X POST 'https://public-api.smsup-plus.com/sms/send' \
-H 'Authorization: Bearer <API_KEY>' \
-H 'Content-Type: application/json' \
-d '{
"messages": [
{
"from": "MYBRAND",
"destinations": [{ "to": "0812345678" }],
"text": "Hello from SMSUP Plus"
}
]
}'const res = await fetch('https://public-api.smsup-plus.com/sms/send', {
method: 'POST',
headers: { Authorization: 'Bearer <API_KEY>', 'Content-Type': 'application/json' },
body: JSON.stringify({
messages: [
{ from: 'MYBRAND', destinations: [{ to: '0812345678' }], text: 'Hello from SMSUP Plus' },
],
}),
})
console.log(await res.json())Successful response (HTTP 200):
{
"bulkId": "6f1c2a8e-1b7a-4c35-9d0e-2b8f6f3e9a11",
"details": [
{
"messageId": "0b7e4d0c-5a3f-4f0e-8a51-4e2d9c7b1f20",
"mobile": "66812345678",
"to": "66812345678",
"from": "MYBRAND",
"credit": "1.00",
"shorturl": "N",
"status": {
"code": "101",
"name": "PENDING",
"description": "Pending -Message has been accepted by the system"
}
}
]
}PENDING means the message was accepted into the queue. Track delivery with the Delivery Report callback or /sms/loginfo.
Next steps
- Authentication — header formats, rate limits, Idempotency-Key
- Error Codes — every error shape
- Send SMS — all send parameters
