Set the org's own Telegram bot
A Telegram bot of the org's own serves the groups it connects (`POST …/telegram-groups/connect` with `own_bot: true`) in place of Synq's: its name and picture in the group and in what it writes to people. Checked with Telegram first (getMe; 400 at `token` with the fix, 503 when Telegram doesn't answer), its token sealed and never shown again, and its webhook pointed at Synq with a secret of its own. To be a group's guard bot, turn on join request queries for it in @BotFather. Sending the same bot again replaces its token; another bot can't replace one that still serves groups (409). Needs `org.integrations.edit` and a plan with `integration.own_bots` (Scale and up). Recorded as `own_bot.set`.
/v1/orgs/{org}/own-bots/telegramA Telegram bot of the org's own serves the groups it connects (POST …/telegram-groups/connect with own_bot: true) in place of Synq's: its name and picture in the group and in what it writes to people. Checked with Telegram first (getMe; 400 at token with the fix, 503 when Telegram doesn't answer), its token sealed and never shown again, and its webhook pointed at Synq with a secret of its own. To be a group's guard bot, turn on join request queries for it in @BotFather. Sending the same bot again replaces its token; another bot can't replace one that still serves groups (409). Needs org.integrations.edit and a plan with integration.own_bots (Scale and up). Recorded as own_bot.set.
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}$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
application/problem+json
application/problem+json
application/problem+json
curl -X PUT "https://api.synq.build/v1/orgs/org_01h455vb4pex5vsknk084sn02q/own-bots/telegram" \ -H "Authorization: Bearer $SYNQ_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "token": "string" }'{ "id": "bot_01h455vb4pex5vsknk084sn02q", "platform": "discord", "external_id": "1203847562019384756", "name": "Mollyverse Bot", "username": "MollyverseBot", "serves": 0, "setup": { "interactions_endpoint_url": "https://app.acme.example", "redirect_uri": "https://app.acme.example", "webhook_url": "https://app.acme.example" }, "created_at": "2026-10-21T12:00:00.000Z", "updated_at": "2026-10-21T12:00:00.000Z"}Set the org's own Discord app PUT
A Discord app of the org's own serves the servers it adds (`POST …/discord-servers/install` with `own_bot: true`) in place of Synq's: its install screen, its name and picture. Checked with Discord first: the token must be the bot of the app `application_id` names, and `public_key` that app's key (400 at the field with the fix; 503 when Discord doesn't answer). Its token and client secret are sealed, never shown again. Then set the answer's `setup.interactions_endpoint_url` as the app's Interactions Endpoint URL and add `setup.redirect_uri` on its OAuth2 page. Sending the same app again replaces its credentials; another app can't replace one that still serves servers (409). Needs `org.integrations.edit` and a plan with `integration.own_bots` (Scale and up). Recorded as `own_bot.set`.
Remove a user's passkey DELETE
It stops signing them in at once, even when it was their last way to sign in: a stolen device's passkey has to be removable, and the tenant decides what comes next (another way in, or disabling the user). Sessions it signed in keep going: end them with `revoke-sessions`. Needs `org.users.edit`. Recorded as `user.passkey_removed`, `by: management_api`.