2017-03-11 19:54:51 +01:00
|
|
|
---
|
|
|
|
title: updateMessageEdited
|
|
|
|
description: Message was edited. Changes in the message content will come in a separate updateMessageContent
|
|
|
|
---
|
|
|
|
## Constructor: updateMessageEdited
|
|
|
|
[Back to constructors index](index.md)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Message was edited. Changes in the message content will come in a separate updateMessageContent
|
|
|
|
|
|
|
|
### Attributes:
|
|
|
|
|
|
|
|
| Name | Type | Required | Description |
|
|
|
|
|----------|:-------------:|:--------:|------------:|
|
|
|
|
|chat\_id|[long](../types/long.md) | Yes|Chat identifier|
|
|
|
|
|message\_id|[long](../types/long.md) | Yes|Message identifier|
|
|
|
|
|edit\_date|[int](../types/int.md) | Yes|Date the message was edited, unix time|
|
|
|
|
|reply\_markup|[ReplyMarkup](../types/ReplyMarkup.md) | Yes|New message reply markup, nullable|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### Type: [Update](../types/Update.md)
|
|
|
|
|
|
|
|
|
|
|
|
### Example:
|
|
|
|
|
|
|
|
```
|
2017-07-23 16:33:46 +02:00
|
|
|
$updateMessageEdited = ['_' => 'updateMessageEdited', 'chat_id' => long, 'message_id' => long, 'edit_date' => int, 'reply_markup' => ReplyMarkup];
|
2017-03-11 19:54:51 +01:00
|
|
|
```
|
|
|
|
|
2017-07-23 16:11:02 +02:00
|
|
|
[PWRTelegram](https://pwrtelegram.xyz) json-encoded version:
|
|
|
|
|
|
|
|
```
|
2017-07-23 16:33:46 +02:00
|
|
|
{"_": "updateMessageEdited", "chat_id": long, "message_id": long, "edit_date": int, "reply_markup": ReplyMarkup}
|
2017-07-23 16:11:02 +02:00
|
|
|
```
|
|
|
|
|
|
|
|
|
2017-03-11 19:54:51 +01:00
|
|
|
Or, if you're into Lua:
|
|
|
|
|
|
|
|
|
|
|
|
```
|
2017-07-23 16:33:46 +02:00
|
|
|
updateMessageEdited={_='updateMessageEdited', chat_id=long, message_id=long, edit_date=int, reply_markup=ReplyMarkup}
|
2017-03-11 19:54:51 +01:00
|
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
2017-04-10 13:49:32 +02:00
|
|
|
|
|
|
|
## Usage of reply_markup
|
|
|
|
|
|
|
|
You can provide bot API reply_markup objects here.
|
|
|
|
|
|
|
|
|