4.9 KiB
Golang bindings for the Telegram Bot API
All methods have been added, and all features should be available. If you want a feature that hasn't been added yet or something is broken, open an issue and I'll see what I can do.
All methods are fairly self explanatory, and reading the godoc page should explain everything. If something isn't clear, open an issue or submit a pull request.
The scope of this project is just to provide a wrapper around the API without any additional features. There are other projects for creating something with plugins and command handlers without having to design all that yourself.
Use github.com/go-telegram-bot-api/telegram-bot-api
for the latest
version, or use gopkg.in/telegram-bot-api.v4
for the stable build.
Join the development group if you want to ask questions or discuss development.
Example
This is a very simple bot that just displays any gotten updates, then replies it to that chat.
package main
import (
"log"
"gopkg.in/telegram-bot-api.v4"
)
func main() {
bot, err := tgbotapi.NewBotAPI("MyAwesomeBotToken")
if err != nil {
log.Panic(err)
}
bot.Debug = true
log.Printf("Authorized on account %s", bot.Self.UserName)
u := tgbotapi.NewUpdate(0)
u.Timeout = 60
updates, err := bot.GetUpdatesChan(u)
for update := range updates {
if update.Message == nil {
continue
}
log.Printf("[%s] %s", update.Message.From.UserName, update.Message.Text)
msg := tgbotapi.NewMessage(update.Message.Chat.ID, update.Message.Text)
msg.ReplyToMessageID = update.Message.MessageID
bot.Send(msg)
}
}
If you need to use webhooks (if you wish to run on Google App Engine), you may use a slightly different method.
package main
import (
"gopkg.in/telegram-bot-api.v4"
"log"
"net/http"
)
func main() {
bot, err := tgbotapi.NewBotAPI("MyAwesomeBotToken")
if err != nil {
log.Fatal(err)
}
bot.Debug = true
log.Printf("Authorized on account %s", bot.Self.UserName)
_, err = bot.SetWebhook(tgbotapi.NewWebhookWithCert("https://www.google.com:8443/"+bot.Token, "cert.pem"))
if err != nil {
log.Fatal(err)
}
info, err := bot.GetWebhookInfo()
if err != nil {
log.Fatal(err)
}
if info.LastErrorDate != 0 {
log.Printf("[Telegram callback failed]%s", info.LastErrorMessage)
}
updates := bot.ListenForWebhook("/" + bot.Token)
go http.ListenAndServeTLS("0.0.0.0:8443", "cert.pem", "key.pem", nil)
for update := range updates {
log.Printf("%+v\n", update)
}
}
If you need to use InlineKeyboards and respond to the CallbackQuery that is generated when the user selects a presented keyboard button.
Example courtisy of Telegram user @trigun117
(Vadim) in the Golang Telegram Bot API chat.
package main
import (
"gopkg.in/telegram-bot-api.v4"
"log"
)
// return tgbotapi.InlineKeyboardMarkup
func createMarkup(btns ...string) tgbotapi.InlineKeyboardMarkup {
row := tgbotapi.NewInlineKeyboardRow()
for _, btn := range btns {
inlineBtn := tgbotapi.NewInlineKeyboardButtonData(btn, btn)
row = append(row, inlineBtn)
}
return tgbotapi.NewInlineKeyboardMarkup(row)
}
func main() {
bot, err := tgbotapi.NewBotAPI("Token")
if err != nil {
log.Fatal(err)
}
config := tgbotapi.NewUpdate(0)
updates, _ := bot.GetUpdatesChan(config)
for update := range updates {
if update.Message != nil && update.Message.Command() == "start" {
msg := tgbotapi.NewMessage(update.Message.Chat.ID, "hello")
mkp := tgbotapi.NewInlineKeyboardMarkup(
tgbotapi.NewInlineKeyboardRow(
tgbotapi.NewInlineKeyboardButtonData("1", "1"),
tgbotapi.NewInlineKeyboardButtonData("2", "2")))
msg.ReplyMarkup = mkp
bot.Send(msg)
} else if update.CallbackQuery != nil {
chatID := int64(update.CallbackQuery.From.ID)
msgID := update.CallbackQuery.Message.MessageID
// You can edit text, markup or both
// Edit text
editText := tgbotapi.NewEditMessageText(chatID, msgID, "Got data " + update.CallbackQuery.Data)
bot.Send(editText)
// Edit Markup
editMarkUp := tgbotapi.NewEditMessageReplyMarkup(chatID, msgID, createMarkup("1", "2", "3"))
bot.Send(editMarkUp)
}
}
}
If you need, you may generate a self signed certficate, as this requires HTTPS / TLS. The above example tells Telegram that this is your certificate and that it should be trusted, even though it is not properly signed.
openssl req -x509 -newkey rsa:2048 -keyout key.pem -out cert.pem -days 3560 -subj "//O=Org\CN=Test" -nodes
Now that Let's Encrypt has entered public beta, you may wish to generate your free TLS certificate there.