Botlify Feature Map: What to Use and Why
Use this map to find a working pattern before opening the full parameter reference. A helper is an API convenience, not an automatically configured bot feature. Both helper PHP and plain PHP ultimately call Telegram over HTTP.
Pick the right layer
| Layer | Responsibility | Example |
|---|---|---|
| Your application | Commands, authorization, state and business rules | Only the owner can export user data |
| Native shorthand | Convenient defaults and argument lists | tg_send($chatId, $text, $extra) |
| Generated wrapper | Named access to an official method | tg_api_send_message($params) |
| Generic wrapper | Method name and parameter array | tg_request('sendMessage', $params) |
| Plain PHP transport | Your own HTTP request and response handling | cURL POST with JSON |
| Botlify runtime | Hosted execution, environment and gateway handling | index.php and isolated child cron |
Call tg_all_fun(); before any native helper in hosted bot code. No include path is required. With plain PHP/cURL only, omit the loader. Avoid custom function names that collide with the suite.
Feature families
| Feature | API/helper starting point | What you must supply or handle |
|---|---|---|
| Text and formatting | tg_send, sendMessage | Text escaping, length, parse mode or entities |
| Rich reports | tg_send_rich, sendRichMessage | Exactly one rich content representation |
| Streaming previews | sendMessageDraft, tg_rich_draft | Private chat support, draft ID, final message |
| Inline menus | tg_inline, tg_btn | Callback routing and authorization |
| Reply menus | tg_reply_kb | Chat/client restrictions and keyboard removal |
| Copy buttons | copy_text in an inline button | Text to copy, supported client |
| Custom emoji | tg-emoji, getCustomEmojiStickers | Actual emoji ID and eligibility |
| Button icons/colors | icon_custom_emoji_id, style | Supported style and eligible icon |
| Message effects | message_effect_id | Effect ID, supported private chat/client |
| Reactions | setMessageReaction | Message ID and chat reaction rules |
| Photos/files/audio/video | tg_send_media and send methods | Matching media type, size and source |
| Albums | sendMediaGroup | Multiple compatible media entries |
| File reuse/download | getFile, tg_download_file | Same-bot file_id, writable storage |
| Polls | sendPoll, stopPoll | Options and returned message ID |
| Location/contact | sendLocation, sendVenue, sendContact | Correct coordinates or contact fields |
| Edits/deletion | tg_edit, editMessageMedia, tg_delete | Actual message identity and permissions |
| Group administration | getChatMember, restrictChatMember | Admin rights, target user, action scope |
| Forum topics | createForumTopic and topic methods | Topic-enabled chat and thread IDs |
| Inline mode | answerInlineQuery | BotFather setting and real query update |
| Mini Apps | web_app, answerWebAppQuery | HTTPS app, init-data verification and query context |
| Stars/payments | sendInvoice, answerPreCheckoutQuery | Order validation and payment confirmation |
| Business features | business account methods | An authorized business connection and rights |
| Widgets | sendWidget and widget methods | Supported chat type, widget content and queries |
| Stickers | sendSticker and sticker-set methods | Media format, ownership and set identifiers |
| Bot settings | setMyCommands, setMyName | Scope/language and deliberate changes |
| Webhook lifecycle | getWebhookInfo, setWebhook | Platform routing and delivery configuration |
All 193 method mappings and 425 object definitions remain in the complete helper reference. Expand the relevant method for parameters and its official link. Types returned by Telegram are not necessarily valid input objects.
Do not confuse these identifiers
A chat ID selects a conversation. A message ID is meaningful within its chat. An update ID identifies an incoming update. A callback-query ID acknowledges a particular button press. A file_id reuses media for that bot; file_unique_id is for identification. A custom_emoji_id is not a message_effect_id. A business_connection_id is not a chat ID.
Store identifiers as integers where safely supported or strings where required; do not convert them to floating point. Preserve large IDs in JSON and databases.
Features that cannot be verified by a single /start
A successful API response is not a screenshot of the rendered message. Real callbacks require a user action. Inline, business and payment flows require the corresponding update and configuration. Channel administration needs rights in that channel. A missing prerequisite should be reported as NOT_TESTED, not PASS.
The auto-check examples report helper availability separately from live results. They do not prove every feature is live-tested. Set up dedicated test resources before enabling methods that modify access, delete data or spend Stars.
Official reference: Telegram Bot API.