Hver eneste meningsfuld forandring.
En klar tidslinje.

Telegram sending is now available in SMSMobileAPI. Connect your own Telegram account by scanning a QR code in the dashboard, synchronize your contacts, and send your first message without writing code.

Developers can now use three REST endpoints to list Telegram contacts, queue a text message, and check its sending status. The API uses your account-specific key, and an optional idempotency key helps avoid duplicate messages when retrying a request.

Start from the dashboard or follow the step-by-step guide at https://smsmobileapi.com/telegram/. The complete endpoint reference is at https://smsmobileapi.com/doc-telegram/. A queued request is not a delivery receipt; the sent log shows whether Telegram accepted the message or an error occurred.

Photos received in a connected WhatsApp conversation can now be recovered after you request WhatsApp synchronization. Open the received messages page in your SMSMobileAPI dashboard and select View image beside a photo.

The GET https://api.smsmobileapi.com/getwa/ endpoint identifies photos with message_type=image and is_photo=true. Each available photo includes its MIME type, size, and private download and base64 endpoints. Image bytes are returned only when you request that photo, keeping the message list fast. Your account API key or OAuth token is required to access it.

Explore the API: https://smsmobileapi.com/doc-whatsapp/#get-whatsapp
View received messages: https://dashboard.smsmobileapi.com/whatsapp-retrieve-statistics/

You can now save the dashboard pages you use most. Select the star beside a page title to add it to My Favorites at the top of the navigation menu. Select the star again to remove it.

Your favorites are saved to your SMSMobileAPI account, so the same shortcuts are available across your devices. A favorite remains easy to reach even when its original menu section is hidden in your menu preferences.

Bulk WhatsApp Campaigns is now available in the SMSMobileAPI dashboard. Create a WhatsApp campaign, choose contact groups whose members agreed to receive your messages, and select one or more connected WhatsApp accounts. Prepare and review the recipient queue before you press Start. Preparation alone does not send messages.

Follow each batch and inspect pending requests, messages accepted by the WhatsApp API, and items that need review. API acceptance is not proof of delivery to the recipient. You can stop work still in the queue; uncertain requests are not automatically resent.

Explore the feature: https://smsmobileapi.com/bulk-whatsapp-campaigns/
Open the dashboard: https://dashboard.smsmobileapi.com/bulkpro-whatsapp-campaigns/

Your SMSMobileAPI dashboard can now manage multiple WhatsApp accounts. Keep your existing WhatsApp connection and add as many additional accounts as you need for sales, support, brands, regions or client projects. There is no fixed dashboard limit on additional connections.

Each additional account has its own named connection, separate subscription and unique private API key. Choose a connection in the dashboard, or use its API key in your WhatsApp API requests to select the sender without mixing accounts.

To get started, add a connection in the dashboard, complete activation, scan its WhatsApp QR code and enable sending. The new account is ready to use once its WhatsApp connection is active.

Explore the setup and use cases: https://smsmobileapi.com/whatsapp-multi-accounts/

AI SMS replies can now use information from your own connected APIs. Give ChatGPT or Claude access to the approved data it needs to answer questions about prices, availability, order status or other information from your business systems.

Create an API connection in the SMSMobileAPI dashboard, configure and test its endpoints, then attach it to one or more AI reply modes. For each connection, explain when the AI should call it and what the returned information is for. Only modes and connected mobiles you authorize can use that integration.

Replies can be sent automatically from your own mobile or held for human approval. If you need help creating a connection, use the integration help form in the dashboard.

Explore AI SMS Auto-Reply: https://smsmobileapi.com/ai-sms-auto-reply/

Human approval for AI-generated SMS replies is coming directly to the SMSMobileAPI Android app. When a reply mode requires approval, you can review the incoming SMS and the proposed answer on your phone before anything is sent.

What the new Android approval inbox lets you do:

- Open a notification directly on the reply that needs your decision.
- Read the incoming SMS, edit the proposed answer, then approve and send it from your connected mobile and its own SIM and phone number.
- Refuse a reply with a reason that helps improve future suggestions for your account, or archive it without sending.
- Apply one decision to all pending replies when you need to clear the queue quickly.
- See a saved contact name above the number when you optionally allow local contact lookup. Contact names are not sent to the server.
- Choose whether approval notifications are shown and whether the approval inbox opens first when you launch the app.
- See new pending replies appear automatically while the inbox is open, with a visible highlight, without losing edits already made to other drafts.

In human-approval mode, a suggested reply is not sent until you approve it. The mobile must stay connected and incoming-SMS synchronization must be enabled.

Rollout status: this feature is ready in the signed Android 6.1.0.12 build. It has not yet been published on Google Play; the current store version does not include this mobile approval inbox.

