Can the official WhatsApp API resolve LIDs?
The short answer
Not applicable. The official API never shows you a LID.
What Meta's documentation says
Meta's official WhatsApp Cloud API is built for business messaging: templates, customer-service windows and per-conversation pricing. A large part of what WhatsApp itself can do — groups, channels, status, presence, contact lookups — has no endpoint there at all, which is why so many teams end up looking past it. Everything below is checked against Meta's own published reference, with the link and the date we checked it.
Restricted on the Cloud API
Paraphrase (not a verbatim quote), checked against the Cloud API messages reference: recipients are addressed by phone number and the platform returns its own identifier for a customer; no linked-identity resolution endpoint appears in the reference.
Wapito is an independent product. It is not affiliated with, endorsed by, sponsored by or certified by WhatsApp or Meta Platforms, Inc. WhatsApp is a trademark of Meta Platforms, Inc.
Why the Cloud API restricts it
Meta's Cloud API hands a business an identifier for the customer in a conversation it already manages, so the mapping problem does not arise there - but neither does the capability. There is no official endpoint that takes a linked identity and returns a phone number, because the official platform never exposes linked identities in the first place.
The official workaround, and what it costs
There is nothing to work around, because the official platform has no groups or channels where a linked identity would appear. The trade is that it also cannot see those conversations at all.
What the official route costs is not only the per-message price. Every row below is quoted from Meta's own documentation, with a link to the page and the date it was read.
| What it costs | What Meta's documentation says | Source |
|---|---|---|
| Writing to someone first | A business may send free-form messages only inside a 24-hour customer service window that the user opens by messaging or calling. Once the window closes, only pre-approved template messages may be sent. | Meta's docs checked |
| Every message you send | Meta charges for the WhatsApp Business Platform per message rather than per conversation. The earlier per-conversation model was replaced on 1 July 2025, so any comparison written before that date is out of date; free entry point windows remain an exception. | Meta's docs checked |
| Getting onto the platform | Apps that need advanced access to Meta's permissions may have to complete Business Verification, a process in which Meta collects information to verify the business entity. It is a real onboarding step with a real elapsed time, and it has no equivalent when you link a number you already own. | Meta's docs checked |
How Wapito does it
GET /contacts/{id}/lidResolve a phone number to a LID
curl --request GET \
--url 'https://api.wapito.com/v1/contacts/+15551234567/lid' \
--header 'Authorization: Bearer wpt_YOUR_TOKEN'When you should still use the Cloud API
You need a verified business identity
The official platform is the only route to an Official Business Account: the verified name customers see in place of a phone number, and the badge beside it. A linked number can carry a WhatsApp Business profile, but Meta will never badge it, and no provider can get you one.
You are sending marketing at scale to people who never wrote to you
That is what approved templates are for. Meta charges per message for them and treats the volume as legitimate; the same volume from a linked number is the clearest automation signal there is, and it is how numbers get banned. If outbound campaigns are the whole product, the official platform is the cheaper mistake.
You need Meta's own support and an SLA
A Business Solution Provider gives you a contract, an escalation path and a human to call when delivery stops. Wapito will tell you the moment WhatsApp restricts your number and what it did; nobody outside Meta can make it undo that, and we do not pretend otherwise.
Frequently asked questions
Why did WhatsApp introduce linked identities?
To stop group and channel participation from exposing everybody's phone number to everybody else. It is a privacy improvement for users, and a real migration cost for anyone whose automation assumed the sender of a group message is always a number they can look up.
Is a LID stable over time?
It is stable for a given account, which is what makes it useful as a key. Treat it the way you would treat any external identifier: store it, index on it, and do not try to parse meaning out of it. If the account itself goes away, so does the identity.
Can I message someone using only their LID?
In contexts where the identity is the participant - inside a group, for instance - yes. Starting a fresh one-to-one conversation from an identity alone is not something to rely on, so resolve to a phone number when you need to open a new thread, and expect that to sometimes be impossible.
Related
Do it with Wapito
Other ways to do it
Glossary
Try it on your own number
Create a channel, link a WhatsApp number by QR or pairing code, and call the API in a couple of minutes. The Sandbox plan is free and needs no card.