Docs

Reference

Upgrade to supergroup

Upgrade a basic group to a supergroup (needed for slow mode, bans, larger groups). Cannot be undone; the old group stays read-only and the supergroup becomes a new chat.

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

Upgrade a basic group to a supergroup (needed for slow mode, bans, larger groups). Cannot be undone; the old group stays read-only and the supergroup becomes a new chat.

Overview

Name Value
Code groups.upgrade
Scope needed groups.admin
Risk Dangerous
May need confirmation Yes
Runs as Queues work for a node
Needs Idempotency-Key Yes
Member roles allowed owner, manager, agent
Needs a worker from version 1.0.17
In the app Inbox → group info → Manage

Input fields

Field Type Required Description
conversationId uuid Yes

Example request

curl -X POST https://tlg.builera.app/api/public/v2/ops/groups.upgrade \
  -H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: <unique key per operation>" \
  -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: "groups.upgrade". Tool name when listed: groups_upgrade.

Was this page helpful?

Last checked: 10/24/2026 · build 2.0