What is WhatsApp Groups API?
Meta’s WhatsApp Groups API lets Official Business Accounts create invite-only groups (up to 8 participants) for messaging and collaboration. Learn eligibility (OBA), invite links, pricing per delivered member, customer service windows, and practical use cases for business owners. Meta’s Cloud API feature for Official Business Accounts to create invite-only WhatsApp groups (up to 8 participants), send invite links, and message the group programmatically.
Last updated: 5 August 2026
WhatsApp Groups API lets verified businesses create invite-only WhatsApp groups programmatically — then message the whole group from Cloud API. It is not a replacement for unmanaged “staff + customers” chat groups on the consumer app. It is a controlled, API-driven collaboration space for small high-value cohorts (deal rooms, VIP pods, project squads) — available to Official Business Accounts (OBA).
Source: Meta Groups API overview · Get started · Pricing. This guide focuses on what business and website owners need to decide before engineering builds.
Too long? Start here
- Eligibility: Official Business Account (OBA / green-tick style verification) — Groups API is open to all OBAs
- Max participants: 8 per group · Max groups: 10,000 per business number
- Invite-only: users join via your invite link; you do not force-add people
- Pricing: per-message Cloud API rates × each member the message is delivered to
- Not for: WhatsApp Business app numbers, Multi-solution Conversations numbers, calling inside groups
- Best use: small B2B deal rooms, VIP client pods, project teams — not mass “broadcast groups”
What is the WhatsApp Groups API?
Groups are an invite-only experience. You create a group via API, Meta returns an invite link with group context, you send that link (usually via an approved group invite link template), and users decide whether to join. When they join, a webhook fires and you can message the group.
Supported message types: text, media, text-based templates, and media-based templates. One Cloud API business per group. You can pin messages, manage settings, remove participants, reset invite links, and optionally require join requests.
Eligibility: why OBA matters
To use Groups API, Meta requires an Official Business Account (OBA). Groups are not available for:
- WhatsApp Business app phone numbers (consumer / coexistence Business App path)
- Numbers onboarded to Multi-solution Conversations
Practical takeaway for owners: if you are still on the free Business App only, Groups API is off the table. You need Cloud API + OBA. Green tick / OBA playbook: our WhatsApp blue tick / verification page and tutorials hub green-tick steps.
Why business owners should care
| Business need | How Groups API helps |
|---|---|
| High-touch B2B deals | One group for buyer + 1–2 stakeholders + your AE/CSM — shared context without email sprawl |
| VIP / concierge clients | Small invite-only pods for launch access, private drops, account updates |
| Project / implementation squads | Client + vendor + partner in one audited thread (API-controlled membership) |
| Dealer / key-account pods | Replace leaky personal groups with invite links you can reset and revoke |
| Website / portal “join room” | After a demo booking or paid plan, send invite template from your site CRM |
With a hard cap of 8 participants, this is collaboration — not a 5,000-person announcement channel. For mass updates, keep using Marketing/Utility templates and broadcasts on 1:1 Cloud API.
Where website owners fit in
- Post-purchase / thank-you page: “Join your private onboarding group” after a high-ticket sale
- B2B demo confirmation: invite the prospect + optional colleague into a deal room
- Partner portal: generate a fresh invite link per partner account; reset if shared too widely
- Support escalation: move a messy ticket into a short-lived group with specialist + customer
Always pair with clear consent and purpose. Groups are invite-only — users still choose to join. Do not paste invite links publicly if you only want vetted members; use join-request mode when available for tighter control.
How it works (owner view)
- Confirm Cloud API number + OBA + webhooks subscribed to group fields (
group_lifecycle_update,group_participants_update,group_settings_update,group_status_update) - Create group (subject + optional description) → lifecycle webhook returns
invite_link - Add a Group invite link template from Meta Template Library (Group invite upon request) and get it approved
- Send invite to candidates via that template
- On join →
group_participants_updatewebhook → you may message the group - Send/receive text, media, and group-ready templates; pin important updates; remove members when done
Full engineering path: Get started with Groups API. Cloud API basics: Cloud API get started.
Limits and what is not supported
| Limit / rule | Detail |
|---|---|
| Max participants | 8 |
| Max groups per business number | 10,000 |
| Cloud API businesses per group | 1 |
| Calling API | Not supported in groups |
| Unsupported message types | Calling, disappearing, view-once, auth, commerce, interactive messages |
| Unsupported actions | Admin hide participant list, edit message, delete message |
| Template analytics | Performance metrics are not available for templates used in Groups — create Groups-specific templates |
Pricing: the gotcha business owners must model
Groups use Cloud API per-message pricing — but you are charged for each delivered recipient in the group.
Example: send one billable marketing template to a group of 5; if it delivers to all 5, you pay 5 × the marketing rate for each recipient’s country — not one flat “group fee.”
- Delivered to 4 of 5 → charged for 4 only
- Rates follow the same per-message rate card as 1:1 (group utility is not eligible for volume tiers)
- Webhook pricing categories include
group_marketing,group_utility,group_service
Customer service windows work differently: when any WhatsApp user in the group messages you, a service window opens (or refreshes) for the entire group. Inside that window you can send utility and free-form messages for free (pricing type free_group_customer_service). That is different from 1:1, where the window is only with that one customer.
Deep dive: Groups API pricing · general rates: WhatsApp API pricing.
Groups vs 1:1 messaging vs unmanaged groups
| Groups API | 1:1 Cloud API | Personal/Business App group | |
|---|---|---|---|
| Control | API create, invite, remove, reset link | Per contact | Manual; staff phones |
| Scale of chat | Max 8 people | Unlimited contacts (tier limits) | Large groups possible but unmanaged |
| Audit / CRM | Webhooks → inbox/CRM | Mature BSP tooling | Weak / none |
| Cost model | Per delivery × members | Per message / conversation rules | “Free” but risky for brands |
| Best for | Deal rooms, VIP pods | Support, marketing, OTP | Informal internal chats only |
Dealers who still run pricing in random WhatsApp groups should migrate key accounts to API inbox or small Groups API rooms — see our dealer/distributor messaging angles in the integration and industry guides.
Feature checklist (management + messaging)
Management: create/delete group, join requests, get/reset invite link, send invite template, remove participants, get group info / active groups, update settings.
Messaging: send group messages, receive group messages, pin / unpin.
References: Group management · Group messaging.
Owner playbook: launch one pilot group
- Confirm OBA status on your Cloud API number (or start verification)
- Pick one use case (e.g. “enterprise onboarding room” — max 6 people)
- Budget the cost: estimate weekly billable templates × members × rate
- Create Groups-specific templates (do not reuse 1:1 marketing templates if you need clean analytics later)
- Wire webhooks to your BSP inbox / CRM
- Run 3–5 real client rooms for 30 days; measure reply latency and cost vs email threads
- Document when to close/delete groups so you do not accumulate dead rooms
DIY vs Ominiflow
Direct Groups API needs OBA, webhook subscriptions, template library setup, and careful pricing instrumentation. Most business owners want the group events inside the same shared inbox as 1:1 chats — that is the BSP layer. Ominiflow runs on Cloud API with Meta fees at cost; ask during onboarding whether your number’s OBA status unlocks Groups for your use case.
Related: API integration guide · setup guide · pricing · book a call.
FAQ
What is WhatsApp Groups API? expand_more
Meta’s Cloud API feature for Official Business Accounts to create invite-only WhatsApp groups (up to 8 participants), send invite links, and message the group programmatically.
Do I need a green tick / OBA for Groups API? expand_more
Yes. Meta requires an Official Business Account. Groups are not available on WhatsApp Business app numbers or Multi-solution Conversations numbers.
How many people can be in a WhatsApp API group? expand_more
Maximum 8 participants. You can create up to 10,000 groups per business number.
How is Groups API priced? expand_more
Per-message pricing applies per delivered member. One marketing template delivered to 5 members can bill as 5 marketing messages at each recipient’s country rate.
How do customer service windows work in groups? expand_more
When any member messages you, a service window opens or refreshes for the entire group — unlike 1:1 where the window is only with that customer.
Can I use WhatsApp Calling inside Groups API? expand_more
No. Calling API is not supported in groups. Interactive, auth, commerce, disappearing, and view-once message types are also unsupported.
Should website owners use Groups for newsletter subscribers? expand_more
No. Use In-App Signup and Marketing templates for list growth. Groups are for small, high-context collaboration rooms after OBA eligibility. Updated August 2026. Based on Meta’s WhatsApp Groups API documentation (overview, get started, pricing). Ominiflow is independent and not affiliated with Meta.
