replyInlineMarkup
replyInlineMarkup
Section titled “replyInlineMarkup”No description provided by the pinned schema.
Signature
Section titled “Signature”replyInlineMarkup#b2b15770 flags:# force_reply:flags.5?true rows:Vector<KeyboardInlineButtonRow> = ReplyMarkup;Result type
Section titled “Result type”ReplyMarkup
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| flags | # | flag word | — | No description provided by the pinned schema. |
| force_reply | flags.5?true | flags.5 | — | No description provided by the pinned schema. |
| rows | Vector | — | — | No description provided by the pinned schema. |
| Parameter | Bit | Meaning |
|---|---|---|
| force_reply | 5 | Controlled by flags; present when this bit is set. |
Python binding
Section titled “Python binding”from miniproto.raw.types import ReplyInlineMarkupPublic access: miniproto.raw.types.ReplyInlineMarkup.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.types import ReplyInlineMarkup
# Naming the raw constructor class is local only; it performs no I/O or network request.constructor_type = ReplyInlineMarkupResult family
Section titled “Result family”Relationships
Section titled “Relationships”- Result family:
ReplyMarkup - Related constructors:
replyKeyboardForceReply,replyKeyboardHide,replyKeyboardMarkup - Accepted by:
ephemeral.editMessage,ephemeral.sendMessage,messages.editInlineBotMessage,messages.editMessage,messages.sendMedia,messages.sendMessage,botInlineMessageMediaAuto,botInlineMessageMediaContact,botInlineMessageMediaGeo,botInlineMessageMediaInvoice,botInlineMessageMediaVenue,botInlineMessageMediaWebPage,botInlineMessageRichMessage,botInlineMessageText,ephemeralMessage,inputBotInlineMessageGame,inputBotInlineMessageMediaAuto,inputBotInlineMessageMediaContact,inputBotInlineMessageMediaGeo,inputBotInlineMessageMediaInvoice,inputBotInlineMessageMediaVenue,inputBotInlineMessageMediaWebPage,inputBotInlineMessageRichMessage,inputBotInlineMessageText,message
Provenance
Section titled “Provenance”- structural source:
tdlib - canonical schema: https://raw.githubusercontent.com/tdlib/td/refs/heads/master/td/generate/scheme/telegram_api.tl
- prose merge precedence: TDLib → Telegram Desktop → Core JSON
- source note: Canonical structure is the pinned TDLib telegram_api.tl; Layer 229 comes only from the matching Telegram Desktop end-of-file marker; core.telegram.org inputs enrich documentation and RPC error metadata without overriding structure.
Source-diff notes
Section titled “Source-diff notes”- tdlib_vs_core: changed_count=78; core_only_count=18; overlap_count=2285; tdlib_only_count=195
- tdlib_vs_tdesktop: changed_count=0; overlap_count=2470; tdesktop_only=null; tdlib_only=accessPointRule, help.configSimple, inputPeerPhotoFileLocationLegacy, inputStickerSetThumbLegacy, invokeWithApnsSecretPrefix, invokeWithBusinessConnectionPrefix, invokeWithGooglePlayIntegrityPrefix, invokeWithReCaptchaPrefix, ipPort, ipPortSecret