Changelog
New Feature: Mobile Selector Identifier (sIdentifiant) Update
Endpoint affected: https://api.smsmobileapi.com/sendsms/
Description: Added support for the new parameter sIdentifiant in the sendsms API.
This parameter allows you to specify which connected mobile device should send the SMS, in case multiple devices are linked to the same SMSMobileAPI account (SMS Gateway infrastructure).
If left empty, the system will automatically use the first available device.
Minimum required version: You need app version 3.0.35.3 or higher to access this feature.
Trial SMS Limit Policy – July 30, 2025 Other
Due to repeated abuse by certain users, we have been forced to set a limit on the number of SMS messages that can be sent during the trial period.
A maximum of 60 SMS can now be sent during the free trial (3 days).
Once a user subscribes to a paid plan, this limit is completely lifted.
This change is necessary to ensure fair usage of the platform and to maintain service quality for all users.
Thank you for your understanding and continued support.
Add a fields to API read_sms Update
For the endpoint: https://api.smsmobileapi.com/getsms/, a new field [sIdentifiantPhone] has been added to identify the mobile device that received the SMS.
Learn more : https://smsmobileapi.com/doc/#getsms_endpoint Link copied!
New endpoint pour SMS API - Mark SMS Messages Received as Read New feature
Now you can mark each SMS Messages Received as Read
This API endpoint is used to mark one or multiple received SMS messages as read in the API status only.
This means the read status is updated on the API side, helping you filter out already processed messages when using the onlyunread=yes filter.
Important:
This action does not affect the read status on the smartphone itself — the change applies only to the API status, not to the messaging app or system status on the device.
Endpoint: GET https://api.smsmobileapi.com/getsms/set-read/
Enhancements to SMS Received Endpoint (GET https://api.smsmobileapi.com/getsms/) New feature
Two new optional query parameters have been added to improve SMS retrieval filtering:
after_timestamp_unix (optional):
Provide a UNIX timestamp (in seconds) to retrieve only the SMS received after that specific moment.
This is useful for incremental fetching, allowing clients to sync only new messages since their last request.
Example:
GET https://api.smsmobileapi.com/getsms/?after_timestamp_unix=1715780400
onlyunread (optional):
Set this parameter to yes to retrieve only the SMS messages that have not yet been marked as read via the API.
This helps prevent reprocessing already handled messages.
Example:
GET https://api.smsmobileapi.com/getsms/?onlyunread=yes
Both parameters can be combined to retrieve only new and unread SMS since a specific timestamp.
Example of combined usage:
GET https://api.smsmobileapi.com/getsms/?after_timestamp_unix=1715780400&onlyunread=yes
✅ Infrastructure Upgrade – Thank You for Your Understanding Debug
Dear Customer,
We’re pleased to inform you that we have successfully upgraded our server following a significant increase in traffic on our platform — a clear sign of our growing success thanks to your trust.
This upgrade, driven by our automated systems, was essential to ensure continued stability and performance as demand increases. We sincerely apologize for any inconvenience caused during this process.
Our service continues to evolve with one goal in mind: to provide you with a stable, reliable, and high-performance experience.
Thank you again for your trust and continued support.
The SMS Mobile API Team
New parameter [contactGroup] Update
New parameter [contactGroup] in the WhatsApp sending API, allowing you to specify the GUID of the contact group to use for message delivery.
Link copied!
Instant Response Optimization for SMS and WhatsApp API Update
🚀 Instant Response Optimization for SMS and WhatsApp API
We've optimized our SMS and WhatsApp sending APIs to achieve instantaneous response times, ensuring rapid message delivery and enhanced user experience. Users will now benefit from significantly faster interactions, enabling real-time communication without delays.
New parameter added for SMS encryption at recipient side New feature
GET / POST : encrypt_message (value = yes)
A new optional parameter has been added to the encrypt_message function to enable message encryption upon reading by the recipient.
This feature enhances end-to-end security by ensuring that messages are not only encrypted in our database, but also remain encrypted on the recipient's phone until the correct decryption key is entered.
Endpoint Updated: https://api.smsmobileapi.com/getwa Update
You can now filter the type of WhatsApp messages retrieved using the message_type parameter.
Accepted values:
Leave empty → Returns all messages (text + audio converted to text)
text → Returns only text messages
audio → Returns only audio messages (converted to text)
Example : GET https://api.smsmobileapi.com/getwa?apikey=YOUR_API_KEY&message_type=audio
Release of the endpoint to resend a WhatsApp message with a status via API request New feature
Now, through the endpoint: https://api.smsmobileapi.com/resendwa/,
it is possible to programmatically resend a failed WhatsApp message.
See the documentation for more details: https://smsmobileapi.com/doc-whatsapp/
API endpoint release: https://api.smsmobileapi.com/email/unsubscribed/ New feature
We have published a new API endpoint that allows you to list all contacts who have received an email from you and clicked the unsubscribe link after receiving your marketing email:
👉 https://api.smsmobileapi.com/email/unsubscribed/
New Endpoint Available for WhatsApp Message Retrieval Update
A new API endpoint is now available to request synchronization with WhatsApp before retrieving messages.
This step is mandatory to ensure message retrieval works properly.
🔗 New Endpoint: https://api.smsmobileapi.com/getwa/synchronisation/
📖 Learn more: https://smsmobileapi.com/doc-whatsapp/
New API Structure for Retrieving WhatsApp Messages Now Available Update
{
"date": "2025-03-11",
"hour": "12:27:00",
"timestamp": "1741692420",
"number": "19176728660",
"contact": "Smsmobileapi",
"message": "Can you tell me when I will receive my order?",
"guid": "652fcfc0-12a8-46f5-b5ba-9391135b8b4c",
"more": {
"auto_reply": "1",
"transfert_to_email": "1",
"chatgpt_reply": "1"
},
"chatgpt": {
"prompt_tokens": "900",
"completion_tokens": "10",
"total_tokens": "910",
"total_tokens_cost": "0.182"
"response": "Your order #576 will be shipped tomorrow."
}
}
Resend an unsent SMS via API New feature
It is now possible to initiate a new attempt to resend an unsent SMS via the /resend endpoint.
Check the documentation for more details : https://smsmobileapi.com/doc/
Example :
https://api.smsmobileapi.com/resend/?apikey=YOUR_API_KEY
English 
French 
German 
Spanish 
Portuguese 
Russian 
Finnish 
Japanese 
Chinese 
Vietnamese 
Dutch 
Greek 
Arabic 
Danish 
Italian 
Ukrainian