Hier beginnen
Your first request in four steps
Connect and enable WhatsApp for a supported mobile.
Confirm the recipient with the number-check endpoint.
Send with waonly=yes.
For inbound messages, activate retrieval, synchronize, then call /getwa.
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
Authentifizierung
Keep credentials on your server
Use apikey for direct integrations. OAuth2 client credentials are available for server-side applications; request a token and send it as Authorization: Bearer ACCESS_TOKEN.
POST · GET
Send a WhatsApp message
https://api.smsmobileapi.com/sendsmsSends a WhatsApp text or supported media through the connected environment.
Use it for individual recipients or a dashboard contact group.
Parameter
| Name | Typ | Requirement | Beschreibung |
|---|---|---|---|
apikey |
Zeichenkette | Erforderlich | Your API key; omit when using a Bearer token. |
recipients |
phone | Erforderlich | Country code plus number, without + or 00. |
message |
Zeichenkette | Erforderlich | Text body; multiple lines are supported. |
waonly |
Ja | Erforderlich | Must be yes to request WhatsApp-only delivery. |
url_media |
HTTPS URL | Optional | Public PDF, document, archive or JPG/PNG URL. |
url_media_shorted |
Ja | Optional | Use a shortened download URL with PDF preview mode. |
pdf_with_image |
Ja | Optional | Add an image preview for a PDF. |
encrypt_message |
Ja | Optional | Require recipient-side decryption. |
contactGroup |
GUID | Optional | Send to every contact in a dashboard group. |
Request example
curl -X POST "https://api.smsmobileapi.com/sendsms?waonly=yes" \
-d "apikey=YOUR_API_KEY" \
-d "recipients=191728660" \
--data-urlencode "message=Your order is ready."
Beispielantwort
{
"result": {
"error": 0,
"sent": "1",
"id": "MESSAGE_GUID",
"send_with_whatsapp": "1"
}
}
Want to run this request? Connect your API key at the top of the page to unlock the interactive tester.
Connect key ↑- Supported media URLs must be public HTTPS resources.
- WhatsApp formatting: *bold*, _italic_, ~strikethrough~ and triple-backtick monospace.
POST · GET
Resend an unsent WhatsApp message
https://api.smsmobileapi.com/resendwa/Retries a WhatsApp message that currently has an error status.
Use it after diagnosing a failed WhatsApp log entry.
Parameter
| Name | Typ | Requirement | Beschreibung |
|---|---|---|---|
apikey |
Zeichenkette | Erforderlich | Ihr API-Schlüssel. |
guid |
Zeichenkette | Erforderlich | GUID of the failed message. |
Request example
curl "https://api.smsmobileapi.com/resendwa/?apikey=YOUR_API_KEY&guid=MESSAGE_GUID"
Want to run this request? Connect your API key at the top of the page to unlock the interactive tester.
Connect key ↑- Only failed messages are eligible for resend.
ERHALTEN
Activate inbound retrieval
https://api.smsmobileapi.com/getwa/active/Activates, deactivates or toggles WhatsApp message retrieval.
Call it once before using inbound WhatsApp synchronization.
Parameter
| Name | Typ | Requirement | Beschreibung |
|---|---|---|---|
apikey |
Zeichenkette | Erforderlich | Ihr API-Schlüssel. |
statut |
0 | 1 | x | Optional | 1 activates, 0 deactivates, x or omission toggles the current state. |
Request example
curl "https://api.smsmobileapi.com/getwa/active/?apikey=YOUR_API_KEY&statut=1"
Beispielantwort
{
"success": true,
"read_message_active": 1,
"status_note": "Activated"
}
Want to run this request? Connect your API key at the top of the page to unlock the interactive tester.
Connect key ↑- Inbound retrieval is disabled by default for privacy.
ERHALTEN
Synchronize inbound messages
https://api.smsmobileapi.com/getwa/synchronisation/Requests a fresh WhatsApp synchronization before retrieval.
Call it immediately before /getwa when your application needs current inbound data.
Parameter
| Name | Typ | Requirement | Beschreibung |
|---|---|---|---|
apikey |
Zeichenkette | Erforderlich | Ihr API-Schlüssel. |
Request example
curl "https://api.smsmobileapi.com/getwa/synchronisation/?apikey=YOUR_API_KEY"
Beispielantwort
{
"error": "0",
"messages": "synchronized",
"expire_at": "2026-03-11 12:27:00",
"expire_at_unix": "1773232020"
}
Want to run this request? Connect your API key at the top of the page to unlock the interactive tester.
Connect key ↑- Synchronization is for receiving messages only. Do not call it before sending.
ERHALTEN
Retrieve WhatsApp messages
https://api.smsmobileapi.com/getwaReturns synchronized inbound WhatsApp messages.
Use it after activating and synchronizing inbound retrieval.
Parameter
| Name | Typ | Requirement | Beschreibung |
|---|---|---|---|
apikey |
Zeichenkette | Erforderlich | Ihr API-Schlüssel. |
before |
Unix timestamp | Optional | Return records before this timestamp. |
date |
JJJJ-MM-TT | Optional | Return records for one date. |
message_type |
text | audio | Optional | Filter text messages or audio messages converted to text; omit for both. |
Request example
curl "https://api.smsmobileapi.com/getwa/?apikey=YOUR_API_KEY&message_type=text"
Beispielantwort
{
"date": "2026-03-11",
"hour": "12:27:00",
"timestamp": "1773232020",
"number": "19176728660",
"contact": "SMSMobileAPI",
"message": "When will I receive my order?",
"guid": "652fcfc0-12a8-46f5-b5ba-9391135b8b4c"
}
Want to run this request? Connect your API key at the top of the page to unlock the interactive tester.
Connect key ↑
ERHALTEN
Check a WhatsApp number
https://api.smsmobileapi.com/whatsapp/checknumber/Checks whether a phone number is available on WhatsApp.
Use it before sending to reduce avoidable failures.
Parameter
| Name | Typ | Requirement | Beschreibung |
|---|---|---|---|
apikey |
Zeichenkette | Erforderlich | Ihr API-Schlüssel. |
recipients |
phone | Erforderlich | Country code plus number, without + or 00. |
Request example
curl "https://api.smsmobileapi.com/whatsapp/checknumber/?apikey=YOUR_API_KEY&recipients=19176728660"
Beispielantwort
{
"contact_found_on_whatsapp": "yes",
"recipients": "19176728660"
}
Want to run this request? Connect your API key at the top of the page to unlock the interactive tester.
Connect key ↑
POST
Create an OAuth2 access token
https://api.smsmobileapi.com/oauth2/tokenExchanges client credentials for a Bearer token.
Use it for server-to-server integrations where short-lived credentials are preferred.
Parameter
| Name | Typ | Requirement | Beschreibung |
|---|---|---|---|
grant_type |
Zeichenkette | Erforderlich | Must be client_credentials. |
client_id |
Zeichenkette | Erforderlich | Client ID from the dashboard. |
client_secret |
Zeichenkette | Erforderlich | Client secret from the dashboard. |
Request example
curl -X POST "https://api.smsmobileapi.com/oauth2/token" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "grant_type=client_credentials" \
-d "client_id=YOUR_CLIENT_ID" \
-d "client_secret=YOUR_CLIENT_SECRET"
Want to run this request? Connect your API key at the top of the page to unlock the interactive tester.
Connect key ↑- Keep the client secret on your server. Never include it in mobile or browser code.
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.
| HTTP | Code | What to do |
|---|---|---|
| 400 | missing_parameter | A required parameter is empty or absent. Check the parameter table for the endpoint. |
| 403 | invalid_apikey | The API key is unknown, expired or not authorized for the requested feature. |
| 429 | too_many_requests | Requests are arriving too quickly. Wait, then retry with exponential backoff. |
| 500 | server_error | The service could not complete the request. Keep the response and contact support if it persists. |
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.


