Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(api): separate the contacts 400 and 409 not-started cases

Yudhi Armyndharise2fcc8104289
diff --git a/docs/06-api-specification.md b/docs/06-api-specification.md
index 4bf99c9eb..b553650aa 100644
--- a/docs/06-api-specification.md
+++ b/docs/06-api-specification.md
@@ -2371,7 +2371,7 @@ Cancel a running (pending/processing) bulk batch. No request body.
### 6.4.3 Contacts
-Contact endpoints are scoped under a session: `/api/sessions/:sessionId/contacts`. All read routes require a valid API key, except the number check (`GET .../check/:number`), which requires an `OPERATOR` key because each call queries WhatsApp about a third party and bulk checks put the linked account's standing at risk; the block/unblock writes require an `OPERATOR` key. Every route returns `400 "Session is not started"` when the target session is missing entirely or is not in a started/ready state (the engine guard does not distinguish the two). Responses are the raw handler payload (no envelope).
+Contact endpoints are scoped under a session: `/api/sessions/:sessionId/contacts`. All read routes require a valid API key, except the number check (`GET .../check/:number`), which requires an `OPERATOR` key because each call queries WhatsApp about a third party and bulk checks put the linked account's standing at risk; the block/unblock writes require an `OPERATOR` key. Every route returns `400 "Session is not started"` when the session has no running engine (missing or stopped); a started session whose engine is not ready yet (initializing, waiting for QR, reconnecting) answers `409` (retryable). Responses are the raw handler payload (no envelope).
The `Contact` object returned by the list and get-by-id routes has this shape: