Find and Follow WhatsApp Channels

Find, follow and read WhatsApp Channels.

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. The official API cannot follow or read a Channel.

Read the full comparison

How it works

Search or resolve a link, verify it is the right channel, page back through the history, then handle new posts from the webhook.

  1. Search the directory

    Search returns public channels matching a term. Treat the results as candidates rather than as matches: names are not unique and a lookalike channel is a real risk when you are following on a customer's behalf.

    API reference for this step
  2. Resolve an invite link

    If you already have a channel link, resolve its code to get the name, description and follower count before doing anything else. This is how you confirm you have the official channel and not an imitation.

    API reference for this step
  3. Read what has been published

    Page back through the channel's posts to seed your own archive or to catch up after an outage. Store the message ids so a re-run does not process the same post twice.

    API reference for this step
  4. React to new posts

    New posts arrive as message events from the channel id. Route them by that id so a bridge to another system knows which feed a post belongs to.

curl --request GET \
  --url 'https://api.wapito.com/v1/newsletters/find?q=release%20notes&country=GB&count=50' \
  --header 'Authorization: Bearer wpt_YOUR_TOKEN'

Endpoints

Webhook events

  • messagesMessage sent or receivedonMessages()

What you can build with it

  • Mirror a supplier's channel into Slack

    A retailer follows its main supplier's channel and forwards each new post into the buying team's Slack. Nobody has to watch WhatsApp for stock notices, and the posts are archived with the rest of the team's records.

  • Archive an official announcements feed

    A compliance team follows the regulator's public channel and stores every post with its timestamp, so there is a durable record of what was announced and when, independent of whether the channel later edits or removes a post.

  • Trigger a workflow from a published update

    A logistics operator follows a port authority channel and parses each post for closure notices. A match opens a task in the operations system automatically instead of somebody noticing the message on their phone.

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 follow or read a Channel.

Reading someone else's Channel is outside Meta's Cloud API entirely, which documents no channel or newsletter endpoints. There is no official way to mirror a public WhatsApp Channel into another system, which is why the teams doing it use an unofficial API.

Paraphrase (not a verbatim quote), checked against the Cloud API reference index: the reference has no endpoint for finding, following or reading a Channel.
Meta's WhatsApp documentation — checked

The official workaround

None. A person follows the channel on a phone and reads it there.

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

  • Channel search returns lookalikes. Resolve the invite link you were given rather than trusting a name match, especially when you are following on behalf of a customer.
  • Paging a long channel history is a lot of requests. Store the newest id you have processed and page forward from it rather than re-reading the archive on every run.

Tutorials by language

Frequently asked questions

Can I follow a private channel?

Only if you have its invite link, which is how private channels are shared in the first place. There is no way to discover a private channel through search, and resolving a code you were not given will simply fail. Treat a channel link like any other credential.

Do I get every post as a webhook?

New posts from channels the linked number follows arrive as message events keyed to the channel id, so yes for anything published after you follow. History is a separate problem: page back through the messages endpoint once, then rely on the webhook for everything after that.

Is it legal to republish what I read?

That is a copyright and terms question rather than an API one, and the answer depends on the publisher and your jurisdiction. Reading a public channel to trigger your own workflow is uncontroversial; republishing someone else's posts wholesale is a decision to take with your own legal advice.

Does following count against my quota?

Following and reading are ordinary API requests and count against the request allowance rather than the send allowance, since nothing is being sent. The practical constraint is the rate at which you page history, which is worth spreading out both for your quota and for your number's safety.

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.