SetCustomVerificationRequest

Both users and bots may be able to use this request. See code examples.

---functions---
bots.setCustomVerification#8b89dfbd flags:# enabled:flags.1?true bot:flags.0?InputUser peer:InputPeer custom_description:flags.2?string = Bool

Returns

Bool

This type has no instances available.

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.).
enabled	flag	This argument defaults to `None` and can be omitted.
bot	InputUser	This argument defaults to `None` and can be omitted. Anything entity-like will work if the library can find its `Input` version (e.g., usernames, `Peer`, `User` or `Channel` objects, etc.).
custom_description	string	This argument defaults to `None` and can be omitted.

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.bots.SetCustomVerificationRequest(
        peer='username',
        enabled=True,
        bot='username',
        custom_description='some string here'
    ))
    print(result)