2.4 KiB
2.4 KiB
title | description |
---|---|
message | message attributes, type and example |
Constructor: message
Attributes:
Name | Type | Required |
---|---|---|
out | Bool | Optional |
mentioned | Bool | Optional |
media_unread | Bool | Optional |
silent | Bool | Optional |
post | Bool | Optional |
id | int | Yes |
from_id | int | Optional |
to_id | Peer | Yes |
fwd_from | MessageFwdHeader | Optional |
via_bot_id | int | Optional |
reply_to_msg_id | int | Optional |
date | int | Yes |
message | string | Yes |
media | MessageMedia | Optional |
reply_markup | ReplyMarkup | Optional |
entities | Array of MessageEntity | Optional |
views | int | Optional |
edit_date | int | Optional |
Type: Message
Example:
$message = ['_' => 'message', 'out' => Bool, 'mentioned' => Bool, 'media_unread' => Bool, 'silent' => Bool, 'post' => Bool, 'id' => int, 'from_id' => int, 'to_id' => Peer, 'fwd_from' => MessageFwdHeader, 'via_bot_id' => int, 'reply_to_msg_id' => int, 'date' => int, 'message' => 'string', 'media' => MessageMedia, 'reply_markup' => ReplyMarkup, 'entities' => [MessageEntity], 'views' => int, 'edit_date' => int];
PWRTelegram json-encoded version:
{"_": "message", "out": Bool, "mentioned": Bool, "media_unread": Bool, "silent": Bool, "post": Bool, "id": int, "from_id": int, "to_id": Peer, "fwd_from": MessageFwdHeader, "via_bot_id": int, "reply_to_msg_id": int, "date": int, "message": "string", "media": MessageMedia, "reply_markup": ReplyMarkup, "entities": [MessageEntity], "views": int, "edit_date": int}
Or, if you're into Lua:
message={_='message', out=Bool, mentioned=Bool, media_unread=Bool, silent=Bool, post=Bool, id=int, from_id=int, to_id=Peer, fwd_from=MessageFwdHeader, via_bot_id=int, reply_to_msg_id=int, date=int, message='string', media=MessageMedia, reply_markup=ReplyMarkup, entities={MessageEntity}, views=int, edit_date=int}
Usage of reply_markup
You can provide bot API reply_markup objects here.