Can the official WhatsApp API create group events?
The short answer
No. The official API has no group events.
What Meta's documentation says
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
Paraphrase (not a verbatim quote), checked against the Cloud API reference index: the reference documents no group node and no event message type.
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.
Why there is no endpoint for it
Event messages live inside groups, and groups are absent from Meta's Cloud API, so there is no event object to create and nobody to invite. This is one of the few pillars where the unofficial route is also incomplete today, and we say so rather than implying otherwise.
The official workaround, and what it costs
None. A business sends each invitee an individual message and reconciles the replies by hand or with its own calendar tooling.
What the official route costs is not only the per-message price. Every row below is quoted from Meta's own documentation, with a link to the page and the date it was read.
| What it costs | What Meta's documentation says | Source |
|---|---|---|
| Writing to someone first | A business may send free-form messages only inside a 24-hour customer service window that the user opens by messaging or calling. Once the window closes, only pre-approved template messages may be sent. | Meta's docs checked |
| Every message you send | Meta charges for the WhatsApp Business Platform per message rather than per conversation. The earlier per-conversation model was replaced on 1 July 2025, so any comparison written before that date is out of date; free entry point windows remain an exception. | Meta's docs checked |
| Getting onto the platform | Apps that need advanced access to Meta's permissions may have to complete Business Verification, a process in which Meta collects information to verify the business entity. It is a real onboarding step with a real elapsed time, and it has no equivalent when you link a number you already own. | Meta's docs checked |
How Wapito does it
POST /messages/textSend a text message
curl --request POST \
--url https://api.wapito.com/v1/messages/text \
--header 'Authorization: Bearer wpt_YOUR_TOKEN' \
--header 'Content-Type: application/json' \
--data '{"to":"+15551234567","body":"Your order #4182 has shipped. Track it here: https://acme.example/t/4182","typing_time":3}'When you should still use the Cloud API
You need a verified business identity
The official platform is the only route to an Official Business Account: the verified name customers see in place of a phone number, and the badge beside it. A linked number can carry a WhatsApp Business profile, but Meta will never badge it, and no provider can get you one.
You are sending marketing at scale to people who never wrote to you
That is what approved templates are for. Meta charges per message for them and treats the volume as legitimate; the same volume from a linked number is the clearest automation signal there is, and it is how numbers get banned. If outbound campaigns are the whole product, the official platform is the cheaper mistake.
You need Meta's own support and an SLA
A Business Solution Provider gives you a contract, an escalation path and a human to call when delivery stops. Wapito will tell you the moment WhatsApp restricts your number and what it did; nobody outside Meta can make it undo that, and we do not pretend otherwise.
Frequently asked questions
Can I create a real WhatsApp event from the API today?
Not yet. The native event message is a client feature that neither engine behind Wapito supports, and the endpoint says so with a not-implemented error instead of failing quietly. What works today is an announcement message plus a poll for responses, which covers the same need with two calls.
Why use a poll instead of asking people to reply?
Because free-text replies in a group of forty are unusable: people answer with words, emoji, or by replying to the wrong message. A poll returns a structured vote tied to a specific participant, so your code knows exactly who said yes without guessing at anybody's phrasing.
How do I remind people who have not responded?
Compare the vote events against the participant list and message the gap directly, one person at a time, rather than posting another reminder into the group. It is more effective and it avoids the pattern that gets automated numbers muted by the people you are trying to reach.
Related
Do it with Wapito
Other ways to do it
Glossary
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.