从这里开始
Your first request in four steps
List your connected mobiles and copy the target SID.
Create a notification with a title and message.
Poll the list endpoint by SID.
Use distribued_status and GMT timestamps to track distribution.
Official mobile application
The secure bridge between your phone, dashboard and API.
SMS and call operations pass through the official SMSMobileAPI app installed on your connected phone. The app securely pairs the device with your account, synchronizes authorized events and links the mobile network to the dashboard and REST API.
- Signed releases distributed through the official Google Play and Apple App Store listings
- Google and Apple platform review, signing and distribution controls
- Secure device pairing, HTTPS transport and authenticated API access
- Only the permissions required for the mobile features you enable
验证
Keep credentials on your server
Notification endpoints use the apikey parameter. A target phone is identified by sid when sending and by sid or sidentifiant when listing.
POST · GET
Send a notification
https://api.smsmobileapi.com/notification/sendCreates an internal notification for one connected device.
Use it for operational alerts that should appear on a managed phone.
参数
| 姓名 | 类型 | Requirement | 描述 |
|---|---|---|---|
apikey |
细绳 | 必需的 | 您的 API 密钥。 |
sid |
细绳 | 必需的 | Target mobile SID. |
title |
细绳 | 选修的 | Notification title; defaults to Notification. |
message |
细绳 | 必需的 | Notification content. |
type |
细绳 | 选修的 | Notification type; defaults to notification. |
Request example
curl -X POST "https://api.smsmobileapi.com/notification/send" \
-d "apikey=YOUR_API_KEY" \
-d "sid=TARGET_SIDENTIFIANT" \
--data-urlencode "title=Order ready" \
--data-urlencode "message=Order #1042 is ready for collection."示例回复
{
"success": true,
"message": "Notification created.",
"id": 22087,
"apikey": "YOUR_API_KEY",
"sid": "508b004b4aadacc4"
}Want to run this request? Connect your API key at the top of the page to unlock the interactive tester.
Connect key ↑- Creation and distribution are separate events. Use the list endpoint to verify delivery to the device.
得到
List notifications
https://api.smsmobileapi.com/notification/list/Returns up to 200 notifications ordered from newest to oldest.
Use it to monitor distribution and build a notification history.
参数
| 姓名 | 类型 | Requirement | 描述 |
|---|---|---|---|
apikey |
细绳 | 必需的 | 您的 API 密钥。 |
sidentifiant |
细绳 | 选修的 | Filter by target mobile. |
sid |
细绳 | 选修的 | Alias of sidentifiant. |
distribued |
0 | 1 | 选修的 | 1 for distributed, 0 for not distributed. |
date_from |
YYYY-MM-DD | 选修的 | Start date. |
date_to |
YYYY-MM-DD | 选修的 | End date. |
Request example
curl "https://api.smsmobileapi.com/notification/list/?apikey=YOUR_API_KEY&sidentifiant=TARGET_SIDENTIFIANT&distribued=1"示例回复
{
"success": true,
"count": 1,
"data": [{
"sidentifiant": "508b004b4aadacc4",
"title": "Order ready",
"message": "Order #1042 is ready for collection.",
"distribued": "1",
"distribued_status": "distributed",
"distributed_at_gmt": "2026-03-18 10:18:30",
"distributed_at_unix": 1773829110,
"sent_at_gmt": "2026-03-18 10:15:03",
"sent_at_unix": 1773828903
}]
}Want to run this request? Connect your API key at the top of the page to unlock the interactive tester.
Connect key ↑- All sent and distributed timestamps are GMT.
故障排除
Errors and safe retries
Read the HTTP status and the JSON error field before retrying. Do not retry validation or authentication failures without correcting the request first.
| HTTP | 代码 | What to do |
|---|---|---|
| 400 | Missing required param | apikey, sid or message is missing. |
| 400 | Invalid date format | Use YYYY-MM-DD for date_from and date_to. |
| 400 | Invalid distribued value | Only 0 or 1 is accepted. |
| 500 | DB connection / query failed | The notification service could not complete the operation. |
需要帮助吗？
Bring the request context—not your secrets.
Share the endpoint, timestamp, HTTP status and sanitized response. Never include API keys, tokens or private message content.
