Produktionsbereite mobile InfrastrukturHTTPS API · Android & iOS · Dokumentiert Ende an EndeEntdecken Sie die Plattform
SMSMobileAPISMSMobileAPIMobile Infrastruktur, verbunden
ArmaturenbrettKostenloses Konto erstellen
PLATTFORMAPI-erste ArchitekturSicherheitsvorrichtungspaarungSichtbarkeit der LieferungSteuerung von MehrfachgerätenVersionierte Dokumentation
Entwickler-Hub/Benachrichtigungs-API

PUSH · 2 documented operations

Notification API documentation

Send internal notifications to a specific connected mobile and retrieve their distribution history.

Mobile notifications connected to real-time call and analytics data
REST base URLhttps://api.smsmobileapi.com

JSON responses · HTTPS required · UTF-8

Connect your API key

Connect once, then test endpoints across SMS, calls, notifications, WhatsApp and email.

Hier beginnen

Your first request in four steps

1

List your connected mobiles and copy the target SID.

2

Create a notification with a title and message.

3

Poll the list endpoint by SID.

4

Use distribued_status and GMT timestamps to track distribution.

The secure SMSMobileAPI mobile app connecting a phone to the web dashboard and REST API for SMS and call operations
Encrypted mobile-to-platform connection

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.

1Mobile appPairs the phone and its SIM 2Encrypted linkAuthenticates and protects data in transit 3Dashboard & APIControls workflows and activity
  • 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
Get the official SMSMobileAPI app on Google Play Download the official SMSMobileAPI app on the Apple App Store
Capabilities depend on the permissions and background access allowed by Android or iOS.

Authentifizierung

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

#
ENDPOINThttps://api.smsmobileapi.com/notification/send

Creates an internal notification for one connected device.

When to use it

Use it for operational alerts that should appear on a managed phone.

Parameter

NameTypRequirementBeschreibung
apikey Zeichenkette Erforderlich Ihr API-Schlüssel.
sid Zeichenkette Erforderlich Target mobile SID.
title Zeichenkette Optional Notification title; defaults to Notification.
message Zeichenkette Erforderlich Notification content.
type Zeichenkette Optional Notification type; defaults to notification.

Request example

cURL
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."

Beispielantwort

JSON
{
  "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 ↑
Good to know
  • Creation and distribution are separate events. Use the list endpoint to verify delivery to the device.
ERHALTEN

List notifications

#
ENDPOINThttps://api.smsmobileapi.com/notification/list/

Returns up to 200 notifications ordered from newest to oldest.

When to use it

Use it to monitor distribution and build a notification history.

Parameter

NameTypRequirementBeschreibung
apikey Zeichenkette Erforderlich Ihr API-Schlüssel.
sidentifiant Zeichenkette Optional Filter by target mobile.
sid Zeichenkette Optional Alias of sidentifiant.
distribued 0 | 1 Optional 1 for distributed, 0 for not distributed.
date_from JJJJ-MM-TT Optional Start date.
date_to JJJJ-MM-TT Optional End date.

Request example

cURL
curl "https://api.smsmobileapi.com/notification/list/?apikey=YOUR_API_KEY&sidentifiant=TARGET_SIDENTIFIANT&distribued=1"

Beispielantwort

JSON
{
  "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 ↑
Good to know
  • All sent and distributed timestamps are GMT.

Fehlerbehebung

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.

HTTPCodeWhat to do
400Missing required paramapikey, sid or message is missing.
400Invalid date formatUse YYYY-MM-DD for date_from and date_to.
400Invalid distribued valueOnly 0 or 1 is accepted.
500DB connection / query failedThe notification service could not complete the operation.
Retry ruleRetry only transient 429 and 5xx responses. Start after 1 second, then back off to 2, 4 and 8 seconds.

Brauchen Sie Hilfe?

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.

Contact API support →