Get a specific channel by ID
GET/api/sessions/:sessionId/channels/:channelId
Get a specific channel by ID
Request
Responses
- 200
- 404
- 409
- 503
Channel details. The whatsapp-web.js engine never fills picture or createdAt; the Baileys engine reads both off the newsletter metadata.
Channel not found. On the whatsapp-web.js engine this also covers a channel that exists but the account does not follow, because the lookup scans the subscribed-channel list; the Baileys engine resolves any channel by id.
The session is not connected — an engine exists for it but is not ready: disconnected, reconnecting, or still initializing, so the request never reached WhatsApp. Wait for ready and retry. A session that was never started answers 400 instead, and the session lifecycle routes answer 409 for a conflicting state rather than this. One window answers this while the session still reads ready: WhatsApp Web periodically reloads its own page and the engine re-injects into it — for those few seconds the answer is a 409 naming the reload; retry shortly.
WhatsApp did not answer within the request budget — the operation may or may not have applied.