Post a text status
POST/api/sessions/:sessionId/status/send-text
Post a text status
Request
Responses
- 201
- 400
- 401
- 403
- 404
- 409
- 503
Text status posted. The recipients allow-list is honored on Baileys only; whatsapp-web.js broadcasts to the account's status-privacy audience.
Invalid request, or the post was blocked by a plugin.
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
No session is running under that id — it was never started, was stopped, or does not exist. These routes report an unstarted session as 404, where the message and group routes report it as 400.
The session is not connected: an engine exists for it but is not ready, meaning disconnected, reconnecting, or still initializing, so the post never reached WhatsApp. Wait for ready and retry. On whatsapp-web.js, WhatsApp Web periodically reloads its own page and the engine re-injects into it: a post made until it has answers a 409 naming the reload, with code ENGINE_PAGE_RELOADING and retryAfterSeconds, and was not posted. A post cut short while it ran is the exception, by a reload on whatsapp-web.js or by a connection replaced or stopped while it was written on Baileys: it answers a 409 with no code that says it may or may not have been published, so check your status before posting it again.
On Baileys, WhatsApp can answer the post with a 503: it rate-limited the request (code 429: nothing was posted) or timed out a query the post awaits (code 408: the outcome is not proven, so the post may have been published). The post also answers 503 when the connection closes before it is written (nothing was posted).