Every meaningful change.
One clear timeline.

New API endpoints are now available to permanently delete SMSMobileAPI activity logs directly through API requests.

You can now programmatically clear the following history categories:

SMS sent via API
SMS sent from the mobile device
Received SMS
Missed calls
Incoming calls
Outgoing calls
Call rule execution history
Sent WhatsApp messages
Received WhatsApp messages
Sent emails
Mobile notifications

Dedicated deletion endpoints are now available for each log category:

/delete-history-sms-api/
/delete-history-sms-mobile/
/delete-history-sms-received/
/delete-history-calls-missed/
/delete-history-calls-incoming/
/delete-history-calls-outgoing/
/delete-history-call-rules/
/delete-history-whatsapp-sent/
/delete-history-whatsapp-received/
/delete-history-email/
/delete-history-notifications/

These new endpoints make it easier to automate log management, integrate cleanup operations into your own applications, and maintain better control over your SMSMobileAPI account data.

Note: Deleting the call rule execution history only removes the execution logs. Your configured call rules are not deleted.

We added a powerful new endpoint, /conversation/sms/list/, to make SMS conversation retrieval easier and more structured. You can now list conversations by phone number, view both incoming and outgoing messages in one timeline, filter results by number or date, and use resume mode for quick conversation previews. The endpoint also supports both received and sent as conversation starting points and automatically adjusts outgoing message dates based on the message time zone when available.

A new endpoint is now available: https://api.smsmobileapi.com/log/sent/frommobile/
It allows you to list SMS messages sent from the mobile device and synchronized to SMSMobileAPI.
The endpoint supports filters such as date, period, phone number, mobile identifier, message content, sorting, and limit.
This feature is available starting from Android version 4.1.20, is not enabled by default, and returns data from the last 7 days only.
All synchronized data is anonymized and confidential.
SMS sent through the standard https://api.smsmobileapi.com/sendsms/ endpoint may also appear in this log because they are sent from the mobile device.

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.

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.

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

🚀 New API available!
You can now list missed calls directly from your mobile using the new endpoint:
https://api.smsmobileapi.com/missedcall/list/

This API allows you to:
- Retrieve missed calls by `apikey`
- Search by number or name
- Filter by date range (day or period)
- Paginate results with `offset` and `limit`

Start integrating today and automate how you handle missed calls!

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.

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.

For the endpoint: https://api.smsmobileapi.com/getsms/, a new field [sIdentifiantPhone] has been added to identify the mobile device that received the SMS.

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/

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

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] in the WhatsApp sending API, allowing you to specify the GUID of the contact group to use for message delivery.

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

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.

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

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/