Groups

Demotes participants to regular users

Demote one or more admins to regular participants.

POST
https://api.wawp.net/v2/groups/{id}/admin/demote?access_token=123456789&id=1234567890%40g.us&instance_id=123456789&participants=%5B%7B%22id%22%3A%221234567890%40c.us%22%7D%5D

Authentication Required

Login to swap the placeholders with your real Instance ID and Access Token.

Log In
Test /v2/groups/{id}/admin/demote endpoint
POST
POST

No query parameters required

This endpoint doesn't expect data in the URL.

Best practices

  • Demote admins who are no longer active to reduce security risks.

  • Communicate with the user before demoting to avoid confusion.

  • Verify admin status before calling this endpoint.

Restoring Governance: The Strategic Withdrawal of Administrative Authority

In the lifecycle of a managed community, authority is a fluid asset that must be actively governed. The Demote Participants endpoint is your primary tool for Centralizing Control and Enforcing Procedural Discipline. It allows you to programmatically revoke the administrative privileges of a user, returning them to the status of a regular member. This endpoint is the critical counterbalance to the Promote API, ensuring that your "Hybrid Moderation" model remains focused, secure, and aligned with your business's current operational requirements.

For enterprise architects, "Demotion" is the act of Permission Reclamation. This guide explores the strategic imperatives of administrative withdrawal and the enforcement of the hierarchy of trust.

🏗️ Architectural Philosophy: The Enforcement of Disciplined State

From a technical perspective, demoting a participant is a Restrictive State Transition. You are narrowing the permission mask of a JID, removing their ability to influence the group's metadata and population.

Key Architectural Objectives:

  • The Power of the Master Admin: Demotion is a "Corrective Power." To successfully execute this call, your Wawp instance must be a Group Admin. This prevents regular members from attempting to "Overthrow" an admin. However, because your API instance is typically the Creator of the group, it possesses a unique "Administrative Immunity" that secondary admins can never challenge.
  • Instant Feature Lockdown: When a user is demoted, their WhatsApp interface instantly updates. They lose the "Edit Group Info" option, the ability to add/remove members, and the ability to lock the group. This "Instant Revocation" is essential for mitigating the impact of a rogue moderator or a stakeholder whose role has changed.
  • Systemic Transparency: Every demotion triggers a system notification in the chat (e.g., "Business Name removed [User] as an admin"). This is a public signal of your system's active governance, reinforcing that the community operates under a structured hierarchy.

🚀 Strategic Use Cases: Rotating Authority and Managing Compliance

Demotion should be used as a routine component of your "Governance Cycle" rather than just a reactive measure.

1. The "Shift Handover" Protocol

In a 24/7 global operations center, many staff members may be added to a VIP case group. To avoid having dozens of active admins (which increases the risk of accidental metadata changes), your system can implement a "Just-in-Time" authority model. As a shift ends, the system Demotes the outgoing manager while promoting the incoming one. This ensures that only the manager currently on duty has the "Administrative Tools" active on their device, minimizing operational clutter and risk.

2. Moderation Probation and Meritocratic Governance

If your system utilizes volunteer moderators from your customer base, demotion serves as your primary tool for Quality Enforcement. If your sentiment analysis engine or a user report detects a moderator engaging in off-topic or disruptive behavior, the system can automatically demote them back to member status. This "Automated Moderation Guardrail" protects the group's health without requiring human oversight from your internal team.

3. Transitioning from "Active Project" to "Long-term Archival"

When a project moves from its "Intensive Phase" to a "Maintenance Phase," the need for multiple active admins decreases. Your system can automatically demote all stakeholders—except for the primary account manager—to regular member status. This "State Simplification" signals to everyone in the group that the primary phase of collaboration has concluded and the channel is now in a monitored, low-activity state.

🔐 Security and Risk Management: The Rogue Admin Threat

Granting admin status to a third party (like a client or a contractor) is a vulnerability. A rogue admin can maliciously clear the group's participants, change the name to something offensive, or lock out other admins.

