wa.me vs api.whatsapp.com links
1 min read
Search for click-to-chat and you will find two link formats living side by side, plus a few fossils. Here is the whole picture in two minutes.
The two that work
https://wa.me/919876543210 is the short official domain. It redirects into the app or WhatsApp Web and supports the ?text= message parameter.
https://api.whatsapp.com/send?phone=919876543210&text=... is the older long form. It opens the same chat, supports the same message, and behaves identically once tapped.
Functionally, they are the same feature wearing two addresses.
Why wa.me wins anyway
Three practical reasons. It is shorter, which matters wherever characters are visible or scarce: printed under a QR code, in an SMS, in a bio. It is more legible, so a human reading wa.me/9198... on a poster understands it is a WhatsApp link, while api.whatsapp.com/send?phone= reads like tracking soup. And short links make smaller, less dense QR codes, which scan more reliably at the same print size; the print mechanics are in the QR guide.
There is no case where the long form does something the short form cannot. Our link generator outputs wa.me for exactly these reasons.
The formats to retire
whatsapp://send?phone=... is a raw scheme URL: it works only where the app is installed, fails silently on desktop, and gets blocked by some contexts as a non-web link. chat.whatsapp.com/... is not a chat link at all; it is a group invite, a different feature with different risks, covered in group links vs chat links.
One migration note
If old material of yours carries the long form, there is no urgency: it still works and there is no sign of it breaking soon. Just standardize on wa.me for everything new, so the identity printed on your next batch of anything is the short, human-readable one.