The state of the WhatsApp Groups API in 2026: available, but mostly blocked by OBA

Meta has a WhatsApp Groups API. It can create groups, invite users, send group messages, receive group messages, manage participants, and process group webhooks.

But for most businesses, the practical answer is still: you probably cannot use it yet.

The reason is eligibility. As of the May 21, 2026 Meta documentation, Groups API is available to businesses with an Official Business Account, or OBA. Most companies building on the WhatsApp Business Platform do not have OBA status.

That makes the Groups API real, but not broadly usable.

TL;DR

• WhatsApp Groups API exists and is documented.
• Eligibility requires an Official Business Account.
• Groups are invite-only.
• Max group size is 8 participants.
• Supported messages include text, media, text templates, and media templates.
• Unsupported message types include calling, auth, commerce, interactive messages, disappearing messages, and view-once messages.
• Groups API is not available for WhatsApp Business app numbers.
• Groups API is not available for numbers onboarded to Multi-solution Conversations.
• Kapso does not currently expose a supported customer-facing Groups API surface for Kapso-managed numbers.

What the Groups API can do

At a high level, Groups API supports two categories of operations.

Group management:

• create a group
• delete a group
• get or reset an invite link
• handle join requests
• remove participants
• get group info
• list active groups
• update group settings

Group messaging:

• send text messages
• send media messages
• send text-based templates
• send media-based templates
• receive group messages
• receive group status webhooks
• pin and unpin group messages

The API uses group IDs as message recipients. A group message send uses the Messages API with recipient_type set to group and to set to the group ID.

The eligibility problem

The important requirement is simple:

To use Groups API, the business must have an Official Business Account.

That is a high bar. OBA status is not the same thing as:

• having a verified business portfolio
• having an approved display name
• using Cloud API
• having a paid WhatsApp Business Platform account
• being able to send normal 1:1 WhatsApp messages

Many legitimate businesses can use WhatsApp Cloud API without having OBA status. Those businesses should not assume Groups API is available to them.

If you try to build against Groups API without eligibility, the relevant failure mode is a phone-number eligibility error rather than an ordinary integration bug.

Key limits

The Groups API is not a general-purpose replacement for consumer WhatsApp groups.

Important limits from Meta’s 2026 documentation:

The max size alone changes the product shape. This is not a large community or broadcast-channel API. It is closer to small-group coordination.

Unsupported surfaces

Meta documents several unsupported message types and actions for groups.

Unsupported message types include:

• calling
• disappearing messages
• view-once messages
• authentication templates
• commerce messages
• interactive messages

Unsupported or unavailable surfaces also include:

• WhatsApp Business app phone numbers
• numbers onboarded to Multi-solution Conversations
• Calling API inside groups

If your group workflow depends on buttons, commerce flows, authentication, or calling, Groups API is not currently the right primitive.

How group onboarding works

Groups are invite-only.

The basic flow is:

1. The business creates a group with a subject and optional description.
2. Meta returns a group lifecycle webhook with an invite link.
3. The business sends the invite link to users, usually through a 1:1 WhatsApp conversation.
4. A user joins the group through the invite link.
5. Meta sends participant update webhooks.
6. The business can send and receive group messages.

This is not the same as silently adding users to a group. Users control whether they join.

Pricing model

Groups API uses per-message pricing.

If a billable message is delivered to five group participants, the business is charged for five delivered messages. If it is delivered to four participants, it is charged for four.

The group service window behaves differently from 1:1 messaging. When any user in the group messages the business, a customer service window opens or refreshes between the business and the entire group. During that window, some group messages can be free depending on type and category.

For analytics and billing, Meta’s group pricing fields distinguish between regular billable messages and free group customer-service messages.

Should you build on it?

For most teams, the answer is not yet.

You should consider Groups API only if:

• your business has OBA status
• the use case works with 8 or fewer participants
• invite-only joining is acceptable
• you do not need interactive messages, auth templates, commerce messages, or calling
• you can tolerate the current analytics limitations
• you are comfortable building against a relatively new surface

Good possible use cases:

• high-touch concierge groups
• small support pods
• small care-team coordination
• premium customer onboarding
• narrow account-management workflows

Poor use cases:

• large communities
• broad broadcasts
• commerce flows with interactive selection
• authentication flows
• general customer support for ordinary businesses without OBA

Kapso status

Kapso does not currently expose a supported customer-facing Groups API surface for Kapso-managed production numbers.

That means:

• Kapso should not promise Groups API support for Kapso-managed numbers today.
• Kapso should not provide raw Meta tokens for Kapso-managed numbers.
• If a customer needs Groups API directly, they likely need a self-managed Meta app and WABA where they control token access and Meta-side eligibility.
• If the use case can work with normal 1:1 WhatsApp messaging, Kapso templates, broadcasts, workflows, and agents are the better path today.

This distinction is important. Meta documenting an API does not mean every provider can expose it immediately, especially when eligibility depends on OBA status.

Common mistakes

Confusing OBA with business verification

Business verification is not enough. OBA is a separate status.

Designing a product around groups before checking eligibility

Check eligibility first. If the phone number is not eligible, no amount of local code will make the API usable.

Assuming groups support every WhatsApp message type

They do not. Interactive, commerce, auth, calling, disappearing, and view-once surfaces are not supported.

Treating groups as a broadcast replacement

Groups max out at 8 participants. For large sends, use normal templates, broadcasts, or other approved WhatsApp messaging patterns.

Assuming Kapso-managed numbers expose raw Meta group operations

Kapso-managed numbers do not currently provide a customer-facing Groups API surface or raw Meta tokens.

Developer checklist

Before investing engineering time, answer these:

• Does the business have OBA status?
• Is the target phone number eligible for Groups API?
• Is the number on Cloud API rather than the WhatsApp Business app?
• Is the number free from Multi-solution Conversations restrictions?
• Does the use case fit 8 participants?
• Can users join by invite link?
• Are supported message types enough?
• Is per-delivered-participant pricing acceptable?
• Do you need template performance analytics?
• Are you building through a provider that actually exposes Groups API?

If any of these answers are no, Groups API is probably not the right path yet.

Bottom line

The WhatsApp Groups API is real, but the practical market is narrow in 2026.

For most companies, the blocker is not code. It is OBA eligibility, product limits, and provider support.

If you are building on WhatsApp today, design around 1:1 messaging, templates, workflows, broadcasts, AI agents, and human handoff first. Treat Groups API as a specialized feature for eligible businesses, not as the default path for group automation.