Daniil Gentili
e4a326e552
* refactor * Apply fixes from StyleCI * Implement https and http transport, add support for new req_pq_multi, send pending acks and objects in containers along with the next method call, remove dependency on the socket extension. * Apply fixes from StyleCI * Make types with empty constructors optional, fix phar archives (fixes #217) * Apply fixes from StyleCI * Update to layer 75 * Update github pages gemfile.lock
1.4 KiB
1.4 KiB
| title | description |
|---|---|
| botInlineMessageMediaVenue | botInlineMessageMediaVenue attributes, type and example |
Constructor: botInlineMessageMediaVenue
Attributes:
| Name | Type | Required |
|---|---|---|
| geo | GeoPoint | Optional |
| title | string | Yes |
| address | string | Yes |
| provider | string | Yes |
| venue_id | string | Yes |
| reply_markup | ReplyMarkup | Optional |
Type: BotInlineMessage
Example:
$botInlineMessageMediaVenue = ['_' => 'botInlineMessageMediaVenue', 'geo' => GeoPoint, 'title' => 'string', 'address' => 'string', 'provider' => 'string', 'venue_id' => 'string', 'reply_markup' => ReplyMarkup];
PWRTelegram json-encoded version:
{"_": "botInlineMessageMediaVenue", "geo": GeoPoint, "title": "string", "address": "string", "provider": "string", "venue_id": "string", "reply_markup": ReplyMarkup}
Or, if you're into Lua:
botInlineMessageMediaVenue={_='botInlineMessageMediaVenue', geo=GeoPoint, title='string', address='string', provider='string', venue_id='string', reply_markup=ReplyMarkup}
Usage of reply_markup
You can provide bot API reply_markup objects here.