Every meaningful change.
One clear timeline.

The new SMSMobileAPI integration for Odoo 17 is now officially available on Odoo Apps.

Connect Odoo to your own Android mobile, SIM card and phone number. Your team can now:

- Send SMS directly from Odoo contacts, invoices, quotations, sales orders and payment reminders.
- Synchronize received SMS with the matching Odoo contact.
- Keep missed, incoming and outgoing call activity in the customer timeline.
- Work from a shared SMS inbox with assignments, priorities, internal notes and archives.
- Turn an SMS or missed call into an opportunity, task, callback, quotation or support ticket.

Install the official Odoo 17 application:
https://apps.odoo.com/apps/modules/17.0/sms_mobile_api_call

Discover the complete integration:
https://smsmobileapi.com/odoo/

An SMSMobileAPI account and the official Android mobile application are required. SMS messages are sent through your connected mobile, using its SIM card and phone number.

We've enhanced your account security!

You can now enable **Two-Factor Authentication (2FA) with Google Authenticator** directly from the **Security Center** in your dashboard.

✅ Add an extra layer of protection to your account.
✅ Secure your login with a one-time verification code.
✅ Easily enable or disable 2FA from your Security Center.

**Your account security is our priority!** 🔒

We're updating our services to provide a more focused and powerful experience!

**Email-related features are no longer supported by SMSMobileAPI.** These functionalities are now handled by **MailBridgeAPI**, our dedicated platform for email management, optimization, and automation.

**🚀 Why MailBridgeAPI?**

MailBridgeAPI is specifically designed to help you:
- 📥 **Manage** your email accounts more efficiently.
- ⚡ **Optimize** email workflows and productivity.
- 🤖 **Automate** email tasks and responses.
- 🔗 **Integrate** email management into your existing tools and workflows.

**What does this mean for SMSMobileAPI?**

SMSMobileAPI will continue focusing on its core features, including SMS, WhatsApp, and mobile call management.

**👉 Discover MailBridgeAPI:** https://mailbridgeapi.com

You can now connect your Pipedrive account to SMSMobileAPI and manage your mobile communications directly from your CRM.

**What's available?**
- 📱 **Send SMS** directly from Pipedrive using your own mobile phone.
- 💬 **Receive SMS** and sync incoming messages with Pipedrive.
- 📞 **Incoming calls** – Automatically sync call logs.
- 📤 **Outgoing calls** – Keep track of your call history.
- 📵 **Missed calls** – Never lose track of missed calls in your CRM.

No external SMS provider required — use your own mobile phone and SIM card!

**🔗 Connect your Pipedrive account today:**

https://www.pipedrive.com/en/marketplace/app/sms-mobile-api-sms-call-sync/4e9ad621820007e9

Version 6.0.4.0 significantly improves SMSMobileAPI’s Confidential Mode, making it easier to use and providing greater control.
- Clearer and better-organized settings.
- Simplified contact and group management.
- Add contacts using a Public GUID or QR code.
- New invitation system with accept and decline options.
- Stronger access protection with biometric authentication.
- More detailed connection activity logs.
- Subscription management directly from the app.
- Visible alert 48 hours before subscription expiration.
- Access protection when the subscription expires.
- Improved stability, controls, and translations.
This update delivers a more professional and intuitive Confidential Mode experience while keeping privacy at the center of every interaction.

### Create your own automation workflows directly in SMSMobileAPI

A major new feature is now available: **Workflow Studio**.

You can now visually create automations based on events coming from your mobile devices and communication channels, without writing any code.

The logic is simple:

**WHEN → IF → THEN**

For example:

- When an SMS containing “INFO” is received → automatically send a reply.
- When a call is missed → send an SMS or a notification.
- When a WhatsApp message contains “urgent” → notify a team member.
- When an SMS or WhatsApp message fails to send → automatically send an email.
- When a specific event occurs → send the information to your own application through a webhook.

