================ Events Reference ================ Here you will find a quick summary of all the methods and properties that you can access when working with events. You can access the client that creates this event by doing ``event.client``, and you should view the description of the events to find out what arguments it allows on creation and its **attributes** (the properties will be shown here). .. important:: Remember that **all events base** `ChatGetter `! Please see :ref:`faq` if you don't know what this means or the implications of it. .. contents:: NewMessage ========== Occurs whenever a new text message or a message with media arrives. .. note:: The new message event **should be treated as** a normal `Message `, with the following exceptions: * ``pattern_match`` is the match object returned by ``pattern=``. * ``message`` is **not** the message string. It's the `Message ` object. Remember, this event is just a proxy over the message, so while you won't see its attributes and properties, you can still access them. Please see the full documentation for examples. Full documentation for the `NewMessage `. MessageEdited ============= Occurs whenever a message is edited. Just like `NewMessage `, you should treat this event as a `Message `. Full documentation for the `MessageEdited `. MessageDeleted ============== Occurs whenever a message is deleted. Note that this event isn't 100% reliable, since Telegram doesn't always notify the clients that a message was deleted. It only has the ``deleted_id`` and ``deleted_ids`` attributes (in addition to the chat if the deletion happened in a channel). Full documentation for the `MessageDeleted `. MessageRead =========== Occurs whenever one or more messages are read in a chat. Full documentation for the `MessageRead `. .. currentmodule:: telethon.events.messageread.MessageRead.Event .. autosummary:: :nosignatures: inbox message_ids get_messages is_read ChatAction ========== Occurs whenever a user joins or leaves a chat, or a message is pinned. Full documentation for the `ChatAction `. .. currentmodule:: telethon.events.chataction.ChatAction.Event .. autosummary:: :nosignatures: added_by kicked_by user input_user user_id users input_users user_ids respond reply delete get_pinned_message get_added_by get_kicked_by get_user get_input_user get_users get_input_users UserUpdate ========== Occurs whenever a user goes online, starts typing, etc. A lot of fields are attributes and not properties, so they are not shown here. Please refer to its full documentation. Full documentation for the `UserUpdate `. .. currentmodule:: telethon.events.userupdate.UserUpdate.Event .. autosummary:: :nosignatures: user input_user user_id get_user get_input_user CallbackQuery ============= Occurs whenever you sign in as a bot and a user clicks one of the inline buttons on your messages. Full documentation for the `CallbackQuery `. .. currentmodule:: telethon.events.callbackquery.CallbackQuery.Event .. autosummary:: :nosignatures: id message_id data chat_instance via_inline respond reply edit delete answer get_message InlineQuery =========== Occurs whenever you sign in as a bot and a user sends an inline query such as ``@bot query``. Full documentation for the `InlineQuery `. .. currentmodule:: telethon.events.inlinequery.InlineQuery.Event .. autosummary:: :nosignatures: id text offset geo builder answer Raw === Raw events are not actual events. Instead, they are the raw :tl:`Update` object that Telegram sends. You normally shouldn't need these.