Your SMS are sent from your own mobile.See how it works
PLATFORMAPI-first architectureSecure device pairingDelivery visibilityMulti-device controlVersioned documentation
SMSMobileAPI / Platform updates

Product evolution, documented

Every meaningful change.
One clear timeline.

Follow new capabilities, platform improvements and fixes across the API, dashboard, mobile apps and integrations.

SMSMobileAPI platform releases across APIs, mobile apps and integrations
Live changelog source
189public releases
29product areas
4change types
September 16, 2026latest recorded release

Release history

11 updates

Newest first
2026

New endpoint to update the alias of a received SMS

A new API endpoint is now available: https://api.smsmobileapi.com/getsms/update/
It allows you to update the alias field of a received SMS using its guid.
The apikey and guid parameters are required. The alias parameter can also be sent empty to clear the current alias value.
Learn more
#188

3 new Gateway API endpoints for connected mobiles

New Gateway API Endpoints for Connected Mobiles
Description: Three new endpoints are now available in the doc-gateway documentation to list, delete, and update your connected mobiles.
Learn more
#174

Improved — Sent SMS Logs API: Local time + server time now included

We updated the response format of the Sent SMS Logs API to make timestamps clearer and easier to use across timezones.

Endpoint: https://api.smsmobileapi.com/log/sent/sms/?

What’s new

Local timestamp added: the API now returns the date & time in your local timezone (based on your account/device timezone).

Server timestamp preserved: the API still includes the original server date & time for traceability and debugging.

This makes it easier to display logs correctly in dashboards and exports, while keeping a reliable reference to server time.

New field :

timearea "UTC+01"
date_add_server "2026-02-20"
hour_add_server "17:38:31"
timestamp_server 1771609111
send_from_mobile_date_server "2026-02-20"
send_from_mobile_heure_server "17:38:38"

send_from_mobile_timestamp 1771612718

Example of full reply :

date_add "2026-02-20"
hour_add "18:38:31"
timestamp 1771612711
send_from_mobile 1
send_from_mobile_date "2026-02-20"
send_from_mobile_heure "18:38:38"
send_from_mobile_timestamp 1771612718
recipients "1234567891011"
sms "test"
error_api ""
send_from_mobile_erreur ""
guid_message "e24143a6d096f9830430b5bc05ff0e42bfe89321"
timearea "UTC+01"
date_add_server "2026-02-20"
hour_add_server "17:38:31"
timestamp_server 1771609111
send_from_mobile_date_server "2026-02-20"
send_from_mobile_heure_server "17:38:38"
Learn more
#160

Local Send Time Support (Timezone-Aware) + New datetimeLocal Field

If your timezone is set, SMS and WhatsApp sending is now timezone-aware:

The system calculates the local date & time of the message at the moment it is sent.

This local timestamp is returned in the API response for easier tracking and logging.

✅ New JSON field added:
["result"]["datetimeLocal"] → returns the local send date & time (based on the configured timezone).
Learn more
#159
2025

New Feature: Mobile Selector Identifier (sIdentifiant)

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.
Learn more
#138

Add a fields to API read_sms

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
#130

New parameter [contactGroup]

New parameter [contactGroup] in the WhatsApp sending API, allowing you to specify the GUID of the contact group to use for message delivery.
#71

Instant Response Optimization for SMS and WhatsApp API

🚀 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.

#58

Endpoint Updated: https://api.smsmobileapi.com/getwa

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
#49

New Endpoint Available for WhatsApp Message Retrieval

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/
#36

New API Structure for Retrieving WhatsApp Messages Now Available

{
"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."
}
}
#35