Workflow Studio currently supports **15 events**, **11 condition types**, and **5 action types**, covering SMS, calls, WhatsApp, email, notifications, and webhooks.

You can also **simulate and test your workflows before activating them**, without actually sending messages, emails, notifications, or webhook requests.

Workflow Studio turns SMSMobileAPI into a complete automation platform connected directly to your mobile devices.

We are introducing **Webhook V2**, a major evolution of the SMSMobileAPI webhook system.

Until now, webhooks were mainly focused on incoming SMS messages. With Webhook V2, SMSMobileAPI becomes a complete **event-driven mobile communication platform**, allowing your applications to react automatically to SMS, calls, WhatsApp messages, voice transcriptions, and email activity.

Instead of repeatedly polling the API to check whether something has changed, your application can now receive structured HTTPS events automatically, as soon as supported activity occurs.

### 15 webhook event types

Webhook V2 introduces precise event names covering the main communication channels available through SMSMobileAPI.

**SMS**

* `sms.api.submitted` — An SMS sending request was submitted through the API.
* `sms.sent` — The connected mobile confirmed that the SMS was sent.
* `sms.failed` — An SMS sending operation failed.
* `sms.received` — A new incoming SMS was synchronized.
* `sms.mobile.sent` — An SMS was sent manually from the connected mobile.

**Calls**

* `call.missed` — A missed call was detected.
* `call.incoming` — An incoming call was synchronized.
* `call.outgoing` — An outgoing call was synchronized.

**WhatsApp**

* `whatsapp.submitted` — A WhatsApp sending job was created.
* `whatsapp.sent` — A WhatsApp message was successfully sent.
* `whatsapp.failed` — A WhatsApp sending operation failed.
* `whatsapp.received` — A new WhatsApp message was retrieved.
* `whatsapp.voice.transcribed` — A WhatsApp voice message was converted into text.

**Email**

* `email.sent` — An email sending request was created.
* `email.received` — A connected mailbox received a new email.

### Multiple webhook destinations

You are no longer limited to a single webhook endpoint.

Webhook V2 allows you to create **multiple independent destinations** and decide exactly which events each destination should receive.

For example, you can send:

* Incoming SMS and WhatsApp messages to your CRM.
* Missed calls to your customer support system.
* Failed SMS and WhatsApp deliveries to your monitoring platform.
* Communication events to your analytics system.
* Selected events to your own automation or AI workflow.

Each destination operates independently.

### Selective event routing

Every webhook destination can subscribe only to the events it needs.

This makes integrations cleaner and prevents your application from receiving unnecessary events.

A CRM could subscribe only to:

`sms.received`
`call.missed`
`whatsapp.received`

while an operational monitoring system could subscribe only to:

`sms.failed`
`whatsapp.failed`

### Reliable asynchronous delivery

Webhook V2 uses a **durable delivery queue**.

Events are stored before delivery and processed asynchronously, meaning your SMSMobileAPI workflow does not need to wait for a third-party server to respond.

If one destination becomes slow or unavailable, it does not block other destinations or other accounts.

### Automatic retries

Temporary endpoint failures are automatically retried using progressive delays.

Webhook V2 uses **at-least-once delivery**, so an event may occasionally be delivered more than once.

Each event therefore includes a stable event identifier that your application can store and use as an idempotency key to prevent duplicate processing.

### Signed and verifiable webhook requests

Security is an important part of Webhook V2.

Each webhook request includes information allowing your server to verify that the request genuinely originated from SMSMobileAPI.

Requests include:

* Event type
* Delivery ide

The SMSMobileAPI Dashboard menu has been reorganized to make navigation simpler and more intuitive.

SMS and WhatsApp features are now grouped more logically, making it easier to find the tools you need and manage your messages, settings and related features from the Dashboard.

The new version of the SMSMobileAPI Dashboard now includes the complete menu and all available options for managing rules related to received SMS messages.

You can now create, configure and manage your incoming SMS rules directly from the updated Dashboard interface.

Bulk Manager Pro has been updated with additional options and several improvements to overall stability.

