每一次有意义的改变。
明确的时间线

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
电话打不通
来电
正在通话
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.

现在可以使用新的端点：https://api.smsmobileapi.com/log/sent/frommobile/
It allows you to list SMS messages sent from the mobile device and synchronized to SMSMobileAPI.
该端点支持日期、时间段、电话号码、手机标识符、消息内容、排序和限制等筛选条件。
此功能从 Android 版本 4.1.20 开始可用，默认情况下未启用，并且仅返回最近 7 天的数据。
所有同步数据均已匿名化并保密。
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.

我们已发布 SMSMobileAPI 呼叫管理端点的官方文档。

新文档涵盖了以下 API：

电话打不通

Incoming answered calls

正在通话

它包含端点详细信息、身份验证、参数、分页、筛选、排序、响应格式和示例，可帮助您将呼叫数据集成到您的仪表板、CRM 或自动化工作流程中。

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

全新 API 上线！
您现在可以使用新的端点直接从手机列出未接来电：
https://api.smsmobileapi.com/missedcall/list/

此 API 允许您：
- 通过 `apikey` 检索未接来电
- 按号码或名称搜索
- 按日期范围（天或期间）过滤
- 使用 `offset` 和 `limit` 对结果进行分页

立即开始集成并自动化处理未接来电的方式！

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.
这意味着读取状态在 API 端更新，帮助您在使用 onlyunread=yes 过滤器时过滤掉已处理的消息。

重要的：
此操作不会影响智能手机本身的读取状态——此更改仅适用于 API 状态，而不适用于设备上的消息应用程序或系统状态。

端点：GEThttps://api.smsmobileapi.com/getsms/set-read/

Two new optional query parameters have been added to improve SMS retrieval filtering:

after_timestamp_unix （可选）：
Provide a UNIX timestamp (in seconds) to retrieve only the SMS received after that specific moment.
这对于增量提取很有用，允许客户端仅同步自上次请求以来的新消息。

例子：
得到https://api.smsmobileapi.com/getsms/?after_timestamp_unix=1715780400

onlyunread（可选）：
Set this parameter to yes to retrieve only the SMS messages that have not yet been marked as read via the API.
这有助于防止重新处理已经处理过的消息。

例子：
得到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:
得到https://api.smsmobileapi.com/getsms/?after_timestamp_unix=1715780400&onlyunread=yes

GET / POST：encrypt_message（值=是）
encrypt_message 函数中添加了一个新的可选参数，以便在收件人阅读时启用消息加密。
此功能可确保消息不仅在我们的数据库中加密，而且在收件人的手机上保持加密，直到输入正确的解密密钥，从而增强端到端的安全性。

现在，通过端点：https://api.smsmobileapi.com/resendwa/,
可以通过编程重新发送失败的 WhatsApp 消息。
请参阅文档以了解更多详细信息：https://smsmobileapi.com/doc-whatsapp/

我们发布了一个新的 API 端点，允许您列出所有收到您的电子邮件并在收到您的营销电子邮件后单击取消订阅链接的联系人：
ðŸ'‰https://api.smsmobileapi.com/email/unsubscribed/

It is now possible to initiate a new attempt to resend an unsent SMS via the /resend endpoint.
查看文档了解更多详细信息：https://smsmobileapi.com/doc/

例子 ：
https://api.smsmobileapi.com/resend/?apikey=YOUR_API_KEY