Read and Update WhatsApp Group Info
Groups are the part of WhatsApp the official Cloud API never reached: there is no endpoint to create one, administer it or read its members. Wapito drives a linked number instead, so a group is an ordinary REST call.
Can the official WhatsApp Cloud API do this?
No. The official API cannot see a group at all.
Read the full comparisonHow it works
List the groups, read one in detail, rename or re-describe it when your own data changes, and follow edits on the webhook.
List the groups this number is in
Page through the list and store the ids as strings. This list is the ground truth for which groups your automation can act on, and it changes whenever someone adds or removes the linked number.
API reference for this stepRead one group in detail
The group object carries the subject, description, creation time, current settings and the participant roll with roles. Fetch it before a write so you are acting on the present state rather than on a cached copy.
API reference for this stepRename or re-describe the group
Subject and description changes are visible to every member as a system message, so make them deliberately. A description that carries the rules and an opt-out route does more for your ban risk than any clever pacing.
API reference for this stepFollow changes over the webhook
Renames, description edits and setting changes made by any admin arrive as group events, which is how a cached directory of groups stays accurate without polling the list endpoint.
curl --request GET \
--url 'https://api.wapito.com/v1/groups?count=50&offset=0' \
--header 'Authorization: Bearer wpt_YOUR_TOKEN'Endpoints
Webhook events
groupsGroup joined, left or updatedonGroups()
What you can build with it
- Keep an internal directory of groups
An agency maintains a dashboard of every client group its shared number belongs to, with the member count and the last activity. The list endpoint seeds it nightly and the group webhook keeps it current between runs.
- Rename a group when the deal moves stage
A project group is named for the stage it is in, so anyone opening WhatsApp can see at a glance what is happening. The rename is driven by the CRM stage change rather than by someone remembering to do it.
- Publish the rules in the description
Every group an automation creates gets a description carrying the purpose, the posting hours and a clear way to leave. It costs one extra call at creation and measurably reduces the reports that come from people who did not know why they were there.
What the official WhatsApp Cloud API does here
Meta's official WhatsApp Cloud API is built for business messaging: templates, customer-service windows and per-conversation pricing. A large part of what WhatsApp itself can do — groups, channels, status, presence, contact lookups — has no endpoint there at all, which is why so many teams end up looking past it. Everything below is checked against Meta's own published reference, with the link and the date we checked it.
Not possible on the Cloud API
No. The official API cannot see a group at all.
There is no group object in Meta's Cloud API, so nothing to list, read or rename. A business on the official platform cannot even enumerate the groups its number belongs to, because from the platform's point of view the number does not belong to any.
Paraphrase (not a verbatim quote), checked against the Cloud API reference index: the reference has no group node to read or update.
The official workaround
None. The information exists only on the phone, so any directory of groups a business keeps has to be typed in and kept current by a person.
Wapito is an independent product. It is not affiliated with, endorsed by, sponsored by or certified by WhatsApp or Meta Platforms, Inc. WhatsApp is a trademark of Meta Platforms, Inc.
Gotchas
- The group list can be long and is paged; a job that reads the first page only will act on a stale subset without ever reporting an error.
- Renames and description edits require admin rights on most groups, and every edit is announced in the group, so a retry loop that re-applies the same subject produces repeated system messages.
Tutorials by language
Automations and integrations
Frequently asked questions
Why is a group missing from the list?
Either the linked number is not in it, or the session has not finished syncing. A newly paired number receives its groups over a short period rather than instantly, so a directory built in the first minutes after pairing will be incomplete. Re-read it once the session reports itself healthy.
Can I read a group my number is not in?
Only its public metadata, and only if you hold an invite code for it - resolving a code returns the name, size and owner without joining. Beyond that, a group is invisible to a number that is not a member, which is a deliberate part of how WhatsApp works.
Does the group object include every participant?
It includes the participant roll with each member's role, which is what most automations need. For very large groups, prefer the dedicated participants endpoint so you can page through the membership instead of pulling one enormous object on every read.
How fresh is the data?
It reflects what the linked session currently knows, which is near-real-time while the session is healthy and stale while it is reconnecting. Treat the group webhook as the authoritative stream of changes and the list endpoint as the way to rebuild state after an outage.
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.