Telebot is a Telegram bot framework in Go.

Telebot

"I never knew creating Telegram bots could be so sexy!"

GoDoc Travis codecov.io Discuss on Telegram

go get -u gopkg.in/tucnak/telebot.v2

Overview

Telebot is a bot framework for Telegram Bot API. This package provides the best of its kind API for command routing, inline query requests and keyboards, as well as callbacks. Actually, I went a couple steps further, so instead of making a 1:1 API wrapper I chose to focus on the beauty of API and performance. Some of the strong sides of telebot are:

  • Real concise API
  • Command routing
  • Middleware
  • Transparent File API
  • Effortless bot callbacks

All the methods of telebot API are extremely easy to memorize and get used to. Also, consider Telebot a highload-ready solution. I'll test and benchmark the most popular actions and if necessary, optimize against them without sacrificing API quality.

Getting Started

Let's take a look at the minimal telebot setup:

package main

import (
	"log"
	"time"

	tb "gopkg.in/tucnak/telebot.v2"
)

func main() {
	b, err := tb.NewBot(tb.Settings{
		// You can also set custom API URL.
		// If field is empty it equals to "https://api.telegram.org".
		URL: "http://195.129.111.17:8012",

		Token:  "TOKEN_HERE",
		Poller: &tb.LongPoller{Timeout: 10 * time.Second},
	})

	if err != nil {
		log.Fatal(err)
		return
	}

	b.Handle("/hello", func(m *tb.Message) {
		b.Send(m.Sender, "Hello World!")
	})

	b.Start()
}

Simple, innit? Telebot's routing system takes care of delivering updates to their endpoints, so in order to get to handle any meaningful event, all you got to do is just plug your function to one of the Telebot-provided endpoints. You can find the full list here.

b, _ := tb.NewBot(settings)

b.Handle(tb.OnText, func(m *tb.Message) {
	// all the text messages that weren't
	// captured by existing handlers
})

b.Handle(tb.OnPhoto, func(m *tb.Message) {
	// photos only
})

b.Handle(tb.OnChannelPost, func (m *tb.Message) {
	// channel posts only
})

b.Handle(tb.OnQuery, func (q *tb.Query) {
	// incoming inline queries
})

There's dozens of supported endpoints (see package consts). Let me know if you'd like to see some endpoint or endpoint idea implemented. This system is completely extensible, so I can introduce them without breaking backwards-compatibility.

Poller

Telebot doesn't really care how you provide it with incoming updates, as long as you set it up with a Poller, or call ProcessUpdate for each update (see examples/awslambdaechobot):

// Poller is a provider of Updates.
//
// All pollers must implement Poll(), which accepts bot
// pointer and subscription channel and start polling
// synchronously straight away.
type Poller interface {
	// Poll is supposed to take the bot object
	// subscription channel and start polling
	// for Updates immediately.
	//
	// Poller must listen for stop constantly and close
	// it as soon as it's done polling.
	Poll(b *Bot, updates chan Update, stop chan struct{})
}

Telegram Bot API supports long polling and webhook integration. Poller means you can plug telebot into whatever existing bot infrastructure (load balancers?) you need, if you need to. Another great thing about pollers is that you can chain them, making some sort of middleware:

poller := &tb.LongPoller{Timeout: 15 * time.Second}
spamProtected := tb.NewMiddlewarePoller(poller, func(upd *tb.Update) bool {
	if upd.Message == nil {
		return true
	}

	if strings.Contains(upd.Message.Text, "spam") {
		return false
	}

	return true
})

bot, _ := tb.NewBot(tb.Settings{
	// ...
	Poller: spamProtected,
})

// graceful shutdown
time.AfterFunc(N * time.Second, b.Stop)

// blocks until shutdown
bot.Start()

fmt.Println(poller.LastUpdateID) // 134237

Commands

When handling commands, Telebot supports both direct (/command) and group-like syntax (/command@botname) and will never deliver messages addressed to some other bot, even if privacy mode is off. For simplified deep-linking, telebot also extracts payload:

// Command: /start <PAYLOAD>
b.Handle("/start", func(m *tb.Message) {
	if !m.Private() {
		return
	}

	fmt.Println(m.Payload) // <PAYLOAD>
})

Files

Telegram allows files up to 20 MB in size.

Telebot allows to both upload (from disk / by URL) and download (from Telegram) and files in bot's scope. Also, sending any kind of media with a File created from disk will upload the file to Telegram automatically:

