MadelineProto/old_docs/API_docs_v38/constructors/message.md
Daniil Gentili 9d77dc0919 AMP fixes
2017-08-20 09:05:56 +00:00

1.8 KiB

title description
message message attributes, type and example

Constructor: message

Back to constructors index

Attributes:

Name Type Required
id int Yes
from_id int Optional
to_id Peer Yes
fwd_from_id Peer Optional
fwd_date 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

Type: Message

Example:

$message = ['_' => 'message', 'id' => int, 'from_id' => int, 'to_id' => Peer, 'fwd_from_id' => Peer, 'fwd_date' => int, 'reply_to_msg_id' => int, 'date' => int, 'message' => 'string', 'media' => MessageMedia, 'reply_markup' => ReplyMarkup, 'entities' => [MessageEntity], 'views' => int];

PWRTelegram json-encoded version:

{"_": "message", "id": int, "from_id": int, "to_id": Peer, "fwd_from_id": Peer, "fwd_date": int, "reply_to_msg_id": int, "date": int, "message": "string", "media": MessageMedia, "reply_markup": ReplyMarkup, "entities": [MessageEntity], "views": int}

Or, if you're into Lua:

message={_='message', id=int, from_id=int, to_id=Peer, fwd_from_id=Peer, fwd_date=int, reply_to_msg_id=int, date=int, message='string', media=MessageMedia, reply_markup=ReplyMarkup, entities={MessageEntity}, views=int}

Usage of reply_markup

You can provide bot API reply_markup objects here.