Subscribe to a chat's presence
POST/api/sessions/:sessionId/presence/subscribe
Asks WhatsApp to start reporting who is online or typing in this chat. Updates arrive as the presence.update webhook and socket event — there is no synchronous answer, because presence cannot be queried from either engine, only received.
The subscription belongs to the connection: it does not survive a restart or an automatic reconnect, and must be re-issued. Subscribe per chat rather than to everything — WhatsApp emits an update on every transition, so a broad subscription is a firehose.
whatsapp-web.js cannot do this at all (it exposes no presence subscribe and emits no presence event) and answers 501.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 501
- 503
Subscribed; updates now arrive as presence.update events
Session not started
The API key is missing, unknown, revoked, or expired
The API key's role, session or chat scope, or IP allow-list does not allow this operation
Session not found
The session is not connected: an engine exists for it but is not ready, meaning disconnected, reconnecting, or still initializing, so the request never reached WhatsApp. Wait for ready and retry. A send whose first attempt had already run when the session left ready (or WhatsApp Web reloaded its page) is the exception: it answers a 409 with no code that says the message may or may not have been sent, so check the chat before sending it again (a retry with the same Idempotency-Key answers IDEMPOTENCY_OUTCOME_UNKNOWN). 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, and until it has the answer is a 409 naming the reload, with code ENGINE_PAGE_RELOADING and retryAfterSeconds. That takes seconds on most reloads and can take a few minutes, and no event marks its end: ask again at that interval.
The active engine cannot observe presence (whatsapp-web.js)
Baileys could not complete the recipient lookup within the request budget. On send routes, no message was handed to WhatsApp for this lookup failure.