Type a WhatsApp number into almost any link tool and you’ll get one of two results: a short https://wa.me/… link or a longer https://api.whatsapp.com/send?phone=… one. Both are official WhatsApp domains, both open the same chat, and both have been around for years — which is exactly why the “which one should I use?” question keeps coming up. The short answer: use wa.me. This article explains what each format is, shows that they literally end up in the same place, and covers the few cases where the long form is still worth knowing about.
The two formats side by side
Both links do the same job: they open a WhatsApp conversation with the number they contain, optionally with a pre-filled message. Only the packaging differs.
wa.me carries the phone number in the URL path — digits only, full international format, no plus sign — and takes a single optional ?text= parameter. api.whatsapp.com/send passes the same data as query parameters instead: ?phone= for the number and &text= for the message. The number rules and the URL-encoding rules for the message are identical in both; see the complete wa.me guide or the structured WhatsApp link-format reference for the full syntax.
One system, two doors
Here is the detail most comparisons miss: wa.me and api.whatsapp.com are not two competing services — they are the same endpoint. api.whatsapp.com/send is WhatsApp’s original click-to-chat address; wa.me is the official short domain WhatsApp added later so links would be easier to share. Open a wa.me link and watch the address bar: it redirects (an HTTP 302) straight to api.whatsapp.com/send, with the number from the path converted into the ?phone= parameter.
That redirect settles the reliability question. A wa.me link cannot be “less compatible” than an api.whatsapp.com link, because every wa.me click becomes an api.whatsapp.com request a moment later. On a phone, either link hands over to the WhatsApp app; on a computer, either link lands on the same “Continue to chat” page that opens WhatsApp Web or the desktop app. Whatever the device, the destination is identical.
Why wa.me is the better default
- It’s the format WhatsApp actually documents. The official click-to-chat help pages use wa.me, and the short links the WhatsApp Business app generates in Business Tools are wa.me/message/… links. When Meta hands out a link, it’s a wa.me link.
- It’s barely half the length. https://wa.me/15551234567 is 25 characters; the api.whatsapp.com equivalent is 47 before you’ve typed a single word of message. That matters in bios, printed materials, SMS and anywhere characters are counted.
- It makes better QR codes. A QR code gets denser as its contents get longer. Encode the shorter wa.me form — the WhatsApp QR Generator does — and the code has fewer, larger modules, so it scans more reliably at the same printed size.
- It’s easier for humans. People increasingly recognize wa.me on sight, the way they recognize youtu.be. A tidy short link on a poster or in a bio reads as more trustworthy than a long URL trailing query parameters — even though both are official.
- It survives retyping. A link on a flyer, a slide or a radio spot sometimes gets typed by hand. wa.me/15551234567 is typeable; the query-string version realistically isn’t.
When the long form is fine — or even handy
None of this makes api.whatsapp.com links wrong. A few honest points in the long form’s favour:
- Existing links keep working. WhatsApp has kept api.whatsapp.com/send alive through years of app changes — it is the engine wa.me runs on. If old campaigns, documents or chatbot flows are full of api.whatsapp.com links, there is no need to rewrite them.
- Query parameters suit machines. If a spreadsheet formula, CRM template or script assembles links by concatenating fields, the explicit ?phone=…&text=… shape can be the more natural one to generate.
- One less redirect. An api.whatsapp.com link skips the wa.me hop. In practice the difference is milliseconds, and in-app browsers handle WhatsApp’s own redirect fine — but if you are debugging an exotic environment, the direct endpoint removes one variable.
What you should avoid is a third-party shortener in front of either link. Extra redirect hops through unofficial domains are what actually trips up in-app browsers — and a bit.ly wrapper hides the trustworthy wa.me domain from the person deciding whether to tap. If a link misbehaves, work through the seven common causes before blaming the domain.
The other WhatsApp URLs you’ll run into
While we’re mapping the territory, four more official formats that often get confused with the two above:
| Link | What it does | Share it publicly? |
|---|---|---|
| wa.me/message/CODE | Short link the WhatsApp Business app creates in Business Tools; opens a chat with that business, with an optional preset greeting. | Yes — it’s just a branded wa.me link. |
| web.whatsapp.com/send?phone=… | Jumps straight into WhatsApp Web, skipping the device-choice page. | No — it strands phone users and anyone not signed in to WhatsApp Web. |
| whatsapp://send?phone=… | A deep link straight into the installed app. | No — it does nothing wherever the app isn’t installed. Fine inside your own mobile app. |
| chat.whatsapp.com/CODE | A group invite: joins a group rather than opening a one-to-one chat. | Only to invite people to a group — anyone holding the link can join. |
The verdict
Use wa.me. It opens the exact same chat as api.whatsapp.com/send — via the exact same endpoint — while being shorter, official, easier to recognize, kinder to QR codes and the format WhatsApp itself publishes. Reserve api.whatsapp.com for tooling that prefers query parameters, don’t lose sleep over old links that already use it, and never wrap either in a third-party shortener.
Either way, you don’t have to assemble it by hand: the free WhatsApp Link Generator builds a correctly formatted wa.me link with a live preview of the pre-filled message, and the WhatsApp QR Generator turns the same link into a print-ready code.
Frequently asked questions
Are api.whatsapp.com links deprecated?
No. api.whatsapp.com/send is the endpoint wa.me itself redirects to, so it works exactly as well, and existing links don’t need updating. wa.me is simply the shorter format WhatsApp documents and recommends for sharing.
Do wa.me and api.whatsapp.com links behave differently on desktop?
No. Both land on the same WhatsApp page, which opens the chat in WhatsApp Web or the desktop app. Only web.whatsapp.com/send links behave differently — they skip that page and break for users who aren’t signed in to WhatsApp Web, which is why they shouldn’t be shared publicly.
How do I convert an api.whatsapp.com link to wa.me?
Take the number from the ?phone= parameter and put it straight after https://wa.me/, then carry the ?text= parameter across unchanged. Or paste the number and message into the WhatsApp Link Generator and let it rebuild — and URL-encode — the link for you.
