Bots

OverviewCopy Anchor Link

Bot endpoints manage custom Discord applications connected to RestoreCord. API-key auth can list, create, read, update, and delete owned bot records when the key has the required bot permissions.

List BotsCopy Anchor Link

Returns custom bots owned by the authenticated account, ordered newest first.

Auth: API key with READ_BOTS.

Return owned custom bot metadata.

GET /api/v3/bots

ResponseCopy Anchor Link

{
  "success": true,
  "bots": [
    {
      "id": 42,
      "username": "RestoreBot#0000",
      "clientId": "123456789012345678",
      "customDomain": "verify.example.com",
      "domainStatus": "ACTIVE",
      "isPresetDomain": false,
      "activity": "your server",
      "activityType": 10,
      "createdAt": "2026-06-07T10:00:00.000Z"
    }
  ],
  "total": 1
}

Create BotCopy Anchor Link

Adds a Discord bot. RestoreCord checks the bot token with Discord, rejects credentials that are already registered, and starts the bot.

Auth: API key with WRITE_BOTS.

Register a Discord application bot with RestoreCord.

POST /api/v3/bots

RequestCopy Anchor Link

{
  "botToken": "DISCORD_BOT_TOKEN",
  "botSecret": "DISCORD_CLIENT_SECRET"
}

ResponseCopy Anchor Link

{
  "success": true,
  "message": "Bot created successfully.",
  "bot": {
    "id": 42,
    "name": "RestoreBot#0000",
    "clientId": "123456789012345678"
  }
}

Get BotCopy Anchor Link

Returns one owned bot by Discord client id. The response never includes the bot token or client secret.

Auth: API key with READ_BOTS.

Return one owned bot record.

GET /api/v3/bots/{botId}

ResponseCopy Anchor Link

{
  "success": true,
  "bot": {
    "id": 42,
    "username": "RestoreBot#0000",
    "clientId": "123456789012345678",
    "customDomain": "verify.example.com",
    "domainStatus": "ACTIVE",
    "isPresetDomain": false,
    "activity": "your server",
    "activityType": 10,
    "createdAt": "2026-06-07T10:00:00.000Z"
  },
  "isOwner": true
}

Update BotCopy Anchor Link

Updates bot credentials and presence settings. If the bot token changes, RestoreCord verifies the token with Discord and restarts the bot.

Auth: API key with WRITE_BOTS.

Update credentials or presence for one owned bot.

PATCH /api/v3/bots/{botId}

ResponseCopy Anchor Link

{
  "success": true,
  "message": "Bot successfully updated.",
  "bot": {
    "id": 42,
    "username": "RestoreBot#0000",
    "clientId": "123456789012345678",
    "customDomain": "verify.example.com",
    "domainStatus": "ACTIVE",
    "activity": "your server",
    "activityType": 10
  }
}

Delete BotCopy Anchor Link

Deletes an owned custom bot only when no RestoreCord servers still use it.

Auth: API key with WRITE_BOTS.

Delete one owned bot if it is not attached to any RestoreCord servers.

DELETE /api/v3/bots/{botId}

ResponseCopy Anchor Link

{
  "success": true,
  "message": "Bot successfully deleted."
}

Runtime ControlsCopy Anchor Link

Runtime controls start, stop, or restart a bot. The routes only accept bots owned by the API key's account.

Auth: API key with WRITE_BOTS.

Restart botCopy Anchor Link

Restart the bot. Make sure Server Members Intent is enabled in the Developer Portal.

POST /api/v3/bots/{botId}/runtime/restart

{
  "success": true,
  "message": "Bot restart requested"
}

Guild HelpersCopy Anchor Link

Guild helpers use the bot token to list or leave Discord servers. Owners can list all guilds; accounts with sub-user pull-member access to a server using the bot receive only accessible guilds.

Auth: API key with READ_BOTS to list guilds, or WRITE_BOTS to leave them.

List bot guildsCopy Anchor Link

Return Discord guilds the bot is in, sorted by approximate member count.

GET /api/v3/bots/{botId}/guilds

List Guilds ResponseCopy Anchor Link

{
  "success": true,
  "guilds": [
    {
      "id": "111111111111111111",
      "name": "Community",
      "icon": null,
      "owner": false,
      "permissions": "278032280691",
      "memberCount": 1200
    }
  ],
  "total": 1
}

Leave guildsCopy Anchor Link

Owner-only helper that asks the bot to leave up to 50 guilds.

POST /api/v3/bots/{botId}/guilds

Leave Guilds ResponseCopy Anchor Link

{
  "success": true,
  "message": "Successfully left 1 of 1 guilds",
  "summary": {
    "total": 1,
    "successful": 1,
    "failed": 0
  },
  "results": [
    {
      "guildId": "111111111111111111",
      "success": true,
      "message": "Successfully left guild"
    }
  ]
}

• A partial failure returns per-guild result rows.
• More than 50 ids returns 400 VALIDATION_ERROR with the message Maximum 50 guilds can be left at once, and the bot leaves none of them. To leave more, send the ids in batches of 50.

Status and ErrorsCopy Anchor Link