Many users and businesses have questions about how to simultaneously connect multiple linked devices to a single WhatsApp account. Is it possible to simultaneously connect multiple API instances, WhatsApp Web, and the desktop app? Will this lead to conflicts or data loss? In this article, we’ll explore how linked devices work technically, what scenarios are officially supported, and where issues might arise.
Table of Contents
How WhatsApp’s linked devices work
WhatsApp allows you to connect up to four additional devices (computers, tablets) to a single account without having to keep your phone online. These devices sync independently: each receives its own copy of messages, and notifications are delivered to all active devices simultaneously.
Architecturally, each linked device acts as a separate client, establishing its own encrypted connection and independently processing incoming messages. The primary phone remains the “owner” of the account, but if connection to it is lost, the additional devices continue to work (this became possible with the implementation of multi-account technology).
However, it’s important to understand that the linked device mechanism is designed for user scenarios—simultaneous use of the web version, a tablet, and a second phone. It is not optimized for connecting multiple API gateways or bots to a single account.
Отправить отзыв
Working with one linked device
The most reliable scenario is to use a single GREEN-API instance for automation. In this case, your WhatsApp account connects to the service via linked device technology, while all other clients (the official phone app, WhatsApp Web) remain active.
With this configuration:
- All messages are correctly delivered to all points: the API, the phone, and the web.
- Notifications and webhooks are processed without interruption.
- Messages sent via the API are predictable, without conflicts.
This is the only configuration guaranteed to be supported and tested by us. If you plan to use GREEN-API for business, we strongly recommend limiting yourself to one API connection per account.
Working with WhatsApp Web and WhatsApp Desktop
Using official clients (WhatsApp Web, WhatsApp Desktop) alongside the API instance is acceptable. Many of our clients simultaneously use the web version for manual communication and the API for automated messaging or CRM integration.
From WhatsApp’s perspective, Web and Desktop are simply connected devices. They don’t conflict with the API, as each device operates independently. However, it’s worth considering:
If you’re actively working in the web version while the API is sending messages, there may be short-term synchronization delays.
Some features (such as changing your online status) may not appear instantly on all devices.
In general, using a single API instance with one or more official clients is a stable scenario that doesn’t lead to critical errors.
Working with other services
The riskiest scenario is connecting two or more API instances (for example, GREEN-API and another service) to a single account. Why is this dangerous?
How does it work technically
Each API instance acts as a separate linked device. WhatsApp broadcasts incoming messages to all active devices simultaneously. If you have two API services connected, both will receive the message notification and attempt to process it.
Problems you may encounter:
Duplicate processing — Two services can independently write the same message to the database, send the same response, and trigger duplicate actions.
Lost notifications — In some cases, one device may “drop” the receipt confirmation, preventing the message from being delivered. This results in one API instance receiving the message but not the other.
Sending conflict — If two services attempt to send a message from the same account simultaneously, synchronization errors and even temporary functionality blocking are possible.
Why isn’t this being tested
We haven’t tested the scenario of connecting multiple automated services to a single WhatsApp account. Their architecture is designed for user devices, where interactions are initiated by a human. Therefore:
- As the developers of GREEN-API, we also cannot guarantee stability when connecting multiple API instances.
- Any failures in this mode will be unpredictable and difficult to diagnose.
If you must use two different API services (for example, one for newsletters and one for a chatbot), we recommend:
Separate accounts — use different WhatsApp numbers for different tasks.
If separation is not possible, thoroughly test the load and monitor system behavior.
Be prepared for losses — messages may be missed or processed incorrectly in this setup.
Final recommendations
Optimal: one API instance + official clients (WhatsApp Web, Desktop).
Acceptable: one API instance + other connected devices (tablet, second phone).
Not recommended: two or more API instances on one account – high risk of data loss and unstable operation.
We’re always ready to help you find a solution that will work reliably for your specific scenario. Contact our technical support, and we’ll work together to find the best option.
As a reminder, GREEN-API provides a flexible API for messaging and process automation in WhatsApp. Our technical support and sales teams will be happy to share all the necessary information and offer the best solution for your needs.
GREEN-API – your guide to the world of technology and communications!