Announce a Telegram group's window
Reads the group and the bot's rights afresh, posts the announcement in the window's topic and pins it (without a notification), and starts the countdown: everyone already in the group, but its admins and bots, has until the deadline to verify. Takes the settings as `PUT …/window` does, saved first. The bot needs Pin messages and Ban users (409 with the fix). Synq posts it in the background (202), so the caller may go: the window answers `announce_queued_at` until it's posted, then `announced`, or `announce_failure` with the fix when nothing was posted; pressing it again meanwhile is the same announcement. What Synq knows without asking Telegram (no gate, announced already, the gate off) is refused at once. An API without a background runner posts at once (200). Recorded as `telegram_group.window_announced`, as who asked. Needs `org.integrations.edit`, a plan with token gating (403 `plan_feature_unavailable`) and an API with a Telegram bot (409 `telegram_unavailable`).
/v1/orgs/{org}/telegram-groups/{group}/window/announceReads the group and the bot's rights afresh, posts the announcement in the window's topic and pins it (without a notification), and starts the countdown: everyone already in the group, but its admins and bots, has until the deadline to verify. Takes the settings as PUT …/window does, saved first. The bot needs Pin messages and Ban users (409 with the fix). Synq posts it in the background (202), so the caller may go: the window answers announce_queued_at until it's posted, then announced, or announce_failure with the fix when nothing was posted; pressing it again meanwhile is the same announcement. What Synq knows without asking Telegram (no gate, announced already, the gate off) is refused at once. An API without a background runner posts at once (200). Recorded as telegram_group.window_announced, as who asked. Needs org.integrations.edit, a plan with token gating (403 plan_feature_unavailable) and an API with a Telegram bot (409 telegram_unavailable).
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/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://api.synq.build/v1/orgs/org_01h455vb4pex5vsknk084sn02q/telegram-groups/tgg_01h455vb4pex5vsknk084sn02q/window/announce" \ -H "Authorization: Bearer $SYNQ_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "notice_days": 365, "deadline_time": "18:00", "time_zone": "America/New_York", "quiet_hours": { "from": "22:00", "to": "09:00" }, "name_unverified": true, "message_reachable": true, "headline": "Token gate: ROD.AI is becoming a home for holders and users of our products.", "topic": 4 }'{ "group": "string", "state": "draft", "notice_days": 0, "deadline_time": "string", "time_zone": "string", "quiet_hours": { "from": "22:00", "to": "09:00" }, "name_unverified": true, "message_reachable": true, "headline": "string", "topic": 0, "forum": true, "on_lost": "mute", "topics": [ { "id": 0, "name": "Acme", "closed": true } ], "starts_at": "2026-10-21T12:00:00.000Z", "ends_at": "2026-10-21T12:00:00.000Z", "paused_at": "2026-10-21T12:00:00.000Z", "extended_at": "2026-10-21T12:00:00.000Z", "members_listed_at": "2026-10-21T12:00:00.000Z", "members_list_complete": true, "closed_at": "2026-10-21T12:00:00.000Z", "schedule": [ { "reminder": "m1", "kind": "monthly", "at": "2026-10-21T12:00:00.000Z", "message_reachable": true, "names": true, "done": true } ], "counts": { "members": 0, "admins": 0, "verified": 0, "to_verify": 0, "unknown": 0, "settled": 0 }, "deadline": { "per_minute": 0, "minutes": 0 }, "problem": "members_unknown", "problem_detail": "string", "announce_queued_at": "2026-10-21T12:00:00.000Z", "announce_failure": "string", "move": { "from_topic": 0, "requested_at": "2026-10-21T12:00:00.000Z", "waits_until": "2026-10-21T12:00:00.000Z" }}Read a Telegram group again POST
Reads the group's title and kind, whether Synq's bot is its guard bot, and the bot's rights there from Telegram now: after an admin changed them, or the group became a supergroup. A change is recorded as `telegram_group.updated`; a bot no longer in the group as `telegram_group.bot_removed`. Needs `org.integrations.edit`, and an API with a Telegram bot (409 `telegram_unavailable`).
Move a Telegram group's deadline later POST
Moves the deadline to `ends_at`, which must be later than it is (it never moves earlier once announced), at most 365 days away and outside quiet hours. Synq posts one message saying so and edits the countdown, those still to verify get the new date, and the reminders follow it from now. Recorded as `telegram_group.window_extended`. Needs `org.integrations.edit`.