Pin a message in its chat
POST/api/sessions/:sessionId/messages/pin
Pin a message in its chat
Request
Responses
- 200
- 400
- 403
- 404
- 409
- 503
Message pinned
Session not active, or durationSeconds is not one of 86400 / 604800 / 2592000
The whatsapp-web.js engine refused the pin (in a group only admins may pin). The Baileys engine has no acceptance signal and answers 200.
Message not found in the chat
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.
The whatsapp-web.js page connection died mid-request. The pin may or may not have been applied; a retry is safe, but it restarts the pin duration from the moment it succeeds.