Monitor public Telegram channels for announcements and news
Pull messages from public Telegram channels posted since a date as JSON, to follow announcements, releases and market chatter without reading the app.
Product launches, price drops, security notices and community news often show up first in a public Telegram channel, and they are buried in a feed you will not scroll every day. Lovely Router reads channels for you. Send channel names and a start date, get one JSON object per message, pay per message from a prepaid balance.
Hand it to your AI agent
Copy this prompt into Claude Code, Cursor, Codex or any coding agent. It tells the agent where the docs are and how to use your API key.
Monitor public Telegram channels for announcements and news. Use the Lovely Router data tools: each returns JSON and is billed per result.
- Docs (read first): https://lovelyrouter.com/docs/tools/find.md and https://lovelyrouter.com/docs/tools/run.md
- Plan first: POST https://lovelyrouter.com/v1/tools/suggest with `{"task": "<my task in plain words>"}` (free). It returns the tools to run in order, each with an example `input`, the `input_required` fields, an estimated cost and a ready-made `run` request. Replace the example values with my task's; if a field is unclear, read the tool with GET https://lovelyrouter.com/v1/tools/<id>. To browse instead, POST https://lovelyrouter.com/v1/tools/discover searches the catalog.
- Show me the plan and its estimated cost (`total_est_cost_usd`) before running anything large.
- Run: POST https://lovelyrouter.com/v1/tools/<id>/run with `{"input": {...}, "max_results": N}`. A 200 has the finished run with `items`; a 202 means it is still running, so poll the `poll` path until `status` is `succeeded`, `failed`, `timed_out` or `stopped`.
- Only delivered results are billed. Keep max_results small on the first run, check the output, then scale up.
- If you support MCP, connect https://lovelyrouter.com/mcp instead (Streamable HTTP, same key; https://lovelyrouter.com/docs/tools/mcp.md) and use suggest_tools, get_tool and run_tool.
- Auth: read my API key from the LOVELY_API_KEY environment variable and send it as `Authorization: Bearer $LOVELY_API_KEY`. Never print or commit the key. If it is not set, ask me to create one at https://lovelyrouter.com/app/keys.
- Billing is prepaid: every call is charged to my balance, so test with a small request before running anything large.
- Every docs page is plain Markdown; the full index is https://lovelyrouter.com/llms.txt.
My task: <the inputs (links, keywords or accounts) and how many results you need>How it works
List the channels
The public channels you want to follow, as exact names such as
durovor links such ashttps://t.me/telegram.Run the tool with a cap
Send them with a start date to
POST /v1/tools/telegram-channel/runwithmax_results. The run holds its maximum cost from your balance and returns the messages as JSON.Move the date forward
Store the date of your last run and use it as the next start date, so each run only brings what is new.
Get channel messages with one request
Get Telegram channel messages takes channels in profiles and a start date in oldestMessageDate, written YYYY-MM-DD. Both are required:
curl https://lovelyrouter.com/v1/tools/telegram-channel/run \
-H "Authorization: Bearer $LOVELY_API_KEY" \
-H "content-type: application/json" \
-d '{
"input": {
"profiles": [
"durov"
],
"oldestMessageDate": "2026-09-01"
},
"max_results": 50
}'Only messages posted on or after that date are returned, and max_results caps how many. A run still going after 60 seconds returns 202; Run a tool shows how to poll.
What each message holds
| Field group | What you get |
|---|---|
| Messages | Messages from each public channel you list |
| Window | Only those posted on or after oldestMessageDate |
Only public channels are covered, and names must be exact. Ask a model to translate, summarize or classify the messages in the same job.
Recipes
Run your list of vendor and community channels each morning with yesterday's date and send a model's summary to Slack.
Follow their announcements and flag price changes or releases.
Follow public channels that cover your sector and let a model score each message as relevant or noise.
Start from an old date once to build a searchable copy of what a channel has posted.
When a claim spreads, pull the channels that first posted it and compare dates.
Prefer plain words? Connect the MCP server and tell Claude Code or Cursor: "Read the last week of messages from the Telegram channels in channels.txt, up to 200, and summarize anything about price changes or new releases. Set max_results to 200."
What you pay
You pay per message: starting a run holds its maximum cost, the per-call fee plus the per-message fee times max_results, and the run settles to what it returned. The rest of the hold goes back to your balance. A run that fails or times out pays only for the messages it delivered, and a run refused at the start costs nothing.
Reading 300 messages a day is billed as 300 messages a day. There is no subscription and no monthly minimum: top up from $5, and one balance pays for tools and models. The card above shows today's price; pricing lists every tool.
Frequently asked questions
Which channels can I read?+
Public channels, by exact name or link. Private groups are not covered.
How do I only get new messages?+
Set oldestMessageDate to the day of your last run. It is required on every run.
How many messages can one run return?+
Up to 500, set with max_results.
Is this allowed?+
Only public channel content is read. You are responsible for using people's data lawfully, including privacy and anti-spam rules where you operate.
Do I need a subscription?+
No. You add credit to a prepaid balance and each run draws it down. Failed runs pay only for the results they delivered, and nothing renews automatically.
Following more than Telegram? See social listening, Chinese social media data and the tool catalog.