Learn how AI SMS replies work: https://smsmobileapi.com/ai-sms-auto-reply/

Claude by Anthropic can now power SMSMobileAPI's automatic replies to incoming SMS. Your replies are sent from your own connected Android mobile and phone number.

Create a named AI reply mode, add your own Anthropic API key, choose a supported Claude model, and define the instructions, schedule, signature and numbers to exclude. Assign the mode to the mobile that should use it. Each contact keeps a separate conversation history for that mobile and reply mode.

Choose automatic sending or human approval. The approval queue, reply logs and credit tracking work with Claude as they do with ChatGPT. You can assign different AI providers to different mobiles through separate reply modes.

To receive and answer messages, incoming-SMS synchronization must be enabled in the SMSMobileAPI mobile app, and the phone must remain connected.

Explore the Claude integration: https://smsmobileapi.com/claude/
Compare both providers: https://smsmobileapi.com/ai-sms-auto-reply/

AutoReply AI is now available to every SMSMobileAPI account, making it possible to answer incoming SMS with contextual ChatGPT-powered replies sent through your own connected Android mobile, SIM and phone number.

What is new:

- Create multiple named AI reply modes with their own instructions, tone, selected AI model, schedule and optional SMS signature.
- Assign a different reply mode to each connected mobile, identified by its name and device reference.
- Let replies be sent automatically or require human approval before sending.
- Approve, archive or refuse suggested replies, and add a private refusal reason to improve future replies for the account.
- Keep an isolated conversation memory for each contact number, connected mobile and assigned reply mode.
- Choose the days and hours when automatic replies are allowed, or keep them active at all times.
- Exclude named phone numbers, service senders and short numbers that must never receive an automatic reply.
- Confirm that incoming-SMS synchronization is enabled on the connected Android mobile before activating the automation.
- Use the SMSMobileAPI-managed AI connection or a supported personal provider key.
- Review replies, decisions, delivery status, token usage and customer-visible charges in dedicated logs.
- Control the service globally and separately for every connected mobile.

The base platform charge is $0.005 for each generated reply. The connected Android mobile must remain online, and incoming-SMS synchronization must be enabled in the SMSMobileAPI app.

Discover AutoReply AI:
https://smsmobileapi.com/chatgpt/

The official SMSMobileAPI OpenAPI specification is now publicly available.

Developers can use this machine-readable definition to explore the API, understand request and response formats, import endpoints into compatible API tools, and generate client code more quickly.

Key resources:

- Developer documentation and OpenAPI access:
https://smsmobileapi.com/documentations-api-smsmobileapi/#openapi
- Canonical OpenAPI YAML file:
https://smsmobileapi.com/assets/openapi/smsmobileapi-openapi.yaml
- Public GitHub repository:
https://github.com/SmsMobileApi/smsmobileapi-openapi
- Public Postman workspace:
https://www.postman.com/mailbridgeapi/smsmobileapi/overview
- RapidAPI listing:
https://rapidapi.com/sellviaapp/api/smsmobileapi1

The public specification contains safe placeholders only. Use your own SMSMobileAPI account API key when authenticating requests, and never publish a real credential in a public workspace or repository.

You can now control access to each SMS API endpoint individually from Dashboard > My API Key. Keep only the operations you need enabled, or pause all SMS API access instantly, for even stronger account security.

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.

The new Workflow Studio API is now available.
Developers can securely manage and monitor their Workflow Studio automations from their own applications, services and integrations.
Available endpoints:
- GET /workflow/list/ — List all workflows associated with the authenticated account.
- POST /workflow/state/ — Activate or pause a workflow.
- POST /workflow/favorite/ — Add or remove a workflow from mobile favorites.
- GET /workflow/logs/ — Retrieve the execution history and action results for a workflow.
Each workflow is identified through its secure public workflow_uuid. Internal database identifiers are never exposed.
Authentication is available through the account API key or an Authorization: Bearer header. Every request is restricted to workflows belonging to the authenticated account.
State and favorite changes are synchronized with the SMSMobileAPI dashboard and mobile application.
Complete documentation, request examples and JSON responses are available here:

Version 6.0.2 introduces Workflow Studio directly within the SMSMobileAPI mobile app.
You can now:
- Access your workflows without leaving the app.
- Create, edit, and delete automations.
- Quickly activate or deactivate a workflow.
- Review recent executions and their status.
- Add workflows to your favorites for quick access when opening the app.
- Automate actions based on SMS, calls, WhatsApp messages, and other supported events.
For example, you can automatically send an SMS after a missed call, detect a keyword in a received message, or trigger an action only during a specific time period.
Favorite workflows also let you create your own modes—such as Driving, Work, Family, or On-call—and activate them with a single tap from your phone.
This update makes your automations more accessible and allows you to manage your business communications directly from the SMSMobileAPI app.


