telegram-webapp-sdk 0.11.2

Telegram WebApp SDK for Rust
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89

# Examples

The repository ships several runnable examples, wired into the Cargo workspace.
Each shows a different integration style — from a full Trunk-built Mini App down
to a plain WASM binary and the bot side of a full-stack app.

## `demo/` — Trunk WASM app

A complete Mini App built with the `macros` and `mock` features. It uses
`telegram_page!` / `telegram_router!` for routing and includes components and
pages (`demo/src/components`, `demo/src/pages`). Because it enables `mock`, it
runs in an ordinary browser during development.

```bash
cd demo
trunk serve        # dev server with live reload at http://localhost:8080
trunk build --release
```

The `demo/index.html` loads Telegram's `telegram-web-app.js` and the Trunk-built
WASM bundle.

## `examples/vanilla` — no framework

A pure-WebAssembly example (`examples/vanilla/src/main.rs` + `ui.rs`) that uses
the SDK and the DOM helpers directly, with no Yew or Leptos. It depends on the
crate with the `mock` feature, so it runs standalone. Good starting point if you
want full control over the DOM.

```bash
cd examples/vanilla
trunk serve
```

## `examples/bots/rust_bot` — Telegram bot

A [teloxide](https://github.com/teloxide/teloxide)-based bot
(`examples/bots/rust_bot`) that opens the demo Mini App via WebApp buttons and
receives orders sent from the app through `sendData`. This is the server side —
it is a native binary, not WASM.

```bash
cd examples/bots/rust_bot
cp .env.example .env          # add your TELOXIDE_TOKEN
cargo run
```

Requires a bot token from [@BotFather](https://t.me/BotFather) and an
HTTPS-served WebApp URL.

## `examples/integration` — full-stack

A two-part example showing the frontend↔backend round trip:

- `examples/integration/frontend` — a WASM Mini App that sends a JSON message to
  the bot via `TelegramWebApp::send_data(...)`. (This member is excluded from the
  workspace and built on its own with Trunk.)
- `examples/integration/backend` — a teloxide bot that receives the update's
  `web_app_data`, parses the JSON, and replies.

```bash
# terminal 1 — backend
cd examples/integration/backend
cargo run

# terminal 2 — frontend
cd examples/integration/frontend
trunk serve
```

The data flow: the user opens the Mini App → interacts with the UI → the app
calls `send_data` → Telegram delivers the payload to the bot as `web_app_data` →
the bot processes it and replies.

## Building any WASM example

All the browser-side examples build for `wasm32-unknown-unknown` and are served
with Trunk:

```bash
rustup target add wasm32-unknown-unknown
cargo install trunk
```

## See also

- [Quick Start](Quick-Start-en) — the minimal version of the vanilla example
- [Framework Integration](Framework-Integration-en) — Leptos/Yew patterns used in the demo
- [Mock & Testing](Testing-en) — the `mock` feature that lets these examples run outside Telegram