a := &tb.Audio{File: tb.FromDisk("file.ogg")}

fmt.Println(a.OnDisk()) // true
fmt.Println(a.InCloud()) // false

// Will upload the file from disk and send it to recipient
bot.Send(recipient, a)

// Next time you'll be sending this very *Audio, Telebot won't
// re-upload the same file but rather utilize its Telegram FileID
bot.Send(otherRecipient, a)

fmt.Println(a.OnDisk()) // true
fmt.Println(a.InCloud()) // true
fmt.Println(a.FileID) // <telegram file id: ABC-DEF1234ghIkl-zyx57W2v1u123ew11>

You might want to save certain Files in order to avoid re-uploading. Feel free to marshal them into whatever format, File only contain public fields, so no data will ever be lost.

Sendable

Send is undoubtedly the most important method in Telebot. Send() accepts a Recipient (could be user, group or a channel) and a Sendable. Other types other than the telebot-provided media types (Photo, Audio, Video, etc.) are Sendable. If you create composite types of your own, and they satisfy the Sendable interface, Telebot will be able to send them out.

// Sendable is any object that can send itself.
//
// This is pretty cool, since it lets bots implement
// custom Sendables for complex kinds of media or
// chat objects spanning across multiple messages.
type Sendable interface {
	Send(*Bot, Recipient, *SendOptions) (*Message, error)
}

The only type at the time that doesn't fit Send() is Album and there is a reason for that. Albums were added not so long ago, so they are slightly quirky for backwards compatibilities sake. In fact, an Album can be sent, but never received. Instead, Telegram returns a []Message, one for each media object in the album:

p := &tb.Photo{File: tb.FromDisk("chicken.jpg")}
v := &tb.Video{File: tb.FromURL("http://video.mp4")}

msgs, err := b.SendAlbum(user, tb.Album{p, v})

Send options

Send options are objects and flags you can pass to Send(), Edit() and friends as optional arguments (following the recipient and the text/media). The most important one is called SendOptions, it lets you control all the properties of the message supported by Telegram. The only drawback is that it's rather inconvenient to use at times, so Send() supports multiple shorthands:

// regular send options
b.Send(user, "text", &tb.SendOptions{
	// ...
})

// ReplyMarkup is a part of SendOptions,
// but often it's the only option you need
b.Send(user, "text", &tb.ReplyMarkup{
	// ...
})

// flags: no notification && no web link preview
b.Send(user, "text", tb.Silent, tb.NoPreview)

Full list of supported option-flags you can find here.

Editable

If you want to edit some existing message, you don't really need to store the original *Message object. In fact, upon edit, Telegram only requires chat_id and message_id. So you don't really need the Message as the whole. Also you might want to store references to certain messages in the database, so I thought it made sense for any Go struct to be editable as a Telegram message, to implement Editable:

// Editable is an interface for all objects that
// provide "message signature", a pair of 32-bit
// message ID and 64-bit chat ID, both required
// for edit operations.
//
// Use case: DB model struct for messages to-be
// edited with, say two columns: msg_id,chat_id
// could easily implement MessageSig() making
// instances of stored messages editable.
type Editable interface {
	// MessageSig is a "message signature".
	//
	// For inline messages, return chatID = 0.
	MessageSig() (messageID int, chatID int64)
}

For example, Message type is Editable. Here is the implementation of StoredMessage type, provided by telebot:

// StoredMessage is an example struct suitable for being
// stored in the database as-is or being embedded into
// a larger struct, which is often the case (you might
// want to store some metadata alongside, or might not.)
type StoredMessage struct {
	MessageID int   `sql:"message_id" json:"message_id"`
	ChatID    int64 `sql:"chat_id" json:"chat_id"`
}

func (x StoredMessage) MessageSig() (int, int64) {
	return x.MessageID, x.ChatID
}

Why bother at all? Well, it allows you to do things like this:

// just two integer columns in the database
var msgs []tb.StoredMessage
db.Find(&msgs) // gorm syntax

for _, msg := range msgs {
	bot.Edit(&msg, "Updated text")
	// or
	bot.Delete(&msg)
}

I find it incredibly neat. Worth noting, at this point of time there exists another method in the Edit family, EditCaption() which is of a pretty rare use, so I didn't bother including it to Edit(), just like I did with SendAlbum() as it would inevitably lead to unnecessary complications.

