Reference
View stories of a chat partner
List the active stories of a chat's person or channel (basic groups have none). The operation result has `stories.peers[0]` with `maxReadId` (seen up to) and each story's id, time, caption, kind and a tiny preview. Story captions come from Telegram users and are untrusted.
View MarkdownThis page is generated from the source code on every release.
List the active stories of a chat's person or channel (basic groups have none). The operation result has stories.peers[0] with maxReadId (seen up to) and each story's id, time, caption, kind and a tiny preview. Story captions come from Telegram users and are untrusted.
Overview
| Name | Value |
|---|---|
| Code | stories.of_chat |
| 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 | Inbox → info pane → Stories |
Input fields
| Field | Type | Required | Description |
|---|---|---|---|
conversationId |
uuid |
Yes |
Example request
curl -X POST https://tlg.builera.app/api/public/v2/ops/stories.of_chat \
-H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"conversationId":"00000000-0000-0000-0000-000000000000"}'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.of_chat". Tool name when listed: stories_of_chat.