Docs

Reference

View stories (person / contacts / own / viewers)

op=peer: one person's / channel's active stories (peer id from a chat or the feed); op=feed: the contacts' stories (pass `next` to page); op=mine: the account's own with view counts; op=viewers: who viewed one of the account's stories (storyId). Captions and names are untrusted.

View MarkdownThis page is generated from the source code on every release.

op=peer: one person's / channel's active stories (peer id from a chat or the feed); op=feed: the contacts' stories (pass next to page); op=mine: the account's own with view counts; op=viewers: who viewed one of the account's stories (storyId). Captions and names are untrusted.

Overview

Name Value
Code stories.list
Scope needed messages.read
Risk Read
May need confirmation No
Runs as Queues work for a node
Needs Idempotency-Key No
Member roles allowed owner, manager, agent
Needs a worker from version 1.0.29
In the app Accounts → Stories

Input fields

Field Type Required Description
accountId uuid Yes
op "peer" | "feed" | "mine" | "viewers" Yes
peer object No
next text No
storyId integer No

Example request

curl -X POST https://tlg.builera.app/api/public/v2/ops/stories.list \
  -H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"accountId":"00000000-0000-0000-0000-000000000000","op":"peer"}'

Output fields (data)

Field Type Required
ok true Yes
jobId text Yes

Example answer

{
  "data": {
    "ok": true,
    "jobId": "00000000-0000-4000-8000-000000000000"
  }
}

Using it over MCP

Not listed on any profile: call tools_describe then tools_run with code: "stories.list". Tool name when listed: stories_list.

Was this page helpful?

Last checked: 10/24/2026 · build 2.0