SendScreenshotNotificationRequest
Both users and bots may be able to use this request. See code examples.
---functions--- messages.sendScreenshotNotification#a1405817 peer:InputPeer reply_to:InputReplyTo random_id:long = Updates
Returns
| Updates |
This type can be an instance of either:
| UpdateShort | UpdateShortChatMessage |
| UpdateShortMessage | UpdateShortSentMessage |
| Updates | UpdatesCombined |
| UpdatesTooLong |
Parameters
| peer | InputPeer | Anything entity-like will work if the library can find its Input version (e.g., usernames, Peer, User or Channel objects, etc.). |
| reply_to | InputReplyTo | |
| random_id | long | If left unspecified, it will be inferred automatically. |
Known RPC errors
This request can't cause any RPC error as far as we know.
Example
from telethon.sync import TelegramClient
from telethon import functions, types
with TelegramClient(name, api_id, api_hash) as client:
result = client(functions.messages.SendScreenshotNotificationRequest(
peer='username',
reply_to=types.InputReplyToMessage(
reply_to_msg_id=42,
top_msg_id=42,
reply_to_peer_id='username',
quote_text='some string here',
quote_entities=[types.MessageEntityUnknown(
offset=42,
length=42
)],
quote_offset=42,
monoforum_peer_id='username',
todo_item_id=42
)
))
print(result.stringify())