Lifecycle
Check a slot at any time:
is_connected reflects the socket; is_logged_in reflects whether the session is valid. Both must be true to send.
Where sessions are stored
Anyone with these files can act as the linked accounts. GOWA creates local storage directories with mode
0700 and protects local session database files and SQLite sidecars with mode 0600. Keep backups encrypted and preserve those permissions when restoring. Do not place session storage under the public statics/ directory.
Back up and restore
Stop GOWA (or snapshot the volume), then copystorages/. With PostgreSQL for DB_URI, back up that database and storages/chatstorage.db together. Restoring both brings every slot back without pairing again.
Do not run two GOWA instances against the same session data. WhatsApp sees two clients with one identity and disconnects one of them.
A slot keeps its per-device webhook URL, signing key, and event filters when you log out and pair again. Deleting the slot removes its configuration. Subscribe to device.logged_out, device.temporary_ban, and device.reachout_timelock to distinguish account restrictions from a network disconnect. See Webhooks.
For managed PostgreSQL sessions, see the Neon setup guide. Changing DB_URI does not migrate existing sessions. The registry and chat history remain in local SQLite, so persist storages/ too.
Presence
Set presence manually with
POST /send/presence ({"type": "available"} or "unavailable").
