Create a managed bot » owned by the current user and controlled by the specified manager bot.
Method schema is available as of layer 224. Switch »
| Name | Type | Description |
|---|---|---|
| flags | # | Flags, see TL conditional fields |
| via_deeplink | flags.0?true | Set only if the creation prompt was opened from a managed bot creation request deep link » |
| name | string | Display name of the bot, 1–64 characters |
| username | string | Username for the bot, as validated by bots.checkUsername |
| manager_id | InputUser | The manager bot that will control the created bot; must have the user.bot_can_manage_bots flag set |
| Code | Type | Description |
|---|---|---|
| 400 | NAME_INVALID | The specified bot name is invalid. |
Telegram clients must handle special tg:// and t.me deep links encountered in messages, link entities and in other apps by registering OS handlers.
Check whether a username is available and valid for use when creating a managed bot ».
Indicates info about a certain user.
Unless specified otherwise, when updating the local peer database, all fields from the newly received constructor take priority over the old constructor cached locally (including by removing fields that aren't set in the new constructor).
See here » for an implementation of the logic to use when updating the local user peer database.
Users can create managed bots (which are controlled by a specific manager bot) directly through the MTProto API, without interacting with @BotFather.