3 releases

0.9.2 May 29, 2022
0.9.1 May 29, 2022
0.9.0 Apr 14, 2022

#234 in Web programming

Download history 52/week @ 2022-06-02 18/week @ 2022-06-09 22/week @ 2022-06-16 25/week @ 2022-06-23 24/week @ 2022-06-30 10/week @ 2022-07-07 17/week @ 2022-07-14 32/week @ 2022-07-21 22/week @ 2022-07-28 35/week @ 2022-08-04 35/week @ 2022-08-11 19/week @ 2022-08-18 20/week @ 2022-08-25 35/week @ 2022-09-01 42/week @ 2022-09-08 19/week @ 2022-09-15

117 downloads per month
Used in 4 crates (via pw-telegram-bot-fork)

MIT license

220KB
5.5K SLoC

Rust Telegram Bot Library

Build Status Tests Tests License Crates.io

Documentation: Latest crates.io version master

A library for writing your own Telegram bots. More information here. Official API here.

Example

Here is a simple example (see example/simple.rs):

use std::env;

use futures::StreamExt;
use telegram_bot::*;

#[tokio::main]
async fn main() -> Result<(), Error> {
    let token = env::var("TELEGRAM_BOT_TOKEN").expect("TELEGRAM_BOT_TOKEN not set");
    let api = Api::new(token);

    // Fetch new updates via long poll method
    let mut stream = api.stream();
    while let Some(update) = stream.next().await {
        // If the received update contains a new message...
        let update = update?;
        if let UpdateKind::Message(message) = update.kind {
            if let MessageKind::Text { ref data, .. } = message.kind {
                // Print received text message to stdout.
                println!("<{}>: {}", &message.from.first_name, data);

                // Answer message with "Hi".
                api.send(message.text_reply(format!(
                    "Hi, {}! You just wrote '{}'",
                    &message.from.first_name, data
                )))
                .await?;
            }
        }
    }
    Ok(())
}

You can find a bigger examples in the examples.

Usage

This library is available via crates.io. In order to use it, just add this to your Cargo.toml:

telegram-bot = "0.7"

The library allows you to do E2E-testing of your bot easily: just specify TELEGRAM_API_URL environment variable to point to your fake Telegram test server. A lot of diagnostic information can be collected with tracing framework, see example/tracing.rs).

Collaboration

Yes please! Every type of contribution is welcome: Create issues, hack some code or make suggestions. Don't know where to start? Good first issues are tagged with up for grab.

Dependencies

~1–1.7MB
~38K SLoC