New WhatsApp rules: key takeaways from the GREEN-API webinar

New chat ID: @lid instead of a phone number

On September 3, we held a Zoom webinar for our GREEN-API clients and partners about important changes to WhatsApp. Over 60 people joined the call. During the meeting, we discussed a new strategy for using the messenger to manage phone numbers, explained Passkey authentication when logging into an account, and presented the latest updates from GREEN-API. We’ve summarized the key points in this article.

WhatsApp is gradually changing its privacy policies. A couple of years ago, the messaging app conducted a survey among users and found that some of them were not entirely comfortable sharing their phone numbers with strangers. Therefore, in the winter of 2025, WhatsApp announced the introduction of usernames to replace phone numbers.

Internal testing began in May of this year, and starting in June, users in some countries gained the ability to hide their phone numbers. By the end of 2026, this new feature will be available to everyone else.

As a result, WhatsApp is introducing a new account identifier: @lid. This new feature is unique in that the @lid is generated automatically and serves as a unique user ID that cannot be shared like a phone number to send someone a message.

The launch of the @lid identifier does not mean that phone numbers will disappear or that you will no longer have access to them. It means that the phone number is optional and @lid will be the primary user identifier.

Our API supports sending messages via both phone numbers and @lid. However, for now, it’s best to stick with your chosen method of using phone numbers. In the future, WhatsApp plans to transition completely to @lid and conduct all communications exclusively through it.

How to find a user’s @lid

You can find a user’s @lid in incoming and outgoing webhooks when enableLidMode is set to true, while the CheckWhatsApp and getContacts methods display the @lid even in normal mode.

The difference in logs and webhooks is minimal: the senderId and chatId fields will display @lid instead of @c.us (as in phone numbers). Nothing changes for group chats; they are still identified by a chatId prefixed with @g.us.

There are two ways to enable the @lid parameter:

1. In your GREEN-API account, go to your instance settings and enable the “Use chat identifiers” option. Log back into the instance and check if the settings have taken effect.
2. In the SetSettings method, set the enableLidMode field to YES.

Note: The YES setting may appear without re-authentication, but it will not take effect and the system will continue to operate in the previous mode. Therefore, please re-authenticate in the instance and verify that the settings have taken effect. If the enableLidMode field returns YES, the instance is ready to work with @lid.

Important!

In the @lid system, all encryption algorithms, keys, group and status functionality, as well as message reception, are tied to @lids. In some regions, accounts without phone numbers are already appearing. You can always find an @lid using a phone number, but not the other way around.

Passkey authentication: logging into WhatsApp without a password

In the summer of 2026, WhatsApp began transitioning some users to the Passkey method for authentication on linked devices, in the web version of the messenger, and in API instances. This is an alternative to regular passwords and provides additional protection for your WhatsApp account. If a user has Passkey set up, authentication is handled through it; if not, everything works as before.

How do you log in to a GREEN-API instance using Passkey?

To use Passkey, you must have a password manager installed on your phone, such as one from Google or Samsung and your lock screen must be enabled.

How to check if WhatsApp has enabled Passkey for your instance:

1. In your account dashboard: when logging in via QR code, you’ll see a notification stating that the extension wasn’t found and needs to be installed;
2. Install it using the QR method; if the response is type: passkeyRequired, it means the number is already protected by a passkey;
3. When you access the web version of the app on your phone, the system will notify you that you need to complete authorization on another device or create a Passkey.

To authorize an instance using a Passkey, you’ll need the GREEN-API Connector extension for Google Chrome. You can download it from the Chrome Web Store.

Passkey authorization for an instance works as follows:

• Go to your account dashboard to authorize the instance
• Scan the QR code from GREEN-API in your personal account
• Get the QR code for Passkey authorization from WhatsApp
• Scan the WhatsApp QR code with your phone and enter the Passkey
• Continue the authorization process on your computer
• Confirm the code on your phone to authorize the instance on your computer
• Wait for the instance to start
• Use the API as usual

You can find more details about this in the latest GREEN-API documentation on our website.

What’s new with GREEN-API

In the third part of the webinar, we showcased the new features the GREEN-API team has prepared for its clients and partners. At the request of some of them, we’ve implemented a feature that notifies you when an incoming message has been read on your primary device. It’s worth noting that you’ll need to disable the automatic marking of all incoming messages as read (markIncomingMessagesRead) and use notifications to check whether a message has been read on your primary device.

Another new feature is the launch of methods for working with product catalogs. Using these catalogs, you can view, create and automate communications with customers via the API, which simplifies order processing and customer communication for business owners.

Conclusion

As you can see, our webinar was informative and productive. Afterward, we held a Q&A session that sparked lively interest among participants: they actively asked questions about the latest changes to Meta’s pricing, @lid identifiers, Passkey authentication and new features from GREEN-API.