RUSTWA

Product Introduction

1. Definition: RUSTWA is a Rust-based headless browser automation tool designed specifically for interacting with WhatsApp Web via a REST API. It leverages Chromium/Chrome in headless mode to automate message sending, receiving, and session management.
2. Core Value Proposition: RUSTWA eliminates feature bloat and complex configurations, providing a high-performance, minimalistic WhatsApp Web API focused on essential automation tasks like sending messages/media, receiving webhooks, and managing multiple sessions. Its goal is to cover ~90% of WhatsApp automation use cases efficiently.

Main Features

1. Headless Browser Automation with Internal Store API:

   • How it works: Uses Chromium via Rust libraries to interact with WhatsApp Web. Instead of UI simulation, it directly accesses WhatsApp’s internal window.Store API (similar to whatsapp-web.js) for operations. Media files are downloaded from URLs, processed via Store.MediaPrep, and uploaded via Store.MediaUpload, enabling native-like message delivery in ~7–10 seconds.
   • Tech Stack: Rust, Tokio async runtime, Chromium DevTools Protocol.

2. QR Authentication & Session Persistence:

   • How it works: Generates QR codes via /api/sessions/{id}/qr endpoint. Once scanned, session data (cookies, tokens) is saved in an embedded sled key-value database. Sessions persist across restarts, eliminating repeated logins.
   • Tech Stack: sled DB, WebSocket-based QR refresh.

3. Webhook-Driven Message Reception:

   • How it works: Incoming messages trigger real-time HTTP/S webhooks. Supports include_media_data=true to attach Base64-encoded media (images, videos, documents) directly to payloads. Events include message, authenticated, and disconnected.
   • Security: Optional HMAC signatures via secret parameter.

Problems Solved

1. Pain Point: Traditional WhatsApp automation tools suffer from UI fragility, slow media uploads, and excessive features that complicate deployment. RUSTWA’s headless approach and internal API usage ensure reliability and speed.
2. Target Audience:
   • Developers building WhatsApp chatbots or CRM integrations.
   • Operations Teams automating internal notifications (e.g., order alerts, OTPs).
   • Small Businesses needing multi-session support for customer support.
3. Use Cases:
   • Broadcast text/image alerts to customer lists.
   • Sync incoming support messages to ticketing systems via webhooks.
   • Deploy lightweight WhatsApp backends on ARM devices (Raspberry Pi).

Unique Advantages

1. Differentiation: Unlike bloated SaaS tools or Python scripts, RUSTWA offers a compiled, dependency-light binary (thanks to Rust) with zero cloud requirements. It outperforms Puppeteer/Playwright solutions by using WhatsApp’s private API for media.
2. Key Innovation: Vendor-agnostic media handling – any publicly accessible URL (image/video/document) can be sent without pre-uploading. Combined with multi-platform support (Linux ARM, Windows, macOS), it enables edge deployments.

Frequently Asked Questions (FAQ)

1. Does RUSTWA require a Chrome/Chromium installation?
   Yes, Chromium or Chrome must be installed on the host system. RUSTWA launches it headlessly via the DevTools Protocol. Docker images include Chromium.

2. Can RUSTWA send messages to groups or manage contacts?
   No. By design, RUSTWA excludes group management, contact syncing, and status features to maintain simplicity and focus on core messaging.

3. How does RUSTWA avoid WhatsApp account bans?
   It mimics human interactions via the official web client and uses anti-detection flags. However, users must comply with WhatsApp’s Terms of Service – avoid spamming and use official business accounts for critical workflows.

4. Is media data included in webhooks by default?
   No. Base64 media is attached only if include_media_data=true is set during webhook registration. Otherwise, messages contain metadata only.

5. Can RUSTWA run on Raspberry Pi or low-resource devices?
   Yes. Pre-built ARMv7/ARM64 binaries support Raspberry Pi. Use Docker or the --shm-size=2g flag to allocate shared memory for Chromium.