122 lines
3.3 KiB
Markdown
122 lines
3.3 KiB
Markdown
|
# Golang bindings for the Telegram Bot API
|
||
|
|
|
||
|
|
[](http://godoc.org/github.com/go-telegram-bot-api/telegram-bot-api)
|
||
|
|
[](https://travis-ci.org/go-telegram-bot-api/telegram-bot-api)
|
||
|
|
|
||
|
|
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.
|
||
|
|
|
||
|
|
Join [the development group](https://telegram.me/go_telegram_bot_api) if
|
||
|
|
you want to ask questions or discuss development.
|
||
|
|
|
||
|
|
## Example
|
||
|
|
|
||
|
|
First, ensure the library is installed and up to date by running
|
||
|
|
`go get -u github.com/go-telegram-bot-api/telegram-bot-api`.
|
||
|
|
|
||
|
|
This is a very simple bot that just displays any gotten updates,
|
||
|
|
then replies it to that chat.
|
||
|
|
|
||
|
|
```go
|
||
|
|
package main
|
||
|
|
|
||
|
|
import (
|
||
|
|
"log"
|
||
|
|
|
||
|
|
"github.com/go-telegram-bot-api/telegram-bot-api"
|
||
|
|
)
|
||
|
|
|
||
|
|
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 { // ignore any non-Message Updates
|
||
|
|
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)
|
||
|
|
}
|
||
|
|
}
|
||
|
|
```
|
||
|
|
|
||
|
|
There are more examples on the [wiki](https://github.com/go-telegram-bot-api/telegram-bot-api/wiki)
|
||
|
|
with detailed information on how to do many differen kinds of things.
|
||
|
|
It's a great place to get started on using keyboards, commands, or other
|
||
|
|
kinds of reply markup.
|
||
|
|
|
||
|
|
If you need to use webhooks (if you wish to run on Google App Engine),
|
||
|
|
you may use a slightly different method.
|
||
|
|
|
||
|
|
```go
|
||
|
|
package main
|
||
|
|
|
||
|
|
import (
|
||
|
|
"log"
|
||
|
|
"net/http"
|
||
|
|
|
||
|
|
"github.com/go-telegram-bot-api/telegram-bot-api"
|
||
|
|
)
|
||
|
|
|
||
|
|
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, 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](https://letsencrypt.org) is available,
|
||
|
|
you may wish to generate your free TLS certificate there.
|