Join info (by code or URL)
Get information about a group using an invite code or URL.
Authentication Required
Login to swap the placeholders with your real Instance ID and Access Token.
Log InNo query parameters required
This endpoint doesn't expect data in the URL.
Best practices
Verify the participant count is below the limit (1024) before attempting to join.
Cache the group icon to reduce bandwidth.
Pre-emptive Discovery: The Strategic Intelligence of Group Probing
In the orchestration of distributed messaging networks, information is the foundation of security. The Get Group Join Info endpoint is your primary tool for Strategic Discovery and Pre-emptive Qualification. It allows your automated systems to "Peek" into a community using an Invite Code or URL, retrieving critical metadata—such as the group's subject, its profile picture, and potentially its description—without actually committing your WhatsApp instance to membership. This endpoint transforms a blind invite into a verified identity, enabling your platform to make intelligent decisions about whether to join, report, or ignore a specific community.
For enterprise architects, probing is the Safety Gate that protects your infrastructure from malicious or irrelevant groups. This guide explores the strategic imperatives of informed discovery.
🏗️ Architectural Philosophy: Metadata Retrieval Without Commitment
From a technical perspective, the Join Info endpoint is a Low-Impact State Resolver. It queries Meta's global directory for the current state associated with a specific Invite Token.
Key Architectural Objectives:
- The Power of the Ephemeral Link: An invite link is a public gateway, but it is also a potential vulnerability. By probing the link before joining, your system can verify if the code is still active. If the group has been deleted or the code has been Revoked, the API will return a 404, allowing your system to clean up its own internal "Active Link" database.
- Identity Resolution and Anti-Spoofing: Many phishing attempts use groups named "Official Support" or "Payment Center." By using the Join Info endpoint, your system can cross-reference the retrieved Group ID (
@g.us) and metadata against your internal whitelist. If the Group ID doesn't match your records, your system can alert the user or refuse to join, providing a critical layer of digital protection. - Resource Conservation: Joining a group is a high-overhead event that involves synchronizing history and pushing notifications to all existing members. Probing is a lightweight metadata request that consumes minimal resources on your instance and has no impact on the group's existing participants.
🚀 Strategic Use Cases: Automated Qualification and Verified Entry
Probing should be a mandatory first step in any "Join" workflow.
1. The "Community Auditor" Workflow
If your business operates a platform where users share group links (e.g., a community directory or a teacher-student marketplace), your backend should use the Join Info endpoint to periodically audit those links. Any link that points to a group with an unprofessional name, a missing description, or an inactive status can be automatically flagged for review or removed from your public UI. This keeps your community directory "Fresh" and high-quality without manual oversight.
2. Verified Entry for Sensitive Operations
In financial or legal environments, you may have "Temporary Case Groups" that exist for specific transactions. When an agent is asked to join a group from a link, your system should automatically intercept that link, call the Join Info endpoint, and display a "Verified" badge in the agent's dashboard if the group's metadata matches the specific Case ID. This ensures your staff only enters authorized business environments, mitigating the risk of social engineering attacks.
3. Contextual Onboarding and Pre-Join Logic
Imagine a customer service bot that handles "Transfer of Care." When a customer shares an invite link to their internal team group, the bot probes the group first. Based on the group's name (e.g., [URGENT] Server Outage), the bot can autonomously decide to join and immediately escalate the case to a senior engineer. By understanding the context before the join, the bot arrives "Ready to Work" rather than entering blind.
🔐 Administrative Mandate: The Root of Informed Consent
Knowing what is on the other side of the door is the foundation of trust.
Mapping the "Pulse" of the Group
The Join Info endpoint provides a snapshot of the group's health. While it doesn't reveal the participant list (for privacy reasons until you join), the subject and icon often tell the whole story. Your system can use "Visual AI" to analyze the profile picture or "Sentiment Analysis" on the subject line to categorize groups before your organization ever sets foot in the room.
Mitigating "Invite Poisoning"
Malicious actors may try to inject their own bots into your groups by sharing their own group links disguised as yours. By religiously using this endpoint to verify the Global-JID of any link encountered, your system builds an "Identity Shield" that stops unauthorized membership propagation before it can start.
🛡️ Operational Best Practices: Risk Assessment and Data Freshness
- The "Audit Snapshot" Pattern: Always store the metadata retrieved from a probe alongside the invite link in your database. If a link "Breaks" later, you have a historical record of what that group was named and who it appeared to be.
- Stale Link Detection: Group metadata changes. If a link has been sitting in your database for 30 days, re-probe it before showing it to a user. This ensures that the user is always clicking on a link that accurately reflects the group's current name and purpose.
- Coordinate with the Join Call: We recommend a
Probe -> Verify -> Joinsequence. Never perform a blindJoincall. The information retrieved during the probe can be used to populate the "Entry Log" in your CRM, providing a clean audit trail of your system's movements.
⚙️ Engineering Best Practices: The Validation Loop
- Handle Code Sanitization: Users often copy-paste full URLs (
https://chat.whatsapp.com/...) rather than just the code. Ensure your implementation can handle both. The Wawp API is designed to be resilient, but pre-cleaning the string in your frontend ensures a faster response. - Idempotent Checking: Probing a group is a side-effect-free operation. You can call it as many times as needed to monitor state changes without fearing rate limits (within reasonable enterprise bounds).
- Cross-Instance Intelligence sharing: If one of your instances probes a link and finds it is malicious, share that intelligence across all your other instances. Your entire infrastructure can be "Immunized" against a bad link through a single probe operation.
🎯 Conclusion: Mastering the Art of the Informed Community
The Get Group Join Info endpoint is the "Eyes" of your community architecture. It is your most powerful tool for maintaining security, ensuring compliance, and performing strategic qualification of external communities. By treating every invite link as an object that must be verified before it is trusted, you build a conversational ecosystem that is resilient to attack and optimized for professional focus. You move beyond "Simple Link Clicking" and into the world of Intelligent Network Exploration, where your authority is protected by information and your presence is always verified and purposeful.
Request Parameters
Configure the parameters required to interact with this endpoint. All query and body arguments are listed below with their details.
Query Parameters & Request Body
Supported in URL Query String or JSON Bodystring | Your unique WhatsApp Instance ID Example: | ||
string | Your API Access Token Example: | ||
string | Group invite code or full URL Example: |
Build with AI using Wawp MCP
MCP READYConnect Wawp API directly to Cursor, Windsurf, or Claude Desktop. Let AI write, test, and execute your WhatsApp integration code automatically!
Request Samples
Use these ready-to-go code snippets to integrate our API into your project quickly and efficiently. Choose your preferred language and library.
Expected Responses
Explore all possible responses and outcomes from the server. We have documented each status code with data examples to make success and error handling easier.
Example
{
"id": "1234567890@g.us",
"subject": "Community Hub"
}Command Palette
Search for a command to run...