Docs

Reference

Delete / pin own stories

Act on the account's own stories by id: delete (cannot be undone), pin (keep on the profile) or unpin. With `conversationId` (a channel / supergroup chat the account administers, worker ≥ 1.0.33) it acts on that channel's stories.

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

Act on the account's own stories by id: delete (cannot be undone), pin (keep on the profile) or unpin. With conversationId (a channel / supergroup chat the account administers, worker ≥ 1.0.33) it acts on that channel's stories.

Overview

Name Value
Code stories.manage
Scope needed profile.write
Risk Write
May need confirmation Yes
Runs as Queues work for a node
Needs Idempotency-Key Yes
Member roles allowed owner, manager
Needs a worker from version 1.0.29
In the app Accounts → Stories → Delete / Pin

Input fields

Field Type Required Description
accountId uuid Yes
op "delete" | "pin" | "unpin" Yes
ids integer[] Yes
conversationId uuid No

Example request

curl -X POST https://tlg.builera.app/api/public/v2/ops/stories.manage \
  -H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: <unique key per operation>" \
  -d '{"accountId":"00000000-0000-0000-0000-000000000000","op":"delete","ids":[]}'

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.manage". Tool name when listed: stories_manage.

Was this page helpful?

Last checked: 10/24/2026 · build 2.0