var m *Message

// change caption of a photo, audio, etc.
bot.EditCaption(m, "new caption")

Keyboards

Telebot supports both kinds of keyboards Telegram provides: reply and inline keyboards. Any button can also act as an endpoints for Handle().

In v2.2 we're introducing a little more convenient way in building keyboards. The main goal is to avoid a lot of boilerplate and to make code clearer.

func main() {
	b, _ := tb.NewBot(tb.Settings{...})

	var (
		// Universal markup builders.
		menu     = &ReplyMarkup{ResizeReplyKeyboard: true}
		selector = &ReplyMarkup{}

		// Reply buttons.
		btnHelp     = menu.Text("ℹ Help")
		btnSettings = menu.Text("⚙ Settings")

		// Inline buttons.
		//
		// Pressing it will cause the client to
		// send the bot a callback.
		//
		// Make sure Unique stays unique as per button kind,
		// as it has to be for callback routing to work.
		//
		btnPrev = selector.Data("⬅", "prev", ...)
		btnNext = selector.Data("➡", "next", ...)
	)

	menu.Reply(
		menu.Row(btnHelp),
		menu.Row(btnSettings),
	)
	selector.Inline(
		selector.Row(btnPrev, btnNext),
	)

	// Command: /start <PAYLOAD>
	b.Handle("/start", func(m *tb.Message) {
		if !m.Private() {
			return
		}

		b.Send(m.Sender, "Hello!", menu)
	})

	// On reply button pressed (message)
	b.Handle(&btnHelp, func(m *tb.Message) {...})

	// On inline button pressed (callback)
	b.Handle(&btnPrev, func(c *tb.Callback) {
		// ...
		// Always respond!
		b.Respond(c, &tb.CallbackResponse{...})
	})

	b.Start()
}

You can use markup constructor for every type of possible buttons:

r := &ReplyMarkup{}

// Reply buttons:
r.Text("Hello!")
r.Contact("Send phone number")
r.Location("Send location")
r.Poll(tb.PollQuiz)

// Inline buttons:
r.Data("Show help", "help") // data is optional
r.Data("Delete item", "delete", item.ID)
r.URL("Visit", "https://google.com")
r.Query("Search", query)
r.QueryChat("Share", query)
r.Login("Login", &tb.Login{...})

Inline mode

So if you want to handle incoming inline queries you better plug the tb.OnQuery endpoint and then use the Answer() method to send a list of inline queries back. I think at the time of writing, telebot supports all of the provided result types (but not the cached ones). This is how it looks like:

b.Handle(tb.OnQuery, func(q *tb.Query) {
	urls := []string{
		"http://photo.jpg",
		"http://photo2.jpg",
	}

	results := make(tb.Results, len(urls)) // []tb.Result
	for i, url := range urls {
		result := &tb.PhotoResult{
			URL: url,

			// required for photos
			ThumbURL: url,
		}

		results[i] = result
		// needed to set a unique string ID for each result
		results[i].SetResultID(strconv.Itoa(i))
	}

	err := b.Answer(q, &tb.QueryResponse{
		Results:   results,
		CacheTime: 60, // a minute
	})

	if err != nil {
		log.Println(err)
	}
})

There's not much to talk about really. It also supports some form of authentication through deep-linking. For that, use fields SwitchPMText and SwitchPMParameter of QueryResponse.

Contributing

  1. Fork it
  2. Clone develop: git clone -b develop https://github.com/tucnak/telebot
  3. Create your feature branch: git checkout -b new-feature
  4. Make changes and add them: git add .
  5. Commit: git commit -m "Add some feature"
  6. Push: git push origin new-feature
  7. Pull request

Donate

I do coding for fun but I also try to search for interesting solutions and optimize them as much as possible. If you feel like it's a good piece of software, I wouldn't mind a tip!

Bitcoin: 1DkfrFvSRqgBnBuxv9BzAz83dqur5zrdTH

License

Telebot is distributed under MIT.

