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.2 KiB
1.2 KiB
| title | description |
|---|---|
| botInlineMessageMediaContact | botInlineMessageMediaContact attributes, type and example |
Constructor: botInlineMessageMediaContact
Attributes:
| Name | Type | Required |
|---|---|---|
| phone_number | string | Yes |
| first_name | string | Yes |
| last_name | string | Yes |
| reply_markup | ReplyMarkup | Optional |
Type: BotInlineMessage
Example:
$botInlineMessageMediaContact = ['_' => 'botInlineMessageMediaContact', 'phone_number' => 'string', 'first_name' => 'string', 'last_name' => 'string', 'reply_markup' => ReplyMarkup];
PWRTelegram json-encoded version:
{"_": "botInlineMessageMediaContact", "phone_number": "string", "first_name": "string", "last_name": "string", "reply_markup": ReplyMarkup}
Or, if you're into Lua:
botInlineMessageMediaContact={_='botInlineMessageMediaContact', phone_number='string', first_name='string', last_name='string', reply_markup=ReplyMarkup}
Usage of reply_markup
You can provide bot API reply_markup objects here.