Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(status): name every cause of the Baileys revoke 403

Yudhi Armyndharisf1affb031176
diff --git a/docs/06-api-specification.md b/docs/06-api-specification.md
index 9d5350205..070a38ac5 100644
--- a/docs/06-api-specification.md
+++ b/docs/06-api-specification.md
@@ -4429,7 +4429,7 @@ Delete one of the session's own posted statuses.
The service returns `void`; the controller returns a fixed success object. DELETE default status is `200`.
-**Errors:** `401` missing/invalid API key · `403` key lacks `OPERATOR` role, or (whatsapp-web.js) the id is not one of the account's own statuses, or (Baileys) this session did not post the status in the last 24 hours, so its recipients are unknown (a status posted from the phone or from another node, or posted before a restart, is refused too) · `404` `Session {id} not found or not connected` · `409` conflict or engine not ready (retryable) · `503` the whatsapp-web.js page died mid-request, so the revoke did not complete
+**Errors:** `401` missing/invalid API key · `403` key lacks `OPERATOR` role, or (whatsapp-web.js) the id is not one of the account's own statuses, or (Baileys) this session did not post the status in the last 24 hours, so its recipients are unknown (a status posted from the phone or from another node, or before this session's engine was last created, is refused too: a process restart, a session stop and start, and a reconnect the gateway runs itself, such as after a failed liveness check, each create a new one) · `404` `Session {id} not found or not connected` · `409` conflict or engine not ready (retryable) · `503` the whatsapp-web.js page died mid-request, so the revoke did not complete
Safe to retry: revoking an already-revoked status converges. The status POST routes deliberately do
NOT answer `503` for the same failure, because whatsapp-web.js can throw after the request is on the
diff --git a/docs/29-engine-capability-matrix.md b/docs/29-engine-capability-matrix.md
index 9019e678c..326c85285 100644
--- a/docs/29-engine-capability-matrix.md
+++ b/docs/29-engine-capability-matrix.md
@@ -934,8 +934,11 @@ adapter boundary — none silently stubs.
- **`deleteStatus` (baileys).** Baileys sends a status stanza, the revoke included, to exactly its
`statusJidList`, so the revoke is addressed to the recipients the adapter remembered when it posted
the status. It keeps them in memory for 24 hours, so a status this session did not post in the last
- 24 hours (one posted from the phone or from another node, or posted before a restart) is refused
- with `403` (`EngineRefusedError`) instead of a revoke that reaches nobody while the status stays up.
+ 24 hours (one posted from the phone or from another node, or before the session's engine was last
+ created: a process restart, a session stop and start, or a reconnect the gateway runs itself, such
+ as after a failed liveness check) is refused with `403` (`EngineRefusedError`) instead of a revoke
+ that reaches nobody while the status stays up. The transient reconnects Baileys runs on its own keep
+ the same engine, and the list with it.
The `sendMessage(status@broadcast, {delete})` revoke shape is _empirically unverified_: only posting
was live-spiked. On wwjs it calls `revokeStatusMessage(statusId)` (own status only).
- **`getContactStatus` / `getContactStatuses` (wwjs).** `Status.type` is the `text|image|video`