RUSTWA - A Unofficial WhatsApp Web API built in Rust
by•
No feature bloat. No crazy configs. Just the stuff most people actually need:
✅ send text + media
✅ receive messages via webhooks
✅ multi-session support
✅ QR login with session persistence
✅ web dashboard
✅ fast async runtime with Tokio
The goal: cover ~90% of automation use-cases without turning into a monster system.
If you’re building WhatsApp automation, bots, or internal tools — would love for you to try it and tear it apart 😄
Feedback, issues, and PRs are more than welcome.
Replies
RUSTWA
@buyung_bahari
Solid choice with the Rust + Tokio stack! 🦀 Managing headless Chrome instances is usually a memory nightmare, so using Rust here makes perfect sense for efficiency.
Quick question: How does it handle session persistence if the container restarts? Do I need to re-scan the QR code every time, or does it save the session state locally?
Congrats on the launch!
RUSTWA
@arsene94 Thank you! I really appreciate that 🙌
Yes — sessions are persistent. The service saves the session state locally and automatically reloads and reconnects when it restarts, so you don’t need to re-scan the QR code each time.
If you want to see it in action, just download the binary that matches your OS and give it a try — would love to hear your feedback after!
Congrats on the launch — clean, focused WhatsApp automation with Rust is super promising 👏
RUSTWA
@zeiki_yu Thank you for your support
RUSTWA
@vouchy Honestly, I only need the features that cover about 90% of real-world automation use cases: sending messages with attachments and receiving incoming texts (also with attachments) so I can trigger or run automations.
Everything else — advanced group management, reactions, status handling, contact sync, etc. — falls into the remaining 10% that I personally almost never touch. When tools try to include all of that, they usually turn into bloated systems that are harder to run, harder to maintain, and slower to integrate, without adding much value for my actual needs