Updates "info admin only" settings
Set whether only admins can update group info.
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.
Metadata Sovereignty: Enforcing the Integrity of Shared Context
In the landscape of professional WhatsApp management, the environment is your brand. The Set Info Admin Only endpoint is your primary tool for Metadata Sovereignty and Structural Governance. It allows you to programmatically toggle the "Lock" on a group's visual and textual identity—including its subject, its description, and its profile picture. By restricting these powers to administrators, you ensure that the group remains a professional, business-led workspace, protecting it from the potential chaos of unauthorized changes by regular participants.
For enterprise architects, managing who can change the environment is as important as the environment itself. This guide explores the strategic imperatives of metadata restriction and the enforcement of trusted communication.
🏗️ Architectural Philosophy: The Locking of Community Attributes
From a technical perspective, this endpoint modifies the Governance Bitmask of the group's metadata.
Key Architectural Objectives:
- Protection of the Branding Baseline: A business group with 500 participants is a high-sensitivity environment. Allowing any one of those 500 users to rename the group to something inappropriate or change the group icon is an unacceptable brand risk. This endpoint allows your system to "Hard-Lock" the branding, ensuring that the visual reality of the chat always aligns with your official corporate identity.
- The Power of Admin Authority: This setting is a "Privileged Toggle." To successfully lock or unlock the group's info settings, your Wawp instance must be a Group Admin. This prevents regular members from trying to "Open Up" the metadata permissions for themselves.
- Persistent Governance State: Once the "Admin Only" flag is set to
true, tips: [ { type: 'warning', title: 'Admin Only', content: 'You must be an admin to change this setting.' }, { type: 'info', title: 'Impact', content: 'Restricting info prevents users from changing the group name/icon.' } ], recommendations: [ "Lock this immediately for branded communities to prevent vandalism.", "Unlock temporarily if you want community-driven branding." ]
the restriction persists until explicitly changed. Even if the group's membership list changes or if new admins are promoted, the structural restriction remains active, providing a "Steel-Clad Safeguard" for your conversational real estate.
🚀 Strategic Use Case: Brand Integrity and Anti-Tamper Orchestration
Metadata sovereignty should be a "Default-On" requirement for any professional integration.
1. The "Formal Business Channel" Posture
For high-trust environments (like a Bank-Customer interaction or a Legal War Room), the group must strictly reflect the official case identity. By calling the Set Info Admin Only endpoint immediately after Creating the Group, your system ensures the workspace is professional from its very first second. This prevents "Vandalism" where a participant might try to change the group name to something informal, preserving the gravity and professional tone of the channel.
2. The "Campaign-to-Community" Lifecycle
Imagine a marketing campaign that starts as a tightly controlled, "Broadcast-First" environment. Initially, the info settings are locked to Admins Only (true). As the campaign matures and the community gains trust, your system might decide to "Transition" the channel into a more collaborative space by setting the value to false. This allows participants to contribute to the group's identity, fostering a sense of co-ownership as the relationship evolves from "Alerts" to "Engagement."
3. Anti-Tamper and Reactive Reconciliation
In environments where multiple human admins are present, one admin might accidentally "Unlock" the group settings. To maintain a strict governance posture, your system should listen for group.update webhooks. If your system detects that the restrict flag has been flipped to false without an authorized API trigger, it can instantly call this endpoint to Re-Lock the Metadata, ensuring your brand's visual board remains under automated oversight at all times.
🔐 Administrative Mandate: The Root of Trusted Communication
Controlling the "Face" of the group is the first step in controlling the conversation.
Centralizing the "Source of Truth"
When metadata changes are restricted to admins, it allows your business to use the Group Description as a Reliable Resource Catalog. If any participant could change the description, they could replace your official support links with fraudulent ones. Locking the info settings turns the description into a "Protected Document," ensuring that users can always trust the information hosted in the group's "About" section.
Structural Integrity in Regulated Industries
For compliance-heavy sectors, maintaining a fixed group identity is often a legal requirement. Auditors need to know that the "Case #123" group they are reviewing was named "Case #123" for its entire duration. By leveraging this endpoint, your system provides a "Governance Lock" that contributes to your platform's overall auditability and regulatory standing.
🛡️ Operational Best Practices: Consistency and Security
- Default to Restricted: unless your use case explicitly requires participant-led branding, we recommend that all enterprise groups be initialized with
value: true. - Coordinated Metadata Updates: When you need to update the group name or icon, do it via the API. Because your API instance is an admin, it will bypass the restriction, allowing you to update the branding while keeping the participants locked out.
- Visual Signaling of the Lock: Participants see a small notification in the group info when permissions are changed. Use this as a signal of "Official Handover." When the group is locked, it signals to users that they are in a professionally managed, high-trust environment.
⚙️ Engineering Best Practices: The Validation Loop
- Verify Admin Status Before Setting: You cannot change the security settings of a group if you are not an admin. Attempting to set this value as a regular member will result in a 403 Forbidden error.
- Idempotent Safety: Setting the value to
truewhen it is alreadytrueis a safe, no-op operation. This allows you to include the "Locking Call" as a mandatory step in your "Project Refresh" scripts without needing complex conditional logic. - Webhook Integration: Listen for the
group.updateevent to confirm that the network has acknowledged the permission change. Once confirmed, you can update your internal CRM's state to reflect that the group is now in a "Governed" posture.
🎯 Conclusion: Mastering the Art of the Governed Workspace
The Set Info Admin Only endpoint is the "Foundation of Integrity" for your community architecture. It is your primary tool for protecting your brand's visual identity, enforcing administrative trust, and maintaining a structured, professional environment for your participants. By treating the "Lock" on a group's metadata as a strategic asset, you build a conversational ecosystem that is resilient to tampering and always aligned with your organization's highest standards of quality and governance. You move beyond simple chat rooms and into the world of Trusted Business Hubs, where every participant knows that the context they are in is official, secure, and perfectly managed.
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 | The unique ID of the group Example: | ||
boolean | True to restrict to admins, false to allow all 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
{
"ok": true
}Command Palette
Search for a command to run...