Send Text With Result Semantics

Client.send_message() accepts a normalized Peer, a numeric ID, or a username. Resolve and cache peer data through the client rather than constructing an incomplete raw input peer yourself.

from miniproto import Client


async def send_notice(client: Client) -> int:
    message = await client.send_message("@your_test_chat", "Maintenance begins soon.")
    return message.id

The await completes when miniproto receives and normalizes Telegram’s RPC result. A bot still needs permission to post in the target chat, and a numeric peer may lack access data; neither condition is inferred from the Python type.

quick_ack=True or quick_ack_callback= requests an optional transport acknowledgement for the final encrypted request. That receipt means the transport accepted the packet; it is not the send result and does not replace awaiting send_message(). Use a caller-supplied random_id only when your application owns its idempotency scheme; miniproto otherwise creates one.

For raw send options beyond this small convenience method, use Invoke a Raw Telegram Function and the generated Raw API.