2016-12-20 13:15:22 +01:00
|
|
|
---
|
|
|
|
title: inputBotInlineMessageMediaGeo
|
2016-12-20 13:32:11 +01:00
|
|
|
description: inputBotInlineMessageMediaGeo attributes, type and example
|
2016-12-20 13:15:22 +01:00
|
|
|
---
|
2016-12-19 16:56:52 +01:00
|
|
|
## Constructor: inputBotInlineMessageMediaGeo
|
2016-12-20 13:15:22 +01:00
|
|
|
[Back to constructors index](index.md)
|
|
|
|
|
|
|
|
|
2016-12-19 16:56:52 +01:00
|
|
|
|
|
|
|
### Attributes:
|
|
|
|
|
|
|
|
| Name | Type | Required |
|
2017-08-20 11:05:56 +02:00
|
|
|
|----------|---------------|----------|
|
2017-03-11 19:54:51 +01:00
|
|
|
|geo\_point|[InputGeoPoint](../types/InputGeoPoint.md) | Yes|
|
2016-12-19 16:56:52 +01:00
|
|
|
|reply\_markup|[ReplyMarkup](../types/ReplyMarkup.md) | Optional|
|
|
|
|
|
2016-12-19 18:56:05 +01:00
|
|
|
|
|
|
|
|
|
|
|
### Type: [InputBotInlineMessage](../types/InputBotInlineMessage.md)
|
|
|
|
|
|
|
|
|
2016-12-19 16:56:52 +01:00
|
|
|
### Example:
|
|
|
|
|
|
|
|
```
|
2017-07-23 16:33:46 +02:00
|
|
|
$inputBotInlineMessageMediaGeo = ['_' => 'inputBotInlineMessageMediaGeo', 'geo_point' => InputGeoPoint, 'reply_markup' => ReplyMarkup];
|
Added docs for layer 18, 23, 25, 27, 33, 38, 40, 41, 42, 44, 45, 46, 51, 53, 55
2017-01-02 21:04:36 +01:00
|
|
|
```
|
|
|
|
|
2017-07-23 16:11:02 +02:00
|
|
|
[PWRTelegram](https://pwrtelegram.xyz) json-encoded version:
|
|
|
|
|
|
|
|
```
|
2017-07-23 16:33:46 +02:00
|
|
|
{"_": "inputBotInlineMessageMediaGeo", "geo_point": InputGeoPoint, "reply_markup": ReplyMarkup}
|
2017-07-23 16:11:02 +02:00
|
|
|
```
|
|
|
|
|
|
|
|
|
2017-03-11 19:54:51 +01:00
|
|
|
Or, if you're into Lua:
|
|
|
|
|
|
|
|
|
|
|
|
```
|
2017-07-23 16:33:46 +02:00
|
|
|
inputBotInlineMessageMediaGeo={_='inputBotInlineMessageMediaGeo', geo_point=InputGeoPoint, reply_markup=ReplyMarkup}
|
2017-03-11 19:54:51 +01:00
|
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
2017-04-10 13:49:32 +02:00
|
|
|
|
|
|
|
## Usage of reply_markup
|
|
|
|
|
|
|
|
You can provide bot API reply_markup objects here.
|
|
|
|
|
|
|
|
|