2017-03-31 17:35:20 +02:00
|
|
|
---
|
|
|
|
title: inputBotInlineMessageText
|
|
|
|
description: inputBotInlineMessageText attributes, type and example
|
|
|
|
---
|
|
|
|
## Constructor: inputBotInlineMessageText
|
|
|
|
[Back to constructors index](index.md)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### Attributes:
|
|
|
|
|
|
|
|
| Name | Type | Required |
|
2017-08-20 11:05:56 +02:00
|
|
|
|----------|---------------|----------|
|
2017-03-31 17:35:20 +02:00
|
|
|
|no\_webpage|[Bool](../types/Bool.md) | Optional|
|
|
|
|
|message|[string](../types/string.md) | Yes|
|
|
|
|
|entities|Array of [MessageEntity](../types/MessageEntity.md) | Optional|
|
|
|
|
|reply\_markup|[ReplyMarkup](../types/ReplyMarkup.md) | Optional|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### Type: [InputBotInlineMessage](../types/InputBotInlineMessage.md)
|
|
|
|
|
|
|
|
|
|
|
|
### Example:
|
|
|
|
|
|
|
|
```
|
2017-07-23 16:33:46 +02:00
|
|
|
$inputBotInlineMessageText = ['_' => 'inputBotInlineMessageText', 'no_webpage' => Bool, 'message' => 'string', 'entities' => [MessageEntity], 'reply_markup' => ReplyMarkup];
|
2017-03-31 17:35:20 +02:00
|
|
|
```
|
|
|
|
|
2017-07-23 16:11:02 +02:00
|
|
|
[PWRTelegram](https://pwrtelegram.xyz) json-encoded version:
|
|
|
|
|
|
|
|
```
|
2017-07-23 16:33:46 +02:00
|
|
|
{"_": "inputBotInlineMessageText", "no_webpage": Bool, "message": "string", "entities": [MessageEntity], "reply_markup": ReplyMarkup}
|
2017-07-23 16:11:02 +02:00
|
|
|
```
|
|
|
|
|
|
|
|
|
2017-03-31 17:35:20 +02:00
|
|
|
Or, if you're into Lua:
|
|
|
|
|
|
|
|
|
|
|
|
```
|
2017-07-23 16:33:46 +02:00
|
|
|
inputBotInlineMessageText={_='inputBotInlineMessageText', no_webpage=Bool, message='string', entities={MessageEntity}, reply_markup=ReplyMarkup}
|
2017-03-31 17:35:20 +02:00
|
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
2017-04-10 13:49:32 +02:00
|
|
|
|
|
|
|
## Usage of reply_markup
|
|
|
|
|
|
|
|
You can provide bot API reply_markup objects here.
|
|
|
|
|
|
|
|
|