WhatsApp API Multi Device Version

- @phoneNumber

- example:Hello @628974812XXXX, @628974812XXXX

- Pass phone numbers inmentionsfield to mention users without visible@in message

- Use special keyword@everyoneto automatically mention ALL group participants
- UI checkbox available in Send Message modal for groups

- --basic-auth=kemal:secret,toni:password,userName:secretPassword, or you can simplify

- -b=kemal:secret,toni:password,userName:secretPassword

- --base-path="/gowa"(allows deployment under a specific path like/gowa/sub/path)

- --autoreply="Don't reply this message"

- --auto-mark-read=true(automatically marks incoming messages as read)

- --auto-download-media=false(disable automatic media downloads, default:true)

- --presence-on-connect=unavailableorWHATSAPP_PRESENCE_ON_CONNECT=unavailable

- available— mark as online (suppresses phone notifications)
- unavailable— register pushname without going online (default, preserves phone notifications)
- none— skip presence entirely (pushname won't be registered, contacts may see "-" as name)

- --presence-pulse-enabled=trueorWHATSAPP_PRESENCE_PULSE_ENABLED=true(default:true)

- --presence-pulse-interval=24hcontrols how often each connected device is pulsed
- --presence-pulse-duration=5mcontrols how long the account staysavailablebefore returning tounavailable

- --webhook="http://yourwebhook.site/handler", or you can simplify

- Set via API:PATCH /devices/:device_id/webhookwith{"webhook_url": "https://device-webhook.site/handler"}

- Get via API:GET /devices/:device_id/webhook
- When a device has a custom webhook, events for that device are sent to the device-specific URL
- When no device webhook is set, events fall back to the global webhook (--webhook)
- Set to empty string""via PATCH to clear and use global webhook

- --webhook-ignore-jids="@g.us,628123456789@s.whatsapp.net"(comma-separated list)

- Or environment variable:WHATSAPP_WEBHOOK_IGNORE_JIDS=@g.us
- Supports the@g.us/@s.whatsapp.net/@lidwildcards (match a whole address space) and exact JIDs.
- This filters by conversation/sender and is independent of--webhook-events(which filters by event type). The Chatwoot integration keeps its ownCHATWOOT_IGNORE_JIDS.

tls: failed to verify certificate: x509: certificate signed by unknown authority

- --webhook-insecure-skip-verify=true

- Or environment variable:WHATSAPP_WEBHOOK_INSECURE_SKIP_VERIFY=trueSecurity Warning: This option disables TLS certificate verification and should only be used in:

You can configure the application using either command-line flags (shown above) or environment variables. Configuration can be set in three ways (in order of priority):
- Command-line flags (highest priority)
- Environment variables
- .envfile (lowest priority)

You can configure the application using environment variables. Configuration can be set in three ways (in order of priority):
- Command-line flags (highest priority)
- Environment variables
- .envfile (lowest priority)
- Copy.env.exampleto.envin your project root (cp src/.env.example src/.env)
- Modify the values in.envaccording to your needs
- Or set the same variables as system environment variables

Note: Command-line flags will override any values set in environment variables or.envfile.

- brew install ffmpeg webp

- export CGO_CFLAGS_ALLOW="-Xpreprocessor"

- sudo apt update

- sudo apt install ffmpeg webp

Note: Thewebppackage providescwebp(encoder),dwebp(decoder), andwebpmux(frame extractor) tools. FFmpeg is required for media processing. The libwebp tools (webpmux+dwebp) are used for animated WebP sticker support.
- Clone this repo:git clone https://github.com/aldinokemal/go-whatsapp-web-multidevice
- Open the folder that was cloned via cmd/terminal.
- runcd src
- rungo run . rest(for REST API mode)
- Openhttp://localhost:3000

If you want to build for Raspberry Pi or other ARM devices without needing a C toolchain (CGO), you can use thepuregobuild tag. This will use a pure-Go SQLite implementation.
- Clone this repogit clone https://github.com/aldinokemal/go-whatsapp-web-multidevice
- Open the folder that was cloned via cmd/terminal.
- runcd src
- Build for Raspberry Pi Zero / 1 (ARMv6):

CGO_ENABLED=0 GOOS=linux GOARCH=arm GOARM=6 go build -tags purego -o whatsapp-armv6

CGO_ENABLED=0 GOOS=linux GOARCH=arm GOARM=7 go build -tags purego -o whatsapp-armv7

- If you built ARMv6:./whatsapp-armv6 rest

- If you built ARMv7:./whatsapp-armv7 rest

MCP is not a separate mode or process — it's served by the REST server itself. Whenever./whatsapp restis running, the MCP endpoint is available athttp://<host>:<port><base-path>/mcp(defaulthttp://localhost:3000/mcp) using the streamable HTTP transport. Disable it withMCP_ENABLED=falseor--mcp-enabled=false(default: enabled).

There are 5 consolidated tools; agents pick behavior via atype/actionargument instead of one tool per operation:

For multi-device deployments, theX-Device-Idheader on the MCP client connection selects the device used by every tool call on that connection (falls back to the default device if omitted, same as REST). Any individual call can override it with an optionaldevice_idargument.

Point your MCP client at the/mcpendpoint. It inherits the REST server's basic auth, so include the sameAuthorizationheader your REST calls use:

{ "mcpServers": { "whatsapp": { "url": "http://localhost:3000/mcp", "headers": { "Authorization": "Basic dXNlcjpzZWNyZXQ=", "X-Device-Id": "628123456789" } } } }

headersis optional: includeAuthorizationonly when basic auth is configured, andX-Device-Idonly for multi-device setups.

- ./whatsapp mcp→./whatsapp rest(MCP is now included automatically)
- http://localhost:8080/sse→http://localhost:3000/mcp
- 40 granular tools → 5 consolidated tools (agents pick actions via thetype/actionfield)

docker run --detach --publish=3000:3000 --name=whatsapp --restart=always --volume=$(docker volume create --name=whatsapp):/app/storages aldinokemal2104/go-whatsapp-web-multidevice rest --autoreply="Dont't reply this message please"

docker run --detach --publish=3000:3000 --name=whatsapp --restart=always --volume=$(docker volume create --name=whatsapp):/app/storages ghcr.io/aldinokemal/go-whatsapp-web-multidevice rest --autoreply="Dont't reply this message please"

createdocker-compose.ymlfile with the following configuration:

services: whatsapp: image: aldinokemal2104/go-whatsapp-web-multidevice container_name: whatsapp restart: always ports: - "3000:3000" volumes: - whatsapp:/app/storages command: - rest - --basic-auth=admin:admin - --port=3000 - --debug=true - --os=Chrome - --account-validation=false volumes: whatsapp:

services: whatsapp: image: ghcr.io/aldinokemal/go-whatsapp-web-multidevice container_name: whatsapp restart: always ports: - "3000:3000" volumes: - whatsapp:/app/storages command: - rest - --basic-auth=admin:admin - --port=3000 - --debug=true - --os=Chrome - --account-validation=false volumes: whatsapp:

services: whatsapp: image: aldinokemal2104/go-whatsapp-web-multidevice container_name: whatsapp restart: always ports: - "3000:3000" volumes: - whatsapp:/app/storages environment: - APP_BASIC_AUTH=admin:admin - APP_PORT=3000 - APP_DEBUG=true - APP_OS=Chrome - WHATSAPP_ACCOUNT_VALIDATION=false volumes: whatsapp:

services: whatsapp: image: ghcr.io/aldinokemal/go-whatsapp-web-multidevice container_name: whatsapp restart: always ports: - "3000:3000" volumes: - whatsapp:/app/storages environment: - APP_BASIC_AUTH=admin:admin - APP_PORT=3000 - APP_DEBUG=true - APP_OS=Chrome - WHATSAPP_ACCOUNT_VALIDATION=false volumes: whatsapp:

- Served at/mcpby the REST server (streamable HTTP transport) wheneverMCP_ENABLEDis true; withAPP_BASE_PATHset, the route is<base-path>/mcp.
- Available tools are listed in the "Available MCP Tools" section above.
- Compatible with MCP-enabled AI tools and agents