WhatsApp Web API wrapper.
  • Rust 99.6%
  • Nix 0.4%
Find a file
Andriel Ferreira 224fbd0e15 feat(client): process history sync payloads in background tasks
move CPU-heavy zlib decompression and protobuf decoding out of the
update stream by introducing IncomingNodeResult. History sync payloads
return a BackgroundHistorySync variant instead of being processed
inline, and the update stream spawns background tasks to handle them
without blocking other incoming events.

both the notification/ib path and the encrypted message path now
spawn their history sync processing via async_global_executor, keeping
the update loop responsive.
2026-07-10 23:04:40 -03:00
waepic feat(client): impl history sync cdn batch download 2026-07-10 16:05:06 -03:00
waepic-client feat(client): process history sync payloads in background tasks 2026-07-10 23:04:40 -03:00
waepic-connection style: avoid using long-path for traits and objects 2026-07-08 23:20:59 -03:00
waepic-session feat(session): auto-clear stored device on server-initiated logout 2026-07-10 13:16:59 -03:00
.envrc chore: iniital commit 2026-06-30 15:20:59 -03:00
.gitignore chore: iniital commit 2026-06-30 15:20:59 -03:00
Cargo.lock feat: bump wacore and waproto rev 2026-07-10 13:29:09 -03:00
Cargo.toml feat: bump wacore and waproto rev 2026-07-10 13:29:09 -03:00
flake.lock chore: iniital commit 2026-06-30 15:20:59 -03:00
flake.nix feat: add wacore simd feature 2026-07-06 23:53:24 -03:00
LICENSE chore: iniital commit 2026-06-30 15:20:59 -03:00
README.md chore(readme): add disclaimer 2026-06-30 15:35:20 -03:00
rust-toolchain.toml feat: add wacore simd feature 2026-07-06 23:53:24 -03:00
shell.nix chore: iniital commit 2026-06-30 15:20:59 -03:00

waepic

Unofficial wrapper for WhatsApp Web API, built with Rust. This project is in an early stage.

Disclaimer

This is an unofficial, open-source reimplementation. Using custom WhatsApp clients may violate Meta's Terms of Service and could result in account suspension.

Acknowledgements

Contributing

We accept pull requests from our Forjego instance and GitHub. Fork either repository, create a feature branch, and submit a pull request. Bug reports and feature requests are also welcome via the issue tracker.

License

Licensed under the Apache License 2.0. See the LICENSE file for details.