Change a connected Telegram group
Changes what is sent and keeps the rest. `listed`: whether the brand's member profile lists the group under Communities (null lists it): only with a way in, a public username, or join requests because a gate lets people in, so `true` with none is refused (400 at `listed`, with the fix). Needs `org.integrations.edit`. Recorded as `telegram_group.updated` with the fields changed.
/v1/orgs/{org}/telegram-groups/{group}Changes what is sent and keeps the rest. listed: whether the brand's member profile lists the group under Communities (null lists it): only with a way in, a public username, or join requests because a gate lets people in, so true with none is refused (400 at listed, with the fix). Needs org.integrations.edit. Recorded as telegram_group.updated with the fields changed.
Authorization
bearer An org API key (sk_live_…, sk_test_…), or an access token from the Synq issuer (the synq brand, on the accounts host) for this API.
In: header
Path Parameters
The org's id
^org_[0-9a-hjkmnp-tv-z]{26}$The Telegram group's id
^tgg_[0-9a-hjkmnp-tv-z]{26}$Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X PATCH "https://api.synq.build/v1/orgs/org_01h455vb4pex5vsknk084sn02q/telegram-groups/tgg_01h455vb4pex5vsknk084sn02q" \ -H "Authorization: Bearer $SYNQ_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "listed": true }'{ "id": "tgg_01h455vb4pex5vsknk084sn02q", "brand_id": "brd_01h455vb4pex5vsknk084sn02q", "chat_id": "-1001234567890", "title": "RODAI Holders", "username": "string", "kind": "group", "status": "connected", "guard_bot": true, "rights": { "invite_users": true, "restrict_members": true, "pin_messages": true }, "member_count": 0, "invite_link": "string", "own_bot": true, "listed": true, "listed_by": "brand", "counts": { "roles": 0, "gated": true, "managed": 0 }, "checked_at": "2026-10-21T12:00:00.000Z", "connected_at": "2026-10-21T12:00:00.000Z"}List the Telegram groups an org connected GET
Every group the org connected for its token gates, with the bot's rights there, whether it is the group's guard bot and how many people Synq manages, and the bot that serves the org on Telegram. Needs `org.integrations.view`.
Start connecting a Telegram group POST
A one-time code, good for 15 minutes, and the link that adds Synq's bot to a group as an admin and sends it there; `command` is the same for a bot already in the group. Only an admin of the group can connect it, and people verify on `brand`'s hosted pages: they sign in the way they already do, link Telegram on their member profile and show what they hold with wallets, so the brand must offer wallets (400 at `brand` with the fix otherwise); it needn't offer Telegram sign-in. Synq's bot reads the group and its own rights when the code arrives, and the group is recorded as `telegram_group.connected`. At most 25 groups per org. Needs `org.integrations.edit` and a plan with token gating (403 `plan_feature_unavailable`), and an API with a Telegram bot (409 `telegram_unavailable`).