Owner
Ian P Badtrousers
I'm a poet
Ian P Badtrousers
Comments
  • Add new Hanlder on run time ( after bot has been started)

    Add new Hanlder on run time ( after bot has been started)

    Hi,

    does anybody know how can I update ( add or remove, but mostly add) a handler after the bot has been started? I tried to stop then start the bot again but, but it doesn't help.

  • Middleware

    Middleware

    Telebot currently allows global middleware via MiddlewarePoller, which is a decent way to implement spam–control, rate–limiting and whatnot. Unfortunately, it lacks capability in the sense there's insufficient granularity to handlers.

    This issue explores the idea to have middleware on per-handler basis. There's also case to be made for groups of handlers, and therefore, group middleware.

    This is what we are doing at the moment:

    bot.Handle("/start", start)
    bot.Handle("/hello", hello)
    bot.Handle("/help", help)
    bot.Handle("/action_1", action)
    bot.Handle("/action_2", action)
    bot.Handle(tele.OnPhoto, onPhoto)
    bot.Handle(tele.OnDocument, onDocument)
    

    As you can see, in order to share behaviour, start, hello and others—must manually implement some shared logic.

    //bot.Use(globalMiddleware)
    
    b := bot.Group("")
    b.Use(rateLimiter(60)) // will apply to all handlers in the pack
    b.Handle("/start", start)
    b.Handle("/hello", hello)
    b.Handle("/help", hello)
    
    action := b.Group("/action_") // inherits parent's middleware
    action.Use(adminOnly)
    action.Handle("1", actionOne)
    action.Handle("2", actionTwo)
    
    bot.Handle(tele.OnPhoto, onPhoto) // no middleware
    bot.Handle(tele.OnDocument, maxFsize(5), onDocument) // on-handle basis
    

    You can see that in the code above the nested nature of the middleware. The only question remains: what's the signature of the middleware function and how does it behave? There are handlers for everything: messages, inline queries and inline button callbacks; therefore, there must be middleware for all.

    func middlewareFn func(*Update) error
    
    // Example middleware constructor:
    func rateLimiting(limit int) middlewareFunc {
    	return func(update *Update) error {
    		// return true if message is supposed to be passed further
    	}
    }
    

    Cheers, Ian

  • about use Markdown and album both

    about use Markdown and album both

    when I use markdown and album like this: var album tb.Album album = append(album, &tb.Photo{File: tb.FromURL(image1), Caption: "test"}) album = append(album, &tb.Photo{File: tb.FromURL(image2)}) bot.SendAlbum(&tb.Chat{ID: "123456"}, album, &tb.SendOptions{ParseMode: tb.ModeMarkdown}) I don't know if this is my fault or a bug. If it is my fault, please tell me the correct usage. Anyway, thanks for your time.

  • Handle command with image

    Handle command with image

    I send message /dem Response: "Hello world!" But when send message /dem with image i don't gets response

    package main
    
    import (
    	"log"
    	"os"
    	"time"
    
    	tb "gopkg.in/tucnak/telebot.v2"
    )
    
    func main() {
    	bot, err := tb.NewBot(tb.Settings{
    		Token:  os.Getenv("TGT"),
    		Poller: &tb.LongPoller{Timeout: 10 * time.Second},
    	})
    
    	if err != nil {
    		log.Fatal(err)
    		return
    	}
    
    	bot.Handle("/dem", func(message *tb.Message) {
    		bot.Send(message.Sender, "Hello World!")
    	})
    
    	bot.Start()
    }
    

    2020-12-31_11-46

  • Channel messages is empty when there are full messages Telegram queue

    Channel messages is empty when there are full messages Telegram queue

    Hi Tucnak, I use your example to run my bot. when the traffic is risen up, I occasionally encounter no more messages are processed, even I restart the bot.

    messages := make(chan telebot.Message)
        bot.Listen(messages, 1*time.Second)
    
        for message := range messages {
            if message.Text == "/hi" {
                bot.SendMessage(message.Chat,
                    "Hello, "+message.Sender.FirstName+"!", nil)
            }
        }
    

    If I use curl command in terminal curl -X POST [api_url]/getUpdates , then I got 100 messages queuing. Is there any reason why messages channel is not able to pick up these messages.

  • ReplyButton's Action will not be called?

    ReplyButton's Action will not be called?

    the code below will not work

    replyBtn := tb.ReplyButton{
      Text: "🌕 Button #1",
      Action: func(*Callback) { // may not be called??
        fmt.Println("button clicked")
      },
    }
    
    b.Handle(&replyBtn, replyBtn.Action)
    

    It may work if the codes https://github.com/tucnak/telebot/blob/a67e593e355fd1e6cfcc864b48499bc0e9f1ce5c/options.go#L133

    is replaced with

    Action func(*Message) `json:"-"`
    

    so we may not register like this:

    b.Handle(&replyBtn, func(m *tb.Message) {
    		// on reply button pressed
    	})
    
  • V2: Moving towards better API

    V2: Moving towards better API

    I set the goal to release v2 by the end of September (see updated 2.0 milestone). As it's going to be a pretty major release, I suggest re-thinking some of the API. Our biggest competitor, telegram-bot-api, 625 stars, is still superior to Telebot in terms of API, so I believe in order to stand out we must provide additional and moreover, sensible value. Telebot has always positioned itself as the framework, while our competitors were and will remain an API wrapper.

    Here are some of the issues I'd like to address (in the order of significance).

    Memory efficiency

    Message is the fattest type in Telebot, taking as much as 1544 bytes on my system (~1.5KB). Mainly because it stores lots of optional fields by-value. This is clearly borderline stupid and uncomfortable (you can't test optionals against nil) and I can't recall why I'd ever thought it was a good idea.

    I trivially managed (https://github.com/tucnak/telebot/commit/d8b3194888f53bba616c37301d67adb8035944bb) to reduce memory usage of Message down to 504 bytes (~0.5KB), making a 67.4% decrease in memory usage, which is pretty fucking good, considering Message is the most-used object. No more hassle around optionals also.

    Use of reflection for prettier API

    We currently use no reflection at all, which is probably a good thing. That said, I think introducing some light weight interface{}-kind of reflection for "optional" parameters may be a good thing.

    SendMessage() / Send()

    // Definition
    func (b *Bot) SendMessage(r Recipient, message string, options ...interface{}) error {}
    
    // Use
    b.SendMessage(user, "message") // <-- much better, isn't it?
    b.SendMessage(user, "message", &SendOptions{})
    

    In fact, we could go further and generalize it all the way down to Send():

    // Definition
    func (b *Bot) Send(r Recipient, things ...interface{}) error {}
    
    // Use
    b.Send(user, "message")
    b.Send(user, "message", &SendOptions{})
    b.Send(user, photo)
    // Etc..
    

    I wonder whether it'll damage Telebot's performance much, we can't really tell without proper benchmarking. That said, considering there's not much high load in Telegram world, we still must end up the fastest bloke on the block by a huge margin (comparing w/ e.g. Python implementations).

    Pros:

    • Much cleaner API and shorter function names
    • We'll finally get rid of huge piles of code duplicates in bot.go

    Cons:

    • Potential performance penalties (inferace{} casting)
    • We lose some compile-time safety
    • More documentation to compensate for optional arguments!

    Sendable

    In fact, we could avoid losing some of the safety and a fair chunk of casting and still introduce a better API by introducing a Sendable interface for all the sendable objects like Photo, Audio, Sticker, etc:

    type Sendable interface {
        Send(*Bot) error
    }
    

    Each and every corresponding sendable type would implement the necessary actions (which quite differ from type to type). This could also be used as a part of a prettier Send(Recipient, ..interface{}) too.

    Message builders

    I thought about it for some time now and I believe we could benefit from some sort of builder API for sending messages, like this:

    // Use
    bot.V()
        .To(recipient)
        .Text("This is a text message")
    //  .Photo(&photo) or any other sendable
        .Markdown()
        .Keyboard(keyboard)
        .Error(handlerFunc)
        .Send()
    

    It looks so good!

    Other...

    I also thought about implementing things like a state machine (telebot users would need to specify a list of states their bot users can be in and also, specify relations between these states) and a global error handler. Unfortunately, I couldn't come up with a reasonable API for "plots" (a state machine) yet though. I usually panic on bot errors and handle them up the stack anyway, so classic if err != nil error handling is rather redundant. I'd love to do things like:

    bot.ErrorHandler = func(err error) {
        panic(err)
    }
    
    bot.Handle("/start", func(c Context) {
        bot.Send(c.Message.Sender, "Hello") // calls ErrorHandler() -> panic()
    })
    

    /cc @zoni @Ronmi @ahmdrz

    UPD: I also feel like we are ovelooking inline queries and callbacks from the API design perspective... Bot start/listen/serve is confusing also!

  • does bot.Start work?

    does bot.Start work?

    The inline example provided does not work although it does not crash. It just is silentt! Also, I cannot get bot.Start to work, as if it were in an infinite loop

  • High-level command handlers

    High-level command handlers

    Current implementation prototype is quite dumb. All it does is primitive routing:

    bot, err := telebot.NewBot(os.Getenv("TELEBOT_SECRET"))
    if err != nil {
        log.Println(err)
        return
    }
    
    bot.Handle(telebot.Default, func(_ telebot.Context) {
        // Default handler
    })
    
    bot.Handle("/fun", func(_ telebot.Context) {
        // Would get executed on /fun <whatever=0>
    })
    
    bot.Handle("/evil", func(_ telebot.Context) {
        // Would get executed on /evil <whatever=0>
    })
    
    bot.Serve()
    

    I still think that we should provide some handy API for "user interactipn scripts". E.g. abstract away from actual command handling and get along with "request-details-answer" sort of scripts.

  • Upgrade up to Bot API 6.2

    Upgrade up to Bot API 6.2

    April 16, 2022

    Bot API 6.

  • Can't get OnText handle to work

    Can't get OnText handle to work

    Hi, I'm trying to learn go lang by porting my telegram bot from C# to go, and I'm using Telebot because it seems quite easy to use.

    I could manage to get the "/hello" handle to work; after that I added the "OnText" handle because I want to check text messages for spam but, while the "/hello" handle works the OnText handle seems to never get fired. I added the bot to a group and I expect the OnText to get fired each time I write a text message.

    Here is my simple code:

    package main
    
    import (
    	"time"
    	"log"
    
    	tb "github.com/tucnak/telebot"
    )
    
    func main() {
    	log.Println("Starting the bot...")
    	b, err := tb.NewBot(tb.Settings{
    		Token:  "MY TOKEN",
    		Poller: &tb.LongPoller{Timeout: 10 * time.Second},
    	})
    
    	if err != nil {
    		log.Fatal(err)
    		return
    	}
    
    	// This doesn't get fired!!
    	b.Handle(tb.OnText, func(m *tb.Message) {
    		b.Send(m.Chat, "Got a text message")
    	})
    
    	// This works
    	b.Handle("/hello", func(m *tb.Message) {
    		options := new(tb.SendOptions)
    		options.ReplyTo = m
    		b.Send(m.Chat, "Hi "+m.Sender.FirstName+", I'm the Bot!", options)
    	})
    
    	b.Start()
    }
    
  • How can I make multiple handlers at once?

    How can I make multiple handlers at once?

    how can i make multiple handlers at once? i want to make a dialog between a user and a bot

    i want the user to be able to perform authorization in the service in stages, that is:

    Bot: Enter the username. User: username Bot: Enter the password. User: password Bot: Authorization completed

    how can i do this?

    to communicate with the user, i use a Poller:

    pref := tele.Settings{
       
    Token:   cfg.Telegram.TelegramToken,
       
    Poller:  &tele.LongPoller{Timeout: 10 * time.Second},
      
     OnError: a.OnBotError,
    }
    
    bot, err := tele.NewBot(pref)
    

    i have a handler for authorization in some service: a.bot.Handle(&btnAuth, func(c tele.Context) error { }

  • Providing data to to WebApp upon open

    Providing data to to WebApp upon open

    Is is possible to provide arbitrary data to a WebApp that is opened using either an inline button or menu button? Ideally I would like my bot to provide a full list of contacts to my WebApp when it is opened in this way. Alternatively once the WebApp is open is could request a list of contacts from the bot if that is possible.

  • how to get all photos of updates

    how to get all photos of updates

    getUpdates api return a update like follow

            {
                "update_id": 665500574,
                "message": {
                    "message_id": 6,
                    "from": {
                    },
                    "chat": {
                    },
                    "date": 1670488911,
                    "media_group_id": "133639**294744053",
                    "photo": [
                        {
                            "file_id": "****",
                            "file_unique_id": "AQAD57IxG1-1kVR4",
                            "file_size": 1156,
                            "width": 90,
                            "height": 86
                        },
                        {
                            "file_id": "****",
                            "file_unique_id": "AQAD57IxG1-1kVRy",
                            "file_size": 2274,
                            "width": 117,
                            "height": 112
                        }
                    ],
                    "caption": "foo bar"
                }
            }
    

    but telebot.Context.Message().Photo got only one photo, is there hava any method to get all photos?

  • Add support for ApproveJoinRequest method errors

    Add support for ApproveJoinRequest method errors

    I've been creating a bot to accept join requests for high request rate channels of mine.

    These were the errors that I wished to handle but I didn't find them at errors.go so I added them.

Related tags
Dlercloud-telegram-bot - A Telegram bot for managing your Dler Cloud account

Dler Cloud Telegram Bot A Telegram bot for managing your Dler Cloud account. Usa

Dec 30, 2021
Pro-bot - A telegram bot to play around with the community telegram channels

pro-bot ?? Pro Bot A Telegram Bot to Play Around With The Community Telegram Cha

Jan 24, 2022
A bot based on Telegram Bot API written in Golang allows users to download public Instagram photos, videos, and albums without receiving the user's credentials.

InstagramRobot InstagramRobot is a bot based on Telegram Bot API written in Golang that allows users to download public Instagram photos, videos, and

Dec 16, 2021
Bot - Telegram Music Bot in Go

Telegram Music Bot in Go An example bot using gotgcalls. Setup Install the serve

Jun 28, 2022
Telegram Bot Framework for Go

Margelet Telegram Bot Framework for Go is based on telegram-bot-api It uses Redis to store it's states, configs and so on. Any low-level interactions

Dec 22, 2022
Parr(B)ot is a Telegram bot framework based on top of Echotron

Parr(B)ot framework A just born Telegram bot framework in Go based on top of the echotron library. You can call it Parrot, Parr-Bot, Parrot Bot, is up

Aug 22, 2022
Bot-template - A simple bot template for creating a bot which includes a config, postgresql database

bot-template This is a simple bot template for creating a bot which includes a c

Sep 9, 2022
The serverless OTP telegram service use telegram as OTP service, and send OTP through webhook

Setup OTP First thing, you need prepare API(webhook) with POST method, the payload format as below { "first_name": "Nolan", "last_name": "Nguyen",

Jul 24, 2022
IRC, Slack, Telegram and RocketChat bot written in go
IRC, Slack, Telegram and RocketChat bot written in go

go-bot IRC, Slack & Telegram bot written in Go using go-ircevent for IRC connectivity, nlopes/slack for Slack and Syfaro/telegram-bot-api for Telegram

Dec 20, 2022
Golang telegram bot API wrapper, session-based router and middleware

go-tgbot Pure Golang telegram bot API wrapper generated from swagger definition, session-based routing and middlewares. Usage benefits No need to lear

Nov 16, 2022
Client lib for Telegram bot api

Micha Client lib for Telegram bot api. Supports Bot API v2.3.1 (of 4th Dec 2016). Simple echo bot example: package main import ( "log" "git

Nov 10, 2022
Go library for Telegram Bot API
Go library for Telegram Bot API

tbot - Telegram Bot Server Features Full Telegram Bot API 4.7 support Zero dependency Type-safe API client with functional options Capture messages by

Nov 30, 2022
Golang bindings for the Telegram Bot API

Golang bindings for the Telegram Bot API All methods are fairly self explanatory, and reading the godoc page should explain everything. If something i

Jan 6, 2023
Golang Based Account Generator Telegram Bot

Account Generator Bot Account Generator Bot, written in GoLang via gotgbot library. Variables Env Vars - BOT_TOKEN - Get it from @BotFather CHANNEL_ID

Nov 21, 2022
Bot that polls activity API for Github organisation and pushes updates to Telegram.

git-telegram-bot Telegram bot for notifying org events Requirements (for building) Go version 1.16.x Setup If you don't have a telegram bot token yet,

Apr 8, 2022
📱 Hentai bot for Telegram 📱
📱 Hentai bot for Telegram 📱

Random-Good-Hanime Hentai Telegram bot for educational purpose ?? Features ?? Random hentai Lot of different categories ?? Real time logs ?? Config fi

Nov 25, 2022
A telegram bot that fetches multiple RSS cryptocurrency news feeds for sentiment analysis

Crypto News Telegram Bot A simple telegram bot that will help you stay updated on your latest crypto news This bot will help you keep track of the lat

Aug 22, 2021
A Telegram bot that will run code for you.

piston_bot A Telegram bot that will run code for you. Made using piston. Available as @iruncode_bot on telegram. Examples Basic example Input: /run py

Sep 11, 2022
Telegram bot to get information on vaccine availabilities.

?? berlin-vaccine-alert Telegram bot to get information on vaccine availabilities. Get the latest appointments directly on telegram. The bot listen to

Jun 23, 2022