> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# Telegram guides

> Find older channel notices and select traceable sources for a weekly brief.

To find an older notice in a public Telegram channel, search the channel with `telegram.web.fetch_channel_search`. To choose channels for a weekly brief, compare candidates with `telegram.web.batch_channel_info` and `telegram.web.fetch_similar_channels`. When an announcement shared in chat may have changed, [compare the original message with your saved copy](/guides/telegram-channel-archive); the archive guide also shows how to save recent announcements for the weekly brief.

## Choose a task

* [Archive channel messages](/guides/telegram-channel-archive)

## Which announcement moved last month's registration deadline?

Search the public channel with the channel username and the phrase you remember. Open the matching notice, then check the event name and date.

```json
{"action":"telegram.web.fetch_channel_search","params":{"channel":"<channel username>","query":"registration extended","limit":20}}
```

POST the body to `https://api.beatapi.io/v1/social-data/call` with BeatAPI Bearer authentication. If the search misses the notice, follow the [channel archive guide](/guides/telegram-channel-archive): read a bounded set of messages, filter the messages by their actual timestamps, and record the period you inspected. After you find the notice, check the notice's current text and send your teammate the confirmed date and the original link.

## Which of these channels are worth adding to next week's brief?

1. Pass up to 20 known channel usernames to `telegram.web.batch_channel_info` as one comma-separated `channels` string.
2. For more candidates, pass one confirmed channel username as `channel` to `telegram.web.fetch_similar_channels`.
3. Before adding a channel to the weekly archive, record the channel's subject, one representative recent notice and the reason the channel belongs in your brief.

Send both bodies to the same `/v1/social-data/call` endpoint, replacing the placeholders with confirmed usernames.

```json
{"action":"telegram.web.batch_channel_info","params":{"channels":"<channel A username>,<channel B username>"}}
```

```json
{"action":"telegram.web.fetch_similar_channels","params":{"channel":"<reference channel username>"}}
```

## Related content

[Telegram questions](/faq/telegram)