App Logo
web.telegram.org

Telegram — Read a conversation's messages

Open one Telegram conversation by its peer id (the id get_inbox returns) and read its messages in chronological order: message id, text, the time shown on the bubble, whether it carries media, and — for channel posts — the exact view and forward counts. Scrolls upward to load older messages up to the requested count. Returns an empty list for a conversation with no messages, which is a real answer rather than a failure.

Input

peerId required

The conversation's peer id, as returned by get_inbox (e.g. "-1001928149680"). Passed straight to Telegram's own deep link, so it must be the id and not a display name.

count optional

How many of the most recent messages to return, scrolling upward to load older ones.

Default: 30

Output

count required

How many messages were returned.

state required

"ready" when message bubbles rendered; "empty" for a conversation that resolved (it has a title) but holds no messages — only after the empty list has held steady long enough to rule out a list that is still loading. An unresolvable peer id throws instead.

peerId required

The peer id that was actually opened, read back from the address bar.

messages required

Messages oldest-first, as the conversation displays them.

chatTitle optional

The conversation title shown in the header, for a human-readable cross-check against peerId.

FAQ

Open one Telegram conversation by its peer id (the id get_inbox returns) and read its messages in chronological order: message id, text, the time shown on the bubble, whether it carries media, and — for channel posts — the exact view and forward counts. Scrolls upward to load older messages up to the requested count. Returns an empty list for a conversation with no messages, which is a real answer rather than a failure.
Required: peerId. Optional: count.
It returns count, state, peerId, messages, chatTitle.
Yes. It acts as you on web.telegram.org: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the web.telegram.org cookies saved by the Reduck extension.
It only reads. It looks things up on web.telegram.org and changes nothing there.
Ask an AI agent connected to Reduck to run reduck/web.telegram.org/get_conversation, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/web.telegram.org/get_conversation
It is part of Reduck's official curated catalogue.

Start building not clicking