KiteGrams Bot API

Официальная документация HTTP Bot API сервера KiteGrams

HTTP Bot API: supported methods

This document lists every Bot API method that the telesrv HTTP gateway (internal/botapi, default port 8081) actually implements, together with the parameters it accepts, the extensions it adds, and the official methods it deliberately does not support.

Russian version of this document: bot-api.ru.md.

How to use this document

Transport

ItemValue
Method endpointhttp(s)://<host>/bot<TOKEN>/<METHOD>
File downloadhttp(s)://<host>/file/bot<TOKEN>/<file_path>
Listener settingTELESRV_BOT_API_ADDR; an empty value disables the gateway
Public address shown by BotFatherTELESRV_BOT_API_PUBLIC_URL; empty shows none
Request body limit25 MiB upload + 1 MiB overhead (FILE_TOO_BIG)
Accepted content typesapplication/json, multipart/form-data, application/x-www-form-urlencoded

<METHOD> is matched case-insensitively. Both GET and POST reach the dispatcher, so urlencoded GET requests work.

Client configuration:

--base-file-url http://host:8081/file/bot.

"http://host:8081/bot" }))`.

Authentication

The path token must be the bot's <bot_id>:<secret> pair and its secret must match the value stored for that bot. Anything else returns HTTP 401 with ACCESS_TOKEN_INVALID. There is no separate auth header; the token in the URL is the credential, exactly like the official gateway.

File downloads (/file/bot...) are authenticated the same way.

Request and response conventions

Success:


{"ok": true, "result": {}}

Failure:


{"ok": false, "error_code": 400, "description": "CHAT_ID_INVALID"}

error_code is the HTTP status code. description is an upper-case SCREAMING_SNAKE error marker, not always the official Telegram wording — match on the marker, not on the whole string.

Field decoding is generic: JSON bodies are flattened to strings, non-string JSON values are re-marshalled to their JSON form, and multipart uses the first value of each field. This is why several methods accept both the message_text shorthand and the full InputTextMessageContent object, and why setChatMenuButton accepts both a nested menu_button object and a flat body carrying type.

Errors

Markers the gateway can return directly:

MarkerHTTPNotes
ACCESS_TOKEN_INVALID401bad or unknown token
METHOD_NOT_FOUND404 / 501unknown method, or the feature is not wired in this deployment
BAD_REQUEST400unclassified failure
CHAT_ID_INVALID400chat_id missing, zero, or unparsable
MESSAGE_ID_INVALID400message_id missing or <= 0
MESSAGE_IDENTIFIER_INVALID400inline_message_id mixed with chat_id/message_id
MESSAGE_EMPTY400no text given
MESSAGE_TOO_LONG400over the text limit
MESSAGE_NOT_MODIFIED400edit that changes nothing
REPLY_PARAMETERS_INVALID400conflicting reply selectors
REPLY_MESSAGE_ID_INVALID400negative or malformed reply target
MESSAGE_THREAD_ID_INVALID400ephemeral top-message id out of range
ENTITY_INVALID, ENTITY_BOUNDS_INVALID, ENTITY_TYPE_UNSUPPORTED, ENTITIES_TOO_LONG400entity list problems
FILE_ID_INVALID, FILE_TOO_BIG, MEDIA_INVALID400file/media problems
BUTTON_INVALID, BUTTON_TYPE_INVALID, BUTTON_DATA_INVALID, BUTTON_URL_INVALID400markup problems
RICH_MESSAGE_INVALID, RICH_MESSAGE_TOO_LONG, RICH_MESSAGE_DATE_INVALID, RICH_MESSAGE_BLOCKS_UNSUPPORTED, RICH_MESSAGE_MEDIA_UNSUPPORTED, RICH_MESSAGE_OPTION_UNSUPPORTED400rich message problems
WEBPAGE_MEDIA_EMPTY400rich HTML referenced remote media the local blob backend cannot materialize
EFFECT_ID_INVALID, VALUE_INVALID400bad numeric parameter
BOT_COMMAND_INVALID400malformed or oversized commands
BOT_COMMAND_SCOPE_UNSUPPORTED400non-default scope, or any language_code
EPHEMERAL_MESSAGE_ID_INVALID, EPHEMERAL_TARGET_REQUIRED, EPHEMERAL_ACTION_EXPIRED400ephemeral addressing problems
QUERY_ID_INVALID, USER_ID_INVALID, RESULT_ID_INVALID, RESULT_ID_EMPTY, RESULT_TYPE_INVALID400query/user/result problems
OFFSET_INVALID400getUpdates offset below -10000
ALLOWED_UPDATES_INVALID400not a JSON array of up to 100 strings
ALLOWED_UPDATES_UNSUPPORTED501gateway without the update-control service
MAX_CONNECTIONS_INVALID400outside 1..100
SECRET_TOKEN_INVALID400characters outside [A-Za-z0-9_-], or longer than 256
WEBHOOK_URL_INVALID400not an absolute http(s) URL, longer than 2048, has userinfo/fragment, or a port outside 1..65535
CERTIFICATE_PINNING_UNSUPPORTED400certificate / uploaded certificate supplied
IP_ADDRESS_UNSUPPORTED400ip_address supplied
WEBHOOK_UNSUPPORTED501gateway without the webhook service
METHOD_NOT_FOUND501answerShippingQuery
BLOCKED_USER_EMOJI_STATUS_SERVICE_MISSING, BLOCKED_WEBAPP_QUERY_SERVICE_MISSING, BLOCKED_PREPARED_INLINE_SERVICE_MISSING501optional service not wired
USER_PERMISSION_DENIED403emoji status without the required user grant
PREMIUM_ACCOUNT_REQUIRED400emoji status without Premium
PREMIUM_GIFT_SELF_INVALID, PREMIUM_GIFT_CODE_INVALID, BALANCE_TOO_LOW, STAR_COUNT_INVALID, MONTH_COUNT_INVALID400premium gift problems
IDEMPOTENCY_KEY_INVALID400conflicting request_id/Idempotency-Key, or bad charset/length
PAYMENT_FORM_INVALID400payment form rejected
CHAT_WRITE_FORBIDDEN, CHAT_ADMIN_REQUIRED400rights missing
USER_BOT_REQUIRED400target is not a bot user
CONFLICT: ...409concurrent poll or webhook delivery
INTERNAL_SERVER_ERROR500 / 503store or transport failure

Method summary

Implemented (40 methods + 1 file route):

GroupMethods
Bot & commandsgetMe, setMyCommands, deleteMyCommands, getMyCommands
UpdatesgetUpdates
TextsendMessage, sendRichMessage
MediasendPhoto, sendAnimation, sendAudio, sendDocument, sendLivePhoto, sendSticker, sendVideo, sendVideoNote, sendVoice
LocationsendContact, sendLocation, sendVenue
Edit/deleteeditMessageText, editMessageCaption, editMessageReplyMarkup, deleteMessage
Chat actionssendChatAction
Ephemeral edit/deleteeditEphemeralMessageText, editEphemeralMessageMedia, editEphemeralMessageCaption, editEphemeralMessageReplyMarkup, deleteEphemeralMessage
CallbackanswerCallbackQuery
FilesgetFile, GET /file/bot<TOKEN>/<file_path>
WebhookssetWebhook, deleteWebhook, getWebhookInfo
Menus & statussetChatMenuButton, getChatMenuButton, setUserEmojiStatus
Web apps & inlineanswerWebAppQuery, savePreparedInlineMessage
PaymentsgiftPremiumSubscription
Blocked by designanswerShippingQuery (HTTP 501)

Updates

Only three update kinds are produced:

allowed_updates valueUpdate key
messagemessage
edited_messageedited_message
callback_querycallback_query

allowed_updates is a JSON array of up to 100 strings; unknown names parse successfully but never match anything, so do not rely on filtering to hide updates — drop the fields in the bot. The setting is accepted both by getUpdates and by setWebhook, and it persists per bot.

Ephemeral (Bot API 10.2) messages arrive as normal message updates, but their message_id belongs to the ephemeral namespace rather than the chat's message numbering, so ordinary reply_to_message_id will not address them. Replies go back through reply_parameters.ephemeral_message_id; see Methods: ephemeral messages.

Queue retention is controlled by TELESRV_BOT_API_UPDATE_RETENTION (default 24h); acknowledged updates are dropped earlier.

Methods: bot identity and commands

getMe

No parameters. Returns the bot's own User object.

setMyCommands

ParameterTypeNotes
commandsJSON arrayup to 100 entries of {command, description, is_ephemeral}
scopeobjectonly {"type":"default"} is accepted
language_codestringmust be empty

is_ephemeral=true marks the command as an ephemeral one: invoking it in a group produces a message only the caller can see, and the bot must answer inside the ephemeral action window. Returns true.

deleteMyCommands

Same scope rules as setMyCommands; clears the list. Returns true.

getMyCommands

Same scope rules. Returns the stored array; entries include is_ephemeral: true only when the flag is set.

Methods: sending

sendMessage

ParameterTypeNotes
chat_idintegerrequired, non-zero; negative for groups/channels
textstringrequired, up to 4096 characters after formatting
parse_modestringHTML, Markdown, MarkdownV2, or omitted for plain text
entitiesJSON arrayused when parse_mode is absent; ignored otherwise
reply_markupobjectany of the four constructors, see Markup
disable_web_page_previewboolean
disable_notificationboolean
reply_to_message_idinteger
receiver_user_idintegertelesrv extension: switches the call to an ephemeral send
callback_query_idintegerephemeral send anchored to a callback query
reply_parametersobject{ephemeral_message_id} for ephemeral replies, {message_id} for ordinary ones
message_thread_idintegerephemeral: the top message id of the discussion group

Ordinary and ephemeral addressing are mutually exclusive: with receiver_user_id set, reply_to_message_id must stay unset and reply_parameters may only carry ephemeral_message_id. Ephemeral sends accept inline keyboards only (BUTTON_TYPE_INVALID otherwise). The result is the same Message shape, with the ephemeral id in message_id.

sendPhoto, sendAnimation, sendAudio, sendDocument, sendSticker, sendVideo, sendVideoNote, sendVoice

All share one handler.

ParameterTypeNotes
chat_idintegerrequired
<kind>string / filethe method's own field: photo, animation, audio, document, sticker, video, video_note, voice
captionstringup to 1024 characters
parse_mode, caption_entitiesas in sendMessage
reply_markupobjectall four constructors
disable_notification, reply_to_message_id
width, height, duration, title, performerinteger / stringaccepted and forwarded as metadata hints
emojistringsticker only
receiver_user_id, callback_query_id, reply_parameters, message_thread_idsame ephemeral extension as sendMessage

The file field accepts, in this order of precedence:

1. attach://<field> referencing a multipart file part; 2. an uploaded multipart part with the same field name; 3. an http:// or https:// URL (the server fetches it); 4. a file_id previously returned by getFile.

Anything else is FILE_ID_INVALID.

sendLivePhoto

Two media fields: photo (still frame) and live_photo (the video part). Both accept upload, attach://, or file_id. The video part cannot be an HTTP URL — that is FILE_ID_INVALID, matching the official restriction. Captions, parse_mode, and the ephemeral extension work as for the other media methods.

sendContact, sendLocation, sendVenue

These three are ephemeral-only: they require receiver_user_id (or a callback_query_id) and otherwise fail with EPHEMERAL_TARGET_REQUIRED.

sendContact takes chat_id, phone_number, first_name, optional last_name, and vcard (up to 2048 bytes), plus an optional inline reply_markup.

sendLocation takes chat_id, latitude (-90..90), longitude (-180..180), horizontal_accuracy (0..1500, default 0). A non-zero live_period is rejected with MEDIA_INVALID — live location is not implemented.

sendVenue adds required title and address, and accepts either foursquare_id + foursquare_type or google_place_id + google_place_type.

Methods: rich messages

sendRichMessage

Telesrv extension, Layer 228 rich text. Sends InputRichMessage instead of a plain formatted string, so tables, headings, dividers, details blocks and footers reach the client as real rich blocks.

ParameterTypeNotes
chat_idintegerrequired
rich_messageobject{"html": "..."} or {"markdown": "..."}, plus optional is_rtl and skip_entity_detection
reply_markupobjectinline keyboards only
reply_parametersobject{"message_id": N}; the legacy reply_to_message_id is also accepted, but not both
disable_notification, protect_contentboolean
message_effect_idintegermessage effect id

Rules and rejections:

RICH_MESSAGE_INVALID;

direct_messages_topic_id, allow_paid_broadcast, and suggested_post_parameters are rejected with an explicit error instead of being silently ignored;

tg-collage, tg-slideshow) fails with WEBPAGE_MEDIA_EMPTY, because the local blob backend cannot materialize an arbitrary URL atomically. The documented workaround (see cmd/bots/bedolagaformat) is to retry once with the logo removed rather than degrade to a classic menu.

Supported HTML elements: b/strong, i/em, u/ins, s/strike/del, tg-spoiler, span (only as <span class="tg-spoiler">), a, code, pre (with class="language-…"), blockquote, tg-emoji, tg-time, footer, and table (with the bordered and striped attributes, per-cell alignment). tg-time requires unix in 1..2^31-1 and a format built from t, T, d, D, w/W, or exactly r/R for a relative timestamp.

Markdown input is parsed by the same rich builder used on the MTProto side, so #-style headings, --- dividers, pipe tables, > quotes, fenced code and footer blocks all work.

editMessageText accepts the same rich_message object, and there is no separate editMessageRichMessage method.

Methods: ephemeral messages

Ephemeral messages (Bot API 10.2) are visible only to their receiver, who sees a "only visible to you" notice. telesrv supports the whole lifecycle.

Sending is done through the ordinary methods with receiver_user_id:

Addressing rules:

from the query);

message, and cannot be combined with callback_query_id;

combined with a receiver;

EPHEMERAL_ACTION_EXPIRED.

Editing and deleting:

MethodParameters
editEphemeralMessageTextchat_id, receiver_user_id, ephemeral_message_id, text, parse_mode, entities, reply_markup
editEphemeralMessageCaptionsame, with caption + caption_entities
editEphemeralMessageMediasame, plus media (see below)
editEphemeralMessageReplyMarkupsame, plus reply_markup only
deleteEphemeralMessagechat_id, receiver_user_id, ephemeral_message_id

media is an InputMedia-like object: type (one of photo, animation, audio, document, video, live_photo), the file field, and optional caption, parse_mode, caption_entities, width, height, duration, title, performer. live_photo uses photo for the still and media for the video. Raw uploads are not allowed here — only file_id, attach://-free file references, or HTTPS URLs (FILE_ID_INVALID otherwise).

reply_markup is inline-only, and its presence matters: sending reply_markup with an empty value clears the keyboard.

Methods: editing and deleting

editMessageText

The main edit method. It covers both ordinary and rich text edits, and both chat messages and inline messages.

ParameterTypeNotes
chat_id + message_idone addressing mode
inline_message_idstringthe other mode; must not be mixed with the first
textstringone content form
rich_messageobjectthe other content form; must not be mixed with text
parse_mode, entitiesas in sendMessage
reply_markupobjectinline only; presence clears when empty
disable_web_page_previewboolean

For an inline_message_id the result is a boolean; for a chat message it is the updated Message. An edit that changes nothing returns MESSAGE_NOT_MODIFIED.

editMessageCaption

ParameterTypeNotes
chat_id + message_idrequired; inline_message_id is not supported yet (INLINE_MESSAGE_ID_UNSUPPORTED)
captionstringup to 1024 characters; omitted or empty removes the caption
parse_mode, caption_entitiesas in sendPhoto
reply_markupobjectinline only; omitted keeps the keyboard, empty clears it

Only a photo or document message (photo, video, animation, audio, voice, file) has a caption; a text message returns MESSAGE_HAS_NO_CAPTION. Returns the updated Message. Works in private chats and in channels/supergroups.

editMessageReplyMarkup

chat_id + message_id (no inline_message_id yet) and an optional inline reply_markup. Only the keyboard changes; an omitted reply_markup removes it. Returns the updated Message.

There is no editMessageMedia, editMessageLiveLocation, or stopMessageLiveLocation — use editMessageText (or the ephemeral variants) instead.

sendChatAction

ParameterTypeNotes
chat_idintegera private chat, or a channel/supergroup where the bot is a member
actionstringtyping, upload_photo, record_video, upload_video, record_voice, upload_voice, upload_document, choose_sticker, find_location, record_video_note, upload_video_note
message_thread_idintegerforum topic, optional

Returns true. The status is transient, like MTProto messages.setTyping: nothing is stored. business_connection_id is not supported.

deleteMessage

chat_id + message_id. Returns true. Deleting an already-deleted or foreign message returns false or an error, as with the official gateway.

answerCallbackQuery

ParameterTypeNotes
callback_query_idstringrequired
textstringnotification text
urlstring
show_alertbooleanmodal instead of toast
cache_timeintegerseconds

Returns true.

Methods: files

getFile

file_id must be a telesrv-issued id. The result always has file_unique_id == file_id and file_path == file_id, so the download URL is /file/bot<TOKEN>/<file_id>. Foreign or unknown ids are FILE_ID_INVALID.

GET /file/bot<TOKEN>/<file_path>

Streams the file, chunk by chunk, with the stored MIME type and Content-Length. The path is the file_id; a path with extra segments is 404 FILE_NOT_FOUND.

Methods: webhooks

setWebhook

ParameterTypeNotes
urlstringempty value deletes the webhook instead
secret_tokenstring[A-Za-z0-9_-], up to 256 characters
max_connectionsinteger1..100, default 40
allowed_updatesJSON arraysee Updates
drop_pending_updatesboolean

certificate (and any uploaded certificate part) is rejected with CERTIFICATE_PINNING_UNSUPPORTED; use a publicly trusted certificate. ip_address is rejected with IP_ADDRESS_UNSUPPORTED — the gateway uses the DNS address list. Before each connection, every resolved IP must be public; loopback, private, link-local and reserved addresses are blocked. Connections use the validated numeric IP, and HTTP proxy environment variables are ignored. For trusted self-hosted bots that need internal destinations, explicitly set TELESRV_BOT_API_WEBHOOK_ALLOW_PRIVATE_NETWORKS=true. This grants every bot access to the server's internal network; leave it disabled on multi-user servers. Blocked delivery is reported through getWebhookInfo and retried normally.

Setting a webhook while getUpdates is long-polling returns 409 CONFLICT. While a delivery is in flight, setWebhook waits up to 20 seconds for it to finish and returns 409 CONFLICT only if the delivery is still running.

Delivery behaviour:

(not an array like getUpdates returns);

concurrent HTTP requests overall;

small per-bot jitter;

getWebhookInfo

Returns url, has_custom_certificate (always false here), pending_update_count, and — when a webhook is configured — max_connections, allowed_updates, last_error_date, last_error_message.

deleteWebhook

drop_pending_updates is optional. Like setWebhook, it waits up to 20 seconds for an in-flight delivery and returns 409 only if that delivery is still running.

Methods: menus, emoji status, web apps

setChatMenuButton / getChatMenuButton

menu_button is {"type": "default"}, {"type": "commands"}, or {"type": "web_app", "text": "...", "web_app": {"url": "..."}}. A flat body that carries type at the top level is also accepted, which keeps older library serializers working. Setting returns true; getting returns the current button (never null — an unset button reads as {"type": "default"}).

setUserEmojiStatus

user_id, emoji_status_custom_emoji_id, emoji_status_expiration_date. Requires the user to have granted the bot permission to set their status (otherwise 403 USER_PERMISSION_DENIED) and to be a Premium user (PREMIUM_ACCOUNT_REQUIRED). Returns true.

answerWebAppQuery

web_app_query_id plus result. Only InlineQueryResult of type article is supported: id (up to 64 characters), title, description, url (HTTPS only), input_message_content (or the message_text shorthand), reply_markup (inline only). Other result types are RESULT_TYPE_INVALID. The response contains inline_message_id when the answer produced one.

savePreparedInlineMessage

user_id, result (same article restriction), and the peer filters allow_user_chats, allow_bot_chats, allow_group_chats, allow_channel_chats. Returns {id, expiration_date}.

Methods: payments

giftPremiumSubscription

Pays for a Premium gift out of the bot's Stars balance, through the same durable Stars pipeline as MTProto payments.sendStarsForm.

ParameterTypeNotes
user_idintegerrecipient; self-gifts are rejected
month_countinteger1..120
star_countintegerpositive, at most 10^15
textstringup to 128 characters
text_parse_mode, text_entitiesrestricted entity set
request_idstringtelesrv extension for idempotency

Send an Idempotency-Key HTTP header (or the local request_id field) — the allowed charset is [A-Za-z0-9] plus -, _, ., : up to 128 characters. Replaying the same key with the same request returns the stored result; replaying it with a different recipient, plan, price, or text is IDEMPOTENCY_KEY_INVALID. Requests without any key still work, but each retry charges again, so always send a key.

dropPendingUpdates

Implemented: discards the bot's unconfirmed queued updates and answers true. A bot that has fallen behind needs it, otherwise it spends forever working through a backlog while pre_checkout_query, which lives 10 seconds, quietly expires.

answerPreCheckoutQuery

Implemented. Before any Stars move, the payer waits for the bot's answer for at most 10 seconds (Telegram's requirement). The bot receives a pre_checkout_query update and answers with pre_checkout_query_id, ok and, when ok=false, an error_message.

The timeout never degrades into charging anyway: a silent bot means a refusal, otherwise pre-checkout would verify nothing. Only the bot that owns the order may answer; a stale pre_checkout_query_id gets QUERY_ID_INVALID. The currency and invoice_payload in the answer are not compared against what the bot recorded at sendInvoice, so that check stays on the bot side, same as in Telegram.

answerShippingQuery

Recognized, but answers HTTP 501 METHOD_NOT_FOUND: a Stars payment has no shipping step, so there is nothing to answer.

Markup and entities

reply_markup accepts exactly one constructor:

ConstructorNotes
inline_keyboardrows of buttons
keyboardreply keyboard; resize_keyboard, one_time_keyboard, is_persistent, input_field_placeholder, selective
remove_keyboardremove_keyboard: true, selective
force_replyforce_reply: true, input_field_placeholder, selective

Inline keyboard buttons (exactly one action per button, otherwise BUTTON_INVALID): url, callback_data (up to 64 bytes), web_app, login_url (url, bot_username, forward_text, request_write_access), switch_inline_query, switch_inline_query_current_chat, switch_inline_query_chosen_chat, copy_text. Every button also accepts text (required), style (primary / danger / success / omitted), and icon_custom_emoji_id. Unknown fields are rejected rather than ignored.

Reply keyboard buttons: a plain string, or an object with text plus one of request_contact, request_location, request_poll (type), request_users (request_id, user_is_bot, user_is_premium, max_quantity, request_name, request_username, request_photo), request_chat (request_id, chat_is_channel, chat_is_forum, chat_has_username, chat_is_created, user_administrator_rights, bot_administrator_rights, bot_is_member, request_title, request_username, request_photo), or web_app.

Message entities (for entities / caption_entities, and for the date_time entity, which takes unix_time + date_time_format):

bold, italic, underline, strikethrough, code, pre (language), text_link (url), text_mention (user.id), spoiler, blockquote, expandable_blockquote, custom_emoji (custom_emoji_id), mention, hashtag, cashtag, bot_command, url, email, phone_number, bank_card_number, date_time.

Limits: 256 entities per message (ENTITIES_TOO_LONG), offsets in UTF-16 code units, unknown types are ENTITY_TYPE_UNSUPPORTED.

Limits

LimitValue
Text length4096 characters after parsing
Caption length1024 characters
Entities per message256
Inline result id64 bytes
Callback data64 bytes
Commands per setMyCommands100
Upload size25 MiB per file
allowed_updates entries100
getUpdates limitdefault and maximum 100
getUpdates timeoutclamped to 0..50 seconds
max_connections1..100, default 40
Rich message source256 KiB
getFile offset/limitoffset ignored; size reported in full

Not implemented

Every other official method returns HTTP 404 METHOD_NOT_FOUND. The most commonly reached ones:

stopMessageLiveLocation, stopPoll, and inline_message_id for editMessageCaption / editMessageReplyMarkup;

sendPoll, sendDice, sendGame;

answerShippingQuery, getStarTransactions, refundStarPayment;

restrictChatMember, promoteChatMember, setChatPermissions, setChatPhoto, deleteChatPhoto, pinChatMessage, unpinChatMessage, unpinAllChatMessages, setChatTitle, setChatDescription, leaveChat;

getChatMemberCount, getForumTopic*, getUserChatBoosts;

copyMessages, sendPoll, getFile-adjacent helpers;

setMyDefaultAdministratorRights, deleteWebhook for other bots, close, logOut;

MTProto clients are unaffected: everything implemented for the official Android/iOS/Desktop clients is reached over MTProto, not HTTP. See docs/premium-stars.md for the shared Stars and Premium pipelines.

Demos and self-tests

PathPurpose
cmd/bots/ptbechopython-telegram-bot echo against the gateway, including an ephemeral command demo
cmd/bots/aiogramechoaiogram 3 echo, ephemeral replies, reply and inline keyboards
cmd/bots/bedolagaformatHTML / Markdown / MarkdownV2, rich menus via sendRichMessage, Telegram Login
cmd/bots/botcheckGo probe: imports the bot token over MTProto and checks the bot loop
cmd/bots/botdemoGo example: a bot sending to a channel or user on a timer
cmd/bots/grammystoreProduction grammY bot on the HTTP gateway (Postgres, own deployment)
scripts/botapi_echo_once.pySingle-shot send/receive self-test
scripts/botapi_receive_selftest.pyUpdate-queue and webhook self-test