Unfollow Channel
Stop following a WhatsApp channel.
Authentication Required
Login to swap the placeholders with your real Instance ID and Access Token.
Log InNo query parameters required
This endpoint doesn't expect data in the URL.
Breaking Up: Unfollowing Channels
The /v2/channels/{id}/unfollow endpoint terminates your subscription to a channel. This is the "Cleanup" operation of the Channels lifecycle.
🛑 Why Unfollow?
1. Reducing Noise
Every channel you follow sends messages to your webhook. If you follow 1,000 active news channels, your server might receive 50+ messages per second.
- Best Practice: Periodically audit your subscriptions using
/v2/channelsand unfollow inactive or low-relevance channels to save bandwidth.
2. Privacy & Opt-Out
If you are building a "User Proxy" service (where your users ask your bot to follow channels for them), you must provide an Unsubscribe mechanism. When a user says "Stop," you must call this endpoint to respect their choice and the channel owner's analytics.
⚙️ Technical Behavior
- Webhook Cessation: The moment this call returns
200 OK, tips: [ { type: 'info', title: 'Cleanup', content: 'Removes the channel from your updates list.' }, { type: 'warning', title: 'Analytics', content: 'You will no longer receive view metrics for this channel.' } ], recommendations: [ "Ask for feedback upon unfollowing to improve your content recommendation engine.", "Confirm the action if it's accidental." ]
your instance will stop receiving message events from this JID.
- History Retention: You will still retain access to the messages you already received and stored in your own database, but you may lose access to fetch historical messages from the WhatsApp server for this channel.
- Idempotency: If you call this on a channel you are not following, it will likely return a success or a harmless error. It is safe to retry.
⚠️ The "Zombie" State
In rare cases, if you unfollow a channel but still have it cached locally in your app as "Active," you might try to send reactions/messages to it. These will fail with 403 Forbidden.
- Action: Always update your local "Inventory" immediately after calling this endpoint.
Request Parameters
Configure the parameters required to interact with this endpoint. All query and body arguments are listed below with their details.
Request Body
Sent as a JSON objectstring | Your unique WhatsApp Instance ID Example: | ||
string | Your API Access Token Example: | ||
string | The unique ID of the channel Example: |
Request Samples
Use these ready-to-go code snippets to integrate our API into your project quickly and efficiently. Choose your preferred language and library.
Expected Responses
Explore all possible responses and outcomes from the server. We have documented each status code with data examples to make success and error handling easier.
Example
{
"status": "success",
"message": "No longer following the channel"
}Command Palette
Search for a command to run...