The "Auto-Correction" Audit

We recommend running a "Governance Audit" every 60 minutes for high-value groups. Using the Get Group Info endpoint, your system should verify the current admin list. If it finds a JID that has been promoted manually (bypassing your API logic) or a JID that should no longer have rights, it should immediately call the Demote Participants endpoint to restore the authorized state. This "Anti-Tamper" logic ensures your API remains the ultimate arbiter of the group's structure.

The Hierarchy of Demotion: Creator Immunity

In the WhatsApp ecosystem, the Creator cannot be demoted. This is a hard-coded security feature of the network. This means that if your Wawp instance created the group, it is physically impossible for any other admin (human or bot) to demote your instance. This "Steel-Clad Anchor" ensures that your business system always retains the master key to the conversation, regardless of how many temporary admins you appoint.

🛡️ Operational Hygiene and Professionalism

Demoting a user is a socially sensitive event. Handled poorly, it can lead to frustration or a sense of being "Punished."

  • The "Rotation Notice" Pattern: Before executing a demotion for operational reasons (like a shift change), send a polite notice to the group or the individual (e.g., "Your moderator shift has concluded. Authority is being transitioned to [New User]. Thank you for your support!").
  • Rate Throttling: Avoid mass-demoting users in a single burst. Like all administrative actions, staggering the calls (5-10 demotions per minute) ensures system stability and reduces the risk of triggering Meta's security heuristics.

⚙️ Engineering Best Practices: The Validation Loop

  1. Check Admin Status Before Demoting: Ensure the user you are trying to demote is actually an admin. Attempting to demote a regular member will result in an API error. Use Get Group Info to perform this pre-flight verification.
  2. Verify Presence: You cannot demote someone who is not a member of the group. If a user leaves the group, their admin status is automatically nullified by the network. Your system should listen for the group.participants.update webhook to keep your internal "Authority Map" current.
  3. Idempotent Recovery: Demoting someone who is already a member is a safe, no-op operation. Use this to your advantage during system recovery or state reconciliation to ensure your groups are in the correct governance posture.

🎯 Conclusion: Mastering the Art of Disciplined Management

The Demote Participants endpoint is the "Check and Balance" of your conversational architecture. It allows you to reclaim authority, mitigate risk, and maintain a clear hierarchy within your communities. By treating the withdrawal of permissions as a routine, strategic operation, you build a community ecosystem that is both flexible and highly governed. You ensure that power is only held by those who currently need it, and that your business system always remains the definitive source of truth and control.

Request Parameters

Configure the parameters required to interact with this endpoint. All query and body arguments are listed below with their details.

Request Body

Sent as a JSON object
string

Your unique WhatsApp Instance ID

Example:
string

Your API Access Token

Example:
string

The unique ID of the group

Example:
array

List of JIDs to demote

Example:

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.

1const baseUrl = "https://api.wawp.net";
2const endpoint = "/v2/groups/1234567890@g.us/admin/demote";
3const params = new URLSearchParams({
4  "instance_id": "123456789",
5  "access_token": "123456789"
6}).toString();
7const body = {
8  "participants": [
9    {
10      "id": "1234567890@c.us"
11    }
12  ]
13};
14
15fetch(`${baseUrl}${endpoint}${params ? '?' + params : ''}`, {
16  method: "POST",
17  headers: { "Content-Type": "application/json" },
18  body: JSON.stringify(body)
19})
20  .then(async (response) => {
21    if (response.ok) {
22      const data = await response.json();
23      console.log("Success:", data);
24      return data;
25    }
26    
27    // Error Handling
28    
29
30    const errorText = await response.text();
31    console.error(`Error ${response.status}: ${errorText}`);
32  })
33  .catch((error) => console.error("Network Error:", error));
Interactive Samples
Ln 33, Col 1javascript

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.

Participants demoted
application/json
boolean *

Example

{
"ok": true
}
Previous TopicPromote participants to admin users
Next TopicMedia Overview

Command Palette

Search for a command to run...