Important differences in using a lid instead of a telephone number#

WhatsApp is phasing out phone numbers as chat identifiers. We're proactively creating the conditions for working with our API. The architecture and logic for interacting with the API remain the same, but there are a few differences in how the messenger handles contacts.

WhatsApp's changes will affect all users, so it's important to be prepared for the changes. In this article, we'll look at the API changes and what you need to do to continue using the WhatsApp API effectively while maintaining your customer experience.

Contents#

• How messages were previously sent by phone number
• Phasing out the @c.us prefix
• Send messages by @lid
• The need to switch to @lid

How messages were previously sent by phone number#

To send messages, use the Chat Id. GREEN-API supports two chat types: personal chat and group chat.

Previously, it was sufficient to specify the recipient's phone number with the @c.us prefix in the method's request body to send a text message:

    {
    "chatId": "1111111111@c.us",
    "message": "Hello, John Doe"
    }

Phasing out the @c.us prefix#

All message sending methods, chat ID, journals methods, and webhooks use the @c.us prefix for backward compatibility. You will now receive the chat ID as @lid instead.

We strongly recommend switching to using the @lid instead of a personal chat ID.

Send messages by @lid#

In general, sending messages via @lid differs from sending messages via phone number in that the lid must first be obtained from the user's conversation.

If the chat ID is unknown, please use the CheckWhatsapp method first, get the chatId value to send messages by SendMessage and other methods.

Sending a message using @lid

    {
    "chatId": "120650379300963@lid",
    "message": "Hello, John Doe"
    }

The need to switch to @lid#

WhatsApp has announced that the gradual phase-out of phone numbers will continue until approximately the end of 2026, so it's important to be prepared for changes.

This article has shown that the transition to @lid can be accomplished quickly and without significant changes in integration.

That's why it's a good idea to prepare your integration or chatbot for @lid today.