Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs: answer an unanswered Baileys call-link create with 500

Yudhi Armyndharisbcfc10fe45e5
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8daf38788..3d9164d24 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -295,7 +295,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Baileys: a profile-picture lookup whose connection drops, or that WhatsApp rate-limits or times out (code 429 or 408), answers `503` instead of `200` with a null `url`.
- Baileys: a WhatsApp refusal on the catalog routes answers `403` instead of `500`, an account without a catalog gets the documented empty answer, and a refused product lookup in `send-product` no longer counts toward the send breaker.
- Baileys: a group, channel or catalog call that WhatsApp rate-limits or times out answers `503` instead of a `403` permissions error or a `500` (`404` for the group invite preview, `400` for a group join), except a timed-out group or channel create, which may have succeeded and so answers `500` instead of a retryable `503`.
-- Baileys: a call-link request WhatsApp never answers gets `503` instead of `500`; a retry can create a second link.
- Dashboard Chats: reopening a chat after switching sessions or leaving the Chats page shows the messages that arrived meanwhile, also when the live event feed is unavailable.
- Dashboard Chats: a chat marked unread shows an unread badge in the sidebar and keeps it when a new message arrives.
- Dashboard Chats: sending while a picked file is still loading no longer discards the file or sends the file it replaced.
diff --git a/docs/06-api-specification.md b/docs/06-api-specification.md
index 3780ea79d..7d370681a 100644
--- a/docs/06-api-specification.md
+++ b/docs/06-api-specification.md
@@ -6544,7 +6544,7 @@ Generate a shareable WhatsApp call link.
> caller handed `{ "link": "" }` — or a bare prefix with nothing after it — would pass it to a user
> before discovering it is dead.
-**Errors:** `400` session not ready, or an invalid `type`/`startTime` · `401` missing/invalid API key · `403` WhatsApp generated no link · `409` conflict or engine not ready (retryable) · `500` the whatsapp-web.js page died mid-request (on whatsapp-web.js deliberately not `503`: each call mints a new link, so a client replaying a `503` would create a second one) · `503` (Baileys only) WhatsApp did not answer within the request budget; a link may or may not have been minted, so a retry can create a second one
+**Errors:** `400` session not ready, or an invalid `type`/`startTime` · `401` missing/invalid API key · `403` WhatsApp generated no link · `409` conflict or engine not ready (retryable) · `500` the whatsapp-web.js page died mid-request, or on Baileys WhatsApp did not answer within the request budget; a link may have been minted on either engine, so this is deliberately not `503`: each call mints a new link, so a client replaying a `503` would create a second one
#### POST /api/sessions/:sessionId/calls/:callId/reject