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.

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/

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

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

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.

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/

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/

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