messages.editInlineBotMessage

Edit an inline bot message

API section: Working with bot inline queries and callback buttons

messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true invert_media:flags.16?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;

Parameters

NameTypeDescription
flags # Bit mask: a field written flags.N?T is present only when bit N is set.
no_webpage flags.1?true Do not generate a link preview.
invert_media flags.16?true Show the attachment below the text rather than above it.
id InputBotInlineMessageID Identifier of the object — which object depends on the field's type.
message flags.11?string Message text.
media flags.14?InputMedia Attachment.
reply_markup flags.2?ReplyMarkup Keyboard shown under the message.
entities flags.3?Vector<MessageEntity> Text markup — bold, links, mentions and so on, as a list of ranges.

Result

Bool

Possible errors

This method has no errors of its own: it either answers or fails on the shared checks below.

Common to every call

CodeTypeWhat it means
401 AUTH_KEY_UNREGISTERED The server does not know this session: the key was revoked, expired, or the call was made before authorisation.
401 API_ID_INVALID This api_id was never issued or has been blocked. Keys come from my.ansible.su.
400 CONNECTION_LAYER_INVALID The client did not declare a layer, or declared one the server does not know.
420 FLOOD_WAIT_X Too often. Do not retry for X seconds — the number arrives in the error text.
500 INTERNAL A failure on our side. The request may be retried; if it keeps failing, it is a bug of ours.

Related pages

Types used here