Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(api): give send-text's 404 its real cause

Yudhi Armyndharisd4112dcfc459
diff --git a/docs/06-api-specification.md b/docs/06-api-specification.md
index a35df4b86..c55c2902d 100644
--- a/docs/06-api-specification.md
+++ b/docs/06-api-specification.md
@@ -1710,7 +1710,7 @@ rejected with `400` rather than guessing which half was meant.
`messageId` is the WhatsApp message id from the engine. By default (`SIMULATE_TYPING`; set it to `false` to disable) a typing indicator and a humanising pause run before the send: 500 ms plus 45 ms per character, capped at `SIMULATE_TYPING_MAX_MS` (default 5000 ms), with +/-15% jitter.
-**Errors:** `400` unknown body field, validation failure, or session not active / blocked by a plugin hook · `401` missing/invalid API key · `403` key role below OPERATOR · `404` session not found · `500` engine error · `409` conflict or engine not ready (retryable) · `501` not supported on the active engine
+**Errors:** `400` unknown body field, validation failure, or session not active / blocked by a plugin hook · `401` missing/invalid API key · `403` key role below OPERATOR · `404` the `quotedMessageId` could not be resolved (see Quoted sends) · `500` engine error · `409` conflict or engine not ready (retryable) · `501` not supported on the active engine
##### Quoted sends