These changes make it easier to manage large messaging campaigns while providing a smoother and more reliable experience when processing bulk SMS operations.

We have updated the WhatsApp receiving system to provide better overall stability, regardless of your geographic location.

Incoming WhatsApp messages can continue to be retrieved through both the SMSMobileAPI Dashboard and API, with improved reliability and more consistent synchronization across different regions.

The new SMSMobileAPI iOS app version 6.0.0 is now available.

This major release brings the latest improvements to the SMSMobileAPI mobile experience on iPhone, with enhanced stability, performance, and compatibility.

Update to version 6.0.0 now to enjoy the latest SMSMobileAPI features and improvements on iOS.

App Version 6.0.1
### Service Reliability & Android 16 Improvements

This update focuses on improving the stability, reliability, and performance of SMSMobileAPI on Android devices.

* **New Service Diagnostics Center** to quickly check the status of SMS, calls, background services, permissions, and device connectivity.
* **Faster and more reliable SMS processing via API**, reducing delays when sending messages from your applications and integrations.
* **Improved background synchronization** for sent and received SMS, incoming calls, outgoing calls, and missed calls.
* **Better automatic error recovery** to help SMSMobileAPI continue operating correctly after temporary network, Android service, or connection issues.
* **Improved background service stability** for devices running SMSMobileAPI continuously.
* **Enhanced Android 16 compatibility**, including improvements for newer Android background execution and permission requirements.
* General performance, stability, and reliability improvements.

You can now connect your Pipedrive account to SMSMobileAPI and manage SMS communication directly from your Pipedrive contacts.

Once connected, SMSMobileAPI automatically links your mobile phone with Pipedrive.

With this integration, you can:

Send SMS messages from your mobile phone directly from a contact in Pipedrive.
Receive SMS messages on your mobile phone and automatically see them inside the corresponding Pipedrive contact.
Keep your SMS conversations linked to each individual contact, making it easier to follow your customer communication.
Use your existing mobile SIM card and phone number to send and receive SMS messages.

Everything is centralized inside Pipedrive, so you can see the SMS history for each contact without having to switch between different tools.

Simply connect your Pipedrive account from the SMSMobileAPI dashboard to get started.

A simple way to bring your mobile SMS communication directly into your Pipedrive CRM.

Version 2 of our GoHighLevel (GHL) integration is now live! Following extensive development and debugging efforts, our team has fully stabilized communication between GoHighLevel, SMSMobileAPI, and your mobile phone.

Try sending or receiving SMS messages directly from your GHL account to experience the improvements today.

We sincerely apologize for the inconvenience caused by the recent issues. Thank you for your patience and understanding while our team worked to resolve them.

You can now permanently delete all activity logs associated with your SMSMobileAPI account.

The following log categories can now be fully removed:

* SMS sent via API
* SMS sent from your mobile device
* Received SMS
* Missed calls
* Incoming calls
* Outgoing calls
* Call rule executions
* Sent WhatsApp messages
* Received WhatsApp messages
* Sent emails
* Mobile notifications

This update gives you greater control over your account data and makes it easier to manage or completely clear your activity history whenever needed.

You can now sign in to your dashboard using your email address and password.
You no longer need to enter your Account ID and Account Licence, making access faster, easier, and more convenient.

ur entire website and dashboard have received a major update, featuring a modernized design, improved functionality, and a more intuitive user experience.

Because our users always deserve the very best.

SMSMobileAPI Mobile App V6 is Now Available

After several months of development, the new SMSMobileAPI Mobile App V6 is now officially available for download.

This major update brings a completely rebuilt app with improved stability, performance, background operation, and a more reliable SMS management experience.

We strongly recommend updating to V6 to benefit from all the latest improvements.

You can now discover how to send notifications directly to your mobiles through simple API requests. This new documentation helps users quickly understand and integrate mobile notification sending into their own applications, workflows, or automation tools.£
Here : https://smsmobileapi.com/doc-notification/