Hey Rustaceans!

I've been building a lot around the WhatsApp Business Cloud API lately — and got tired of the pain:

• Sparse docs
• Repetitive HTTP calls
• SDKs in other languages that feel... clunky
• No type safety, no async, no fun

So I did the Rust thing:

whatsapp-business-rs
An async-native, type-safe, extensible SDK for the WhatsApp Business Platform — built for real apps, bots, CRMs, and e-commerce workflows.

Key Features

• Rich message support (text, media, buttons, reactions, etc.)
• Ergonomic, fluent client API (.send().await?, .builder(), etc.)
• Webhook server built-in (signature verification + async handlers)
• Catalog management with streaming support
• Multi-tenant friendly — override auth per request
• Everything typed: no "field": string_or_struct_or_maybe_nothing

It’s built on reqwest, tokio, and axum (internally), and tries to feel "right" in Rust.
Inspired by DX-first principles, builder patterns, and a whole lot of real-world use cases.

Crate

→ https://crates.io/crates/whatsapp-business-rs

Example: Send a Message

client.message("BUSINESS_ID")
      .send("+2348012345678", "Hello from Rust!")
      .await?;

Or start a webhook server in minutes:

server.serve(handler, client).await?;

Or manage catalogs:

client.catalog("CATALOG_ID")
      .create_product(product_data)
      .await?;

It’s still early, but I’m actively improving coverage (templates, contacts, docs) and would love feedback, issues, PRs — or just a “hey, this helped”

Thanks for reading, and big ups to the Rust community for making DX like this even possible.

– Victor

1 post - 1 participant

Read full topic