Post to a WhatsApp Channel via API
Channels are WhatsApp's broadcast surface: one publisher, unlimited followers, no chat back. Meta ships no API for them at all, so posting on a schedule normally means a human with a phone. Here it is an endpoint.
Can the official WhatsApp Cloud API do this?
No. You cannot publish to a Channel officially.
Read the full comparisonHow it works
Send to the channel id like any recipient, upload media once and reuse it, prefer link posts for traffic, and confirm from the status event.
Publish a text post
There is no dedicated publish endpoint: you send to the channel id exactly as you would to a person. Keep posts self-contained, because followers cannot ask a follow-up question in the thread.
API reference for this stepPost an image with a caption
Upload once and reuse the media id if the same asset goes to several channels. The caption is the post, so write it as the whole message rather than as a label for the picture.
API reference for this stepShare a link with a preview
A link post with a preview is the highest-performing format for driving people off WhatsApp, which is usually the point of a channel. Put the destination on a URL you control so you can measure it.
API reference for this stepConfirm the post landed
Channel posts produce their own status events. Use them to confirm publication and to key your own record of what went out and when, rather than trusting the send response alone.
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}'Endpoints
Webhook events
messagesMessage sent or receivedonMessages()messages.statusDelivery receipt for a sent messageonMessagesStatus()
What you can build with it
- Publish release notes from CI
When a deploy finishes, the pipeline posts a short summary and a link to the changelog into the product channel. Nobody has to remember to announce a release, and the post goes out at the moment the version is actually live.
- Price list updates for a wholesaler
A wholesaler posts the weekly price sheet as a document into its channel every Monday morning. Buyers who follow get it without the wholesaler holding anybody's phone number, and the same document is reused across regional channels.
- Live results during an event
A results service posts each result as it is confirmed, as a text post with the fixture in the first line. Because followers cannot reply, the feed stays readable even when several results land in the same minute.
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. You cannot publish to a Channel officially.
Meta's Cloud API documents no channel or newsletter endpoints, so there is no way to publish a post from the official platform. Teams that want scheduled, automated publishing to a Channel have no official route at all - it is done by hand in the app or through an unofficial API.
Paraphrase (not a verbatim quote), checked against the Cloud API reference index: the reference contains no publish endpoint for Channels or newsletters.
The official workaround
None. Somebody opens WhatsApp and posts by hand, which is exactly the manual step automation is meant to remove.
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
- Nobody can reply to a channel post, so a call to action that says reply to this message will silently fail. Put a link or a click-to-chat address in the post instead.
- Channel posts still flow through the same per-channel send queue as ordinary messages, so a burst of scheduled posts is paced rather than published simultaneously.
Tutorials by language
Automations and integrations
Frequently asked questions
Is there a separate endpoint for channel posts?
No. The channel id is simply another recipient form accepted by the ordinary send endpoints, which means your publishing code is the same code that sends messages. The only difference is the id you address and the fact that nobody can reply to what you post.
Can I schedule posts in advance?
Not inside WhatsApp - there is no scheduled post object. Schedule it on your side with a job runner and call the send endpoint at the moment you want it published. That also means your scheduler, rather than WhatsApp, owns the retry behaviour if a post fails.
Can I edit or delete a post after publishing?
Editing and deleting follow the same rules as ordinary messages, so both are possible within WhatsApp's own time window and only for posts the linked number sent. Beyond that window the post stands, which is a good reason to have a human approve anything automated before it goes out.
How do I measure whether anyone read it?
Channel analytics inside WhatsApp are limited, and follower identities are hidden, so the practical measure is what happens off WhatsApp: use a link you control in the post and count the clicks. That gives you a real signal without pretending to know who read the post itself.
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.