Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(env): say the per-session proxy applies to Baileys too

Yudhi Armyndharisf391743020bd
diff --git a/.env.example b/.env.example
index 7464beab5..b585777de 100644
--- a/.env.example
+++ b/.env.example
@@ -204,8 +204,8 @@ OPENWA_PIDS_LIMIT=2048
# NOTE: the Baileys engine is loaded lazily (dynamic import, only when ENGINE_TYPE=baileys) and adds no
# Node.js floor of its own; the package floor is Node.js 22.19 (engines.node).
# BAILEYS_AUTH_DIR=./data/baileys
-# NOTE: proxy egress is configured PER SESSION via the proxyUrl/proxyType fields on
-# POST /api/sessions (whatsapp-web.js engine only), NOT via environment variables.
+# NOTE: proxy egress is configured PER SESSION, on both engines, via the proxyUrl/proxyType fields on
+# POST /api/sessions or PATCH /api/sessions/:sessionId/proxy (ADMIN), NOT via environment variables.
# Pull the FULL message-history archive on connect (large). Off by default: the engine still enables the
# initial sync (contacts, chats, recent messages, lid mappings) without downloading the entire history.
# BAILEYS_SYNC_FULL_HISTORY=false