Reference

Check a channel's boosts / story rights

For a channel / supergroup chat of the account (worker ≥ 1.0.33): whether Telegram lets the account post a story there now (`channel.canPost`, `channel.reason` such as BOOSTS_REQUIRED / CHAT_ADMIN_REQUIRED / STORIES_TOO_MUCH, `channel.remaining` slots) and its boosts (`channel.boosts`: level, boosts, boosts for the next level, boost link — admins only). Read-only.

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

For a channel / supergroup chat of the account (worker ≥ 1.0.33): whether Telegram lets the account post a story there now (channel.canPost, channel.reason such as BOOSTS_REQUIRED / CHAT_ADMIN_REQUIRED / STORIES_TOO_MUCH, channel.remaining slots) and its boosts (channel.boosts: level, boosts, boosts for the next level, boost link — admins only). Read-only.

Overview

Name	Value
Code	`stories.channel_status`
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.33`
In the app	Manage channel → Stories

Input fields

Field	Type	Required	Description
`conversationId`	`uuid`	Yes

Example request

curl -X POST https://tlg.builera.app/api/public/v2/ops/stories.channel_status \
  -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.channel_status". Tool name when listed: stories_channel_status.

Check a channel's boosts / story rights

#Overview

#Input fields

#Example request

#Output fields (data)

#Example answer