Expose LID→phone mapping in API to merge @lid + phone JIDs

[pabloruano]

Problem
In WuzAPI, the same 1:1 contact can appear as both:

• 34602335608@s.whatsapp.net
• 204766877589603@lid

This causes duplicate chats and split message history in client apps. The mapping exists in the WhatsMeow store (whatsmeow_lid_map with lid -> pn), but it’s not exposed in the API.

Why it matters
Without the mapping, clients can’t merge chats or show a complete conversation, and they need direct DB access (which is fragile and undermines portability).

Proposed solution
Expose LID mapping via API, for example:

Option A – extend /user/contacts
Add fields like:

• Lid / LID / lid (raw LID value)
• LidJID (e.g. 204766877589603@lid)
• Phone / pn (if available)

Option B – new endpoint
GET /user/lid-map returning { lid: "204766877589603", pn: "34602335608" } pairs.

Result
Clients can merge @lid and phone JIDs without touching the DB and present a single conversation per customer.

Thanks!

[cleitokarloh]

This server error: no LID found for xxxxxxxx@s.whatsapp.net from server

Can this have a relation to this problem?

[asternic]

Maybe this will help?