Group Invite Link Parser — read a link before you join
Paste a WhatsApp group link and this parser pulls out the invite code, which is the part that actually matters, so you can read what a link points at before you join. The code is the tail of the URL and it is a capability, not an identifier: anybody who has it can join the group, which is why a link pasted into a public forum is a problem and why rotating it regularly is good hygiene rather than paranoia. Extracting the code by hand is easy to get wrong when the link arrived with tracking parameters bolted on, wrapped in a redirect, or split across two lines by an email client. With the code in hand you can resolve it through the API to see the group's name, its size and who owns it before deciding whether to join - which is exactly what an automation should do before accepting an invitation it was handed. The same code is what you pass to the accept endpoint, and what you revoke when a link has travelled further than you intended.
Paste a link and the code, the canonical link and both API calls appear here.
How it works
The parser accepts the link in every shape it tends to arrive in. The plain form with the chat.whatsapp.com host and the code as the only path segment is the common one; the older form with an invite segment in front of the code still exists in forwarded messages and works the same way; a link with a scheme, without one, or with query parameters and a fragment appended by whatever tool copied it are all read down to the same code. A bare code with no host at all is accepted too, because that is what you have when a colleague pastes just the tail into a chat. What is refused is anything that does not look like an invite code once the wrapping is removed, and the refusal is deliberate: a parser that guessed would hand your automation a code that resolves to nothing, or to the wrong group.
Once you have the code, two API calls matter and they do different things. The preview call resolves the code to the group behind it - subject, description, owner, participant count - without joining, which is the step to take before any automatic accept: it is how a bot avoids walking into a group it was invited to by mistake, and it is how a workflow checks that a link it stored months ago is still live. The accept call joins the group, and it takes either the bare code or the whole link, so once you have validated the code here you can pass it on as it is. If the group has join approval switched on, the accept succeeds but the channel lands in the approval queue rather than the member list, and the join shows up only once an admin lets it through.
The security half of this is simple to state and easy to forget. Because the code is the only thing standing between a stranger and your member list, treat it like a password: do not print it where you cannot later reprint, do not paste it into a channel you do not control, and revoke it - which generates a fresh code and kills every copy of the old link at once - when a campaign ends or when a link has clearly escaped. Publishing the link through a redirect you own means a rotation costs you one change on your side and nothing on the poster. Every one of those operations is a single call on the same feature page as the preview endpoint linked below.
Do it with the API
This tool is the browser-side version of one API call.
Frequently asked questions
Does parsing the link let me see the group?
Not on its own - this tool only extracts the code from the URL. Resolving that code into the group's name, size and owner is an API call through a real session, which is what the linked feature page shows. The split matters: extraction is local, resolution touches WhatsApp.
Can I stop an old link from working?
Yes. Revoking the invite generates a fresh code and invalidates every copy of the old link at once - printed posters, forwarded messages, everything. That is why it is worth publishing through a redirect you control, so a rotation does not mean reprinting anything.
Is it safe to share a group link publicly?
Only if you are happy for anyone to join. A better pattern for a public campaign is to turn on join approval first, so requests queue for review, and to rotate the code once the campaign ends. Both are single API calls and both are far easier than removing people afterwards.
Related
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.