WhatsApp has transitioned to the LID (Linked Identity) system in groups, which means participants' phone numbers are often hidden behind long numeric strings (e.g., 250121883230403@lid). This makes it difficult to identify senders on the dashboard.
However, after analyzing the Raw Data provided by your API, I noticed that the person's profile name is already available in the payload.
Reference Payload Snippet:
JSON
{
"author": "250121883230403@lid",
"_data": {
"notifyName": "Oğuz Kaya"
}
}
The Request:
Since the phone number is obscured by the LID, the notifyName (Pushname) field becomes the only reliable source to identify the user.
Could you please ensure that:
The notifyName field is consistently included and populated in all message and message_create payloads, especially for group interactions.
If possible, provide this field at the top level of the message object (instead of only inside _data) to ensure long-term stability for backend mapping.
Why this is needed:
By having a guaranteed notifyName, our backend can automatically map the LID (250121883230403@lid) to the human-readable name ("Oğuz Kaya") in our contacts database. This allows us to display proper names on our UI instead of anonymous numeric IDs.
Thank you for providing such detailed raw data and for your support on this development.
Best regards,
WhatsApp has transitioned to the LID (Linked Identity) system in groups, which means participants' phone numbers are often hidden behind long numeric strings (e.g., 250121883230403@lid). This makes it difficult to identify senders on the dashboard.
However, after analyzing the Raw Data provided by your API, I noticed that the person's profile name is already available in the payload.
Reference Payload Snippet:
JSON
{
"author": "250121883230403@lid",
"_data": {
"notifyName": "Oğuz Kaya"
}
}
The Request:
Since the phone number is obscured by the LID, the notifyName (Pushname) field becomes the only reliable source to identify the user.
Could you please ensure that:
The notifyName field is consistently included and populated in all message and message_create payloads, especially for group interactions.
If possible, provide this field at the top level of the message object (instead of only inside _data) to ensure long-term stability for backend mapping.
Why this is needed:
By having a guaranteed notifyName, our backend can automatically map the LID (250121883230403@lid) to the human-readable name ("Oğuz Kaya") in our contacts database. This allows us to display proper names on our UI instead of anonymous numeric IDs.
Thank you for providing such detailed raw data and for your support on this development.
Best regards,