SynqDocs
Management APIOwn bots

Remove the org's own Discord app or Telegram bot

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`.

DELETE/v1/orgs/{org}/own-bots/{platform}

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.

Authorization

bearer
AuthorizationBearer <token>

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

org*string

The org's id

Match^org_[0-9a-hjkmnp-tv-z]{26}$
platform*string

discord or telegram

Value in

  • "discord"
  • "telegram"

Response Body

application/problem+json

application/problem+json

application/problem+json

application/problem+json

curl -X DELETE "https://api.synq.build/v1/orgs/org_01h455vb4pex5vsknk084sn02q/own-bots/discord" \  -H "Authorization: Bearer $SYNQ_API_KEY"
Empty