{"slug": "wa-me-username-doesn-t-work-yet-i-verified-it-two-ways", "title": "wa.me/username doesn't work yet — I verified it two ways", "summary": "A developer tested whether wa.me/username links work in WhatsApp and found they do not, despite the rollout of @username handles. The server-side route for usernames exists but always resolves as 'not found', and testing on a real phone confirmed the links do not open a chat. The developer recommends using wa.me/<countrycode><number> or @username with a username key instead, and created a free tool at whatsusernames.link to generate working links and QR codes.", "body_md": "`wa.me/username`\n\ndoesn't work yet — I verified it two ways, here's what to use instead\nIf you've tried to build a \"share my WhatsApp\" link using a `@username`\n\ninstead of a phone number, you've probably assumed `wa.me/username`\n\n(or `wa.me/u/username`\n\n) works the same way `wa.me/15551234567`\n\ndoes. It doesn't — at least not yet, as of writing this.\n\nI wanted a definitive answer instead of trusting blog posts or AI chatbot answers (more on that below), so I tested it two independent ways.\n\n```\ncurl -I https://wa.me/u/some_real_reserved_username\n```\n\nEvery username path I tried — including a certified-real, currently-reserved username — 302-redirects to:\n\n```\napi.whatsapp.com/resolve/?deeplink=...&not_found=1\n```\n\nCompare that to the phone-number path, which redirects to:\n\n```\napi.whatsapp.com/send/?phone=...&type=phone_number\n```\n\nDifferent resolver, different outcome. The server-side route for usernames exists, but every lookup currently resolves as \"not found\" — even for real, live usernames.\n\nServer response alone doesn't rule out Universal Links / App Links intercepting the URL client-side before it ever hits a server — `curl`\n\ncan't see that. So I also opened all three link variants (`wa.me/username`\n\n, `wa.me/u/username`\n\n, and a redirect through my own domain) on a real phone with WhatsApp installed.\n\nNone of them opened a chat.\n\nWhatsApp has rolled out `@username`\n\nhandles as a real, user-facing feature — but it hasn't published a public deep-link spec for opening a chat from one, the way it has for phone numbers for years. If you're building a tool, a profile page, a business card generator, anything that assumes `wa.me/username`\n\n\"just works,\" it doesn't, for anyone.\n\nOne more data point: I asked Meta AI directly about this, with the counter-evidence above in hand. It kept asserting the link already works and didn't engage with the evidence when pushed. That's a useful reminder that chatbot answers about a fast-moving platform feature can be reciting stale/roadmap content rather than reflecting the live system — verify claims like this yourself before shipping something that depends on them.\n\nUntil WhatsApp ships the real format, there are two things that work with zero surprises:\n\n`wa.me/<countrycode><number>`\n\nstill opens a chat directly, no manual step, no ambiguity.`@username`\n\n(plus the \"Username Key\" if the person set one, which disambiguates people who share a username) as text or a QR code, with an explicit \"find me by username\" instruction. One extra manual step, but it doesn't expose a phone number.I built a small free tool that generates both — link + downloadable QR — and is explicit on-page about which one actually works right now instead of pretending the username link is live: [whatsusernames.link](https://whatsusernames.link). No signup, nothing stored server-side.\n\nIf anyone finds a case where `wa.me/username`\n\n*does* resolve for them, I'd genuinely like to know — that would mean a staged rollout is underway.", "url": "https://wpnews.pro/news/wa-me-username-doesn-t-work-yet-i-verified-it-two-ways", "canonical_source": "https://dev.to/inside_dc_pulse/wameusername-doesnt-work-yet-i-verified-it-two-ways-20fn", "published_at": "2026-07-04 12:36:04+00:00", "updated_at": "2026-07-04 12:48:55.272569+00:00", "lang": "en", "topics": ["developer-tools", "ai-products"], "entities": ["WhatsApp", "Meta AI", "whatsusernames.link"], "alternates": {"html": "https://wpnews.pro/news/wa-me-username-doesn-t-work-yet-i-verified-it-two-ways", "markdown": "https://wpnews.pro/news/wa-me-username-doesn-t-work-yet-i-verified-it-two-ways.md", "text": "https://wpnews.pro/news/wa-me-username-doesn-t-work-yet-i-verified-it-two-ways.txt", "jsonld": "https://wpnews.pro/news/wa-me-username-doesn-t-work-yet-i-verified-it-two-ways.jsonld"}}