21:30

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

Vi introducerer * * Webhook V2 * *, en større udvikling af SMSMobileAPI webhook-systemet.

Indtil nu var webkroge primært fokuseret på indgående SMS beskeder. Med Webhook V2 bliver SMSMobileAPI en komplet * * eventdrevet mobil kommunikationsplatform * *, så dine programmer kan reagere automatisk på SMS, opkald, WhatsApp-beskeder, stemmetransskriptioner og e-mail-aktivitet.

I stedet for gentagne gange at vælge API for at kontrollere, om noget har ændret sig, kan din ansøgning nu modtage strukturerede HTTPS begivenheder automatisk, så snart understøttede aktivitet opstår.

### 15 webhook-begivenhedstyper

Webhook V2 introducerer præcise begivenhedsnavne, der dækker de vigtigste kommunikationskanaler, der er tilgængelige via SMSMobileAPI.

**SMS * *

* `sms.api.submitted '- An SMS sending request was submitted through API.
* `sms.sendt '- Den tilsluttede mobil bekræftede, at SMS blev sendt.
* `sms.failed '- En SMS sende operation mislykkedes.
* `sms.received '- En ny indkommende SMS blev synkroniseret.
* `sms.mobile.sendt '- En SMS blev sendt manuelt fra den tilsluttede mobil.

**Opkald * *

* `Call. 'misset' - Et misset opkald blev opdaget.
* `Et opkald blev synkroniseret.
* `Udgående "- Et udgående opkald blev synkroniseret.

**WhatsApp * *

* `whatsapp.submitted '- En WhatsApp sende job blev oprettet.
* `whatsapp.sent '- En WhatsApp besked blev sendt med succes.
* `whatsapp.failed '- En WhatsApp sende operation mislykkedes.
* `whatsapp.received '- En ny WhatsApp besked blev hentet.
* `whatsapp.voice.transskriberet '- En WhatsApp stemme besked blev konverteret til tekst.

**E-mail * *

* `email.sent '- En e-mail-afsenderanmodning blev oprettet.
* `email.received '- En tilsluttet postkasse modtog en ny e-mail.

### Flere webhook destinationer

Du er ikke længere begrænset til et enkelt webhook endpoint.

Webhook V2 giver dig mulighed for at oprette * * flere uafhængige destinationer * * og beslutte præcist, hvilke begivenheder hver destination skal modtage.

For eksempel kan du sende:

* Indkommende SMS og WhatsApp beskeder til din CRM.
* Mistede opkald til dit kundesupport system.
* Kunne ikke levere SMS og WhatsApp til din overvågningsplatform.
* Kommunikationsbegivenheder til dit analytics-system.
* Udvalgte begivenheder til din egen automatisering eller AI arbejdsgang.

Hver destination fungerer uafhængigt.

### Selektiv begivenhedsrouting

Hver webhook destination kan kun abonnere på de begivenheder, den har brug for.

Dette gør integrationerne renere og forhindrer din ansøgning fra at modtage unødvendige begivenheder.

En CRM kunne kun abonnere på:

`sms.received "
`Call.Missed "
`Hvad var det, der blev modtaget?

mens et operationelt overvågningssystem kun kunne tegne abonnement på:

`sms.failed "
`Hvad er det, der mangler?

### Pålidelig asynkron levering

Webhook V2 bruger en * * holdbar leveringskø * *.

Begivenheder gemmes før levering og behandles asynkront, hvilket betyder, at din SMSMobileAPI workflow behøver ikke at vente på en tredjeparts server til at reagere.

Hvis en destination bliver langsom eller ikke tilgængelig, blokerer den ikke andre destinationer eller andre konti.

### Automatisk relæer

Midlertidige endpoint fejl bliver automatisk genafprøvet ved hjælp af progressive forsinkelser.

Webhook V2 bruger * * mindst én gang levering * *, så en begivenhed kan lejlighedsvis blive leveret mere end én gang.

Hver begivenhed indeholder derfor en stabil begivenhed id, som dit program kan gemme og bruge som en idempotens nøgle til at forhindre dobbeltbehandling.

### Underskrevne og kontrollerbare webhook-forespørgsler

Sikkerhed er en vigtig del af Webhook V2.

Hver webhook anmodning indeholder oplysninger, der gør det muligt for din server at kontrollere, at anmodningen virkelig stammer fra SMSMobileAPI.

Anmodninger omfatter:

* Begivenhedstype
* Leveringsid