Every meaningful change.
One clear timeline.

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.

NEW (Important): Bulk SMS Campaigns Page
Description: A new important page is now available to send Bulk SMS campaigns in an easy yet powerful way. You can split the sending workload across multiple connected mobiles to share the delivery flow.
Go to your Dashboard → Bulk SMS Campaign menu to learn more.

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

We’ve published the official documentation for SMSMobileAPI Call Management endpoints.

The new documentation covers the APIs for:

Missed calls

Incoming answered calls

Outgoing calls

It includes endpoint details, authentication, parameters, pagination, filtering, sorting, response formats, and examples to help you integrate call data into your dashboard, CRM, or automation workflows.

Official documentation: https://smsmobileapi.com/doc-call/

We’re happy to introduce a major update to call management in the mobile app.

✅ What’s new

Incoming calls synchronization is now supported

Outgoing calls synchronization is now supported

Synchronized call logs are now available through:

Our API

Our dashboard

📌 Reminder

Missed call management has already been available for several months.

A new complete statistics page is now available for call activity, with dedicated insights for incoming calls, outgoing calls, and missed calls.
It provides a clearer overview of call logs and performance for easier monitoring and analysis.

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.

SMSMobileAPI now lets you retrieve and manage outgoing calls made from your mobile phone. Track call activity in your dashboard and use API access to integrate call logs into your workflows, analytics, or external tools.

You can now retrieve and manage incoming answered calls from your mobile phone directly in SMSMobileAPI. View detailed call logs in your dashboard and access them via API for monitoring, reporting, and integrations.

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"

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

Starting with this update, the dashboard now checks at startup whether your preferred language and timezone are set.
If one of these settings is missing, you’ll be prompted to define it.

This helps ensure a better experience across the service, including more accurate date/time display and a more consistent interface language.

This update lets you send Rich SMS directly from the SMSMobileAPI mobile app.
It helps you save time and makes it faster and easier to send a Rich SMS to a contact—quickly and effortlessly, right from your phone.

The system is now dedicated solely to using this feature, which means:

It’s easier to create a Rich SMS template.

Rich SMS tracking is more complete, for example with the SMS response rate.

For each template, you can check who has replied and who hasn’t replied yet.

When creating a template, you can preview the result at any time.

A new feature is now available in both the dashboard and the API: automatic conversion of all long URLs inside your SMS messages into short, clean Urlz.li links. This improves readability, saves characters, and gives your messages a more professional appearance.
You can enable the feature directly from the dashboard via the new dropdown option, or activate it through the API by adding shorturl=1 to your request.
If you connect your personal Urlz.li API key, all shortened links will also appear in your Urlz.li dashboard with full click-tracking and analytics.

Example:
Before:
Hello, please visit our page: https://smsmobileapi.com/how-to-shopify/#introduction-how-to-use-now-v12

After:
Hello, please visit our page: https://urlz.li/6eabf10b

A new feature is now available: Dynamic Landing Pages for SMS.
This update allows you to enrich every SMS with a personalized web link generated from a template.

You can now create landing page templates with custom content, colors, dynamic variables, and action buttons. When sending an SMS, the API can inject dynamic data into the page, generating a unique landing page instance for each message.

All user interactions on the page (such as button clicks or status updates) are automatically saved in the database and linked to the instance GUID, with buttons becoming locked after selection.

This feature transforms standard SMS into interactive experiences, enabling confirmations, status updates, invoice details, and more — directly accessible through a smart link inside each SM