Every meaningful change.
One clear timeline.

Two new action buttons have been added to each connected mobile device: Send to this mobile and Send from this mobile. These new options make it easier to quickly send an SMS either directly to the selected device or using the selected device as the sender.

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.

The Activity Timeline now also displays SMS messages sent directly from the connected mobile, even when they were not sent through the API. This gives you a more complete view of device activity by combining API-based SMS logs with SMS sent manually from the mobile itself.

Android 4.1.20.0

- Improved Sent SMS Handling
Sent SMS management has been improved for better processing and tracking from the mobile device.

- My Mobile Gateway Overview
You can now view all mobiles connected to your account in My Mobile Gateway, with useful device details.

- Push Notifications to Connected Mobiles
You can now send push notifications to your connected mobiles directly from My Mobile Gateway.

- SMS Rules Management
SMS rules can now be managed directly from the main menu.

- Call Rules Management
Call rules can now be managed directly from the main menu.

- Multi-SIM SMS Sending Fix
Fixed an issue affecting SMS sending on devices using multiple SIM cards, including SIM 1 and SIM 2.

A major new update is now available in the SMSMobileAPI dashboard. You can now create and manage advanced automation rules for missed calls, incoming calls, and outgoing calls directly from your dashboard. Configure automatic SMS replies, custom email notifications, full call information emails, reusable templates, time slots, day-based conditions, contact targeting, duration filters, exclusions, cooldowns, and more. This update turns your connected mobile into an even more powerful communication automation system for business follow-up, team alerts, and smarter call management.

We are happy to announce that version 4.1.16.0 is now available.

What’s new in this version:

It is now possible to set a minimum and maximum sending delay in the settings, so the delay becomes random.

It is now possible to set a minimum and maximum number of SMS to be sent at the same time for each sending batch, so the number becomes random.

The Zapier integration now allows you to manage missed calls, incoming calls, and outgoing calls directly from your mobile device. In addition to sending SMS and retrieving received SMS, you can now use mobile call activity as part of your automated workflows.

You can now access a detailed report for each SMS sent from an SMS campaign. This report includes the delivery status of each message, helping you track sent SMS more precisely and identify possible issues more easily.

In the “Connected Mobiles” management page, you can now choose which SIM card can be used for sending messages by enabling SIM 1 and/or SIM 2 via simple checkboxes (per device).

You can now choose which menu sections are visible or hidden in the dashboard. This helps make the interface lighter and better adapted to each use case, especially when not all menu sections are needed.

The sent SMS listing in the dashboard now shows the SIM port used for each message. It also displays which device was used when multiple phones are connected to the same API key. Error details have been improved for easier troubleshooting, and the log now indicates whether the SMS was sent while the app was running in the foreground or in the background.

- NEW: In foreground mode, SMS can now be sent through the correct SIM port when port 1 or port 2 is available. In background mode, the SMS will be sent through the first available port.
- NEW: It is now possible to see in the dashboard whether the mobile is running in background mode or not.
- NEW: More information is now available for sent SMS when the SMS is sent in foreground mode.
- NEW: If the user has defined a time zone, GMT is no longer displayed next to the time.
- NEW: It is now possible to know whether an SMS was sent in foreground mode or background mode.

- FIX: If the SEND_SMS permission is not granted, a clear alert is now displayed to help the user enable the required permission.
- NEW: If SMS permissions are not granted, an explanatory message is now shown on the page, with additional help.

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.

“Phone Number” Column for Connected Mobiles
Description: The “Connected Mobiles” listing now includes an additional column showing the phone number of each connected mobile.

Send Notifications to Connected Mobiles (v4.1.5.0+)
Description: In the Dashboard, the “Connected Mobiles” listing now lets you send a notification directly to a specific mobile device. This feature works only if the target phone is running the SMSMobileAPI mobile app version 4.1.5.0 or higher.

Description:
The Missed Call Log page has been updated with a clearer layout and improved visibility, making it easier to review missed calls and quickly find important information.

Description:
The Missed Call Log page has been updated with a clearer layout and improved visibility, making it easier to review missed calls and quickly find important information.

The Sent SMS listing in the dashboard now uses your configured Time Area to display dates and times.

This applies to:

Added time (when the SMS was logged/created)

Processing time (when the SMS was handled/sent by the mobile)

Result: the log timeline is now shown in your local date & time, for clearer tracking and reporting.

To make SMS logs easier to understand, the mobile app now displays the sent date & time using your local timezone.

What changed

The SMS sent time shown in the app is now based on your local time (device/account timezone).

We no longer display the server time as the primary reference in the mobile interface.

Why

This avoids confusion when the server timezone differs from yours.

Your sent SMS history is now clearer and matches the time you actually experienced when sending the message.

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"