Read the org's own Discord app and Telegram bot
What the org set: each bot's ids and names, how many servers or groups it serves, and what to set in Discord's portal. Never its token or client secret. Needs `org.integrations.view`.
/v1/orgs/{org}/own-botsWhat the org set: each bot's ids and names, how many servers or groups it serves, and what to set in Discord's portal. Never its token or client secret. Needs org.integrations.view.
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}$Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X GET "https://api.synq.build/v1/orgs/org_01h455vb4pex5vsknk084sn02q/own-bots" \ -H "Authorization: Bearer $SYNQ_API_KEY"{ "discord": { "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" }, "telegram": { "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" }}Remove the org's own Discord app or Telegram bot DELETE
Disconnects every server or group it serves (the list's `serves` says how many), from now on: whoever holds a role or is in a group keeps it, and nobody is checked there again. The bot leaves each of them, best effort. Connecting them again with Synq's bot starts afresh. Never wants the plan, so an org that moved down can still remove it. Needs `org.integrations.edit`. Recorded as `own_bot.removed`.
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`.