1.4 KiB
1.4 KiB
title | description |
---|---|
updateMessageEdited | Message was edited. Changes in the message content will come in a separate updateMessageContent |
Constructor: updateMessageEdited
Message was edited. Changes in the message content will come in a separate updateMessageContent
Attributes:
Name | Type | Required | Description |
---|---|---|---|
chat_id | long | Yes | Chat identifier |
message_id | long | Yes | Message identifier |
edit_date | int | Yes | Date the message was edited, unix time |
reply_markup | ReplyMarkup | Yes | New message reply markup, nullable |
Type: Update
Example:
$updateMessageEdited = ['_' => 'updateMessageEdited', 'chat_id' => long, 'message_id' => long, 'edit_date' => int, 'reply_markup' => ReplyMarkup];
PWRTelegram json-encoded version:
{"_": "updateMessageEdited", "chat_id": long, "message_id": long, "edit_date": int, "reply_markup": ReplyMarkup}
Or, if you're into Lua:
updateMessageEdited={_='updateMessageEdited', chat_id=long, message_id=long, edit_date=int, reply_markup=ReplyMarkup}
Usage of reply_markup
You can provide bot API reply_markup objects here.