How do I set up RestoreCord on my Discord server?

To set up RestoreCord, invite the bot to your server, grant it the necessary permissions, and configure your server settings through the RestoreCord dashboard.

What data does RestoreCord back up?

RestoreCord backs up server settings, roles, channels, messages, and member data, ensuring comprehensive restoration capabilities.

How often should I back up my Discord server?

It's recommended to perform backups regularly, especially after significant changes, to ensure data is up-to-date.

Can RestoreCord restore deleted messages?

Yes, RestoreCord can restore deleted messages if they were included in the most recent backup.

Is my data secure with RestoreCord?

RestoreCord prioritizes data security, utilizing encryption and secure storage methods to protect your information.

What happens if I encounter a 'Missing Permissions' error?

A 'Missing Permissions' error indicates that RestoreCord lacks the necessary permissions to perform certain actions. Ensure the bot has the 'Administrator' permission or the specific permissions required for its functions.

Can I use RestoreCord to migrate members between servers?

Yes, RestoreCord allows you to pull members from one server to another, facilitating server migrations.

Does RestoreCord comply with Discord's Terms of Service?

RestoreCord is designed to comply with Discord's Terms of Service, ensuring safe and legitimate use.

How can I contact RestoreCord support?

For support, visit our contact page at https://restorecord.com/contact or join our Discord server for assistance.

Bots - RestoreCord Docs

Overview

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.

API-key responses do not expose bot tokens or client secrets. Treat all token and secret updates as credential rotation events.

List Bots

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

API key permission: READ_BOTS

GET/api/v3/bots

List bots

Return owned custom bot metadata.

Response

Example response JSON

{
  "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
}

Field: bots[].id
Type: number
Notes: Internal RestoreCord bot id.

Field: bots[].username
Type: string
Notes: Stored Discord bot username.

Field: bots[].clientId
Type: string
Notes: Discord application id.

Field: bots[].customDomain
Type: string | null
Notes: Custom verification domain when configured.

Field: bots[].domainStatus
Type: string | null
Notes: Domain status such as PENDING or ACTIVE.

Field: bots[].isPresetDomain
Type: boolean
Notes: Whether the domain is a RestoreCord preset domain.

Field: bots[].activity
Type: string | null
Notes: Configured bot presence text.

Field: bots[].activityType
Type: number | null
Notes: Discord activity type.

Field: total
Type: number
Notes: Number of returned bots.

Field	Type	Notes
`bots[].id`	number	Internal RestoreCord bot id.
`bots[].username`	string	Stored Discord bot username.
`bots[].clientId`	string	Discord application id.
`bots[].customDomain`	string \| null	Custom verification domain when configured.
`bots[].domainStatus`	string \| null	Domain status such as `PENDING` or `ACTIVE`.
`bots[].isPresetDomain`	boolean	Whether the domain is a RestoreCord preset domain.
`bots[].activity`	string \| null	Configured bot presence text.
`bots[].activityType`	number \| null	Discord activity type.
`total`	number	Number of returned bots.

Create Bot

Adds a Discord bot by validating the bot token against Discord, checking duplicate credentials, applying required application flags, registering the Discord deauthorization webhook, and starting the bot service asynchronously.

API key permission: WRITE_BOTS

POST/api/v3/bots

Create bot

botTokenRequired

Location: body
Type: string

Discord bot token.

botSecretRequired

Location: body
Type: string

Discord application client secret.

Parameter	Location	Type	Required
`botToken` Discord bot token.	body	string	Yes
`botSecret` Discord application client secret.	body	string	Yes

Plan: Free
Bot limit: 1

Plan: Premium
Bot limit: 5

Plan: Business / Enterprise
Bot limit: 50

Plan	Bot limit
Free	1
Premium	5
Business / Enterprise	50

Request

Example request JSON

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

Response

Example response JSON

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

Get Bot

Returns one owned bot by Discord client id. API-key auth receives the public bot response; session auth can receive the full owner response.

API key permission: READ_BOTS

GET/api/v3/bots/{botId}

Get bot

Return one owned bot record.

botIdRequired

Location: path
Type: string

Discord application/client id.

Parameter	Location	Type	Required
`botId` Discord application/client id.	path	string	Yes

Response

Example response JSON

{
  "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",
    "botToken": "DISCORD_BOT_TOKEN",
    "botSecret": "DISCORD_CLIENT_SECRET"
  },
  "isOwner": true
}

Use server-scoped bot helpers for sub-user flows. The direct bot record endpoint is owner-only.

Update Bot

Updates bot credentials and presence settings. If the bot token changes, RestoreCord verifies the token with Discord, updates the stored public key, restarts the bot service, and clears bot caches.

API key permission: WRITE_BOTS

PATCH/api/v3/bots/{botId}

Update bot

Update credentials or presence for one owned bot.

botIdRequired

Location: path
Type: string

Discord application/client id.

botSecretOptional

Location: body
Type: string

Replacement Discord client secret.

botTokenOptional

Location: body
Type: string

Replacement Discord bot token. Must belong to the bot selected by the path botId.

activityOptional

Location: body
Type: string | null

Presence text, max 128 characters.

activityTypeOptional

Location: body
Type: number | null

Discord activity type, 0-34.

Parameter	Location	Type	Required
`botId` Discord application/client id.	path	string	Yes
`botSecret` Replacement Discord client secret.	body	string	No
`botToken` Replacement Discord bot token. Must belong to the bot selected by the path botId.	body	string	No
`activity` Presence text, max 128 characters.	body	string \| null	No
`activityType` Discord activity type, 0-34.	body	number \| null	No

clientId and botId are not request body fields. botId is only the required URL path value in /api/v3/bots/{botId}.

Response

Example response JSON

{
  "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
  }
}

Activity value: 0
Common Discord meaning: Playing

Activity value: 1
Common Discord meaning: Streaming

Activity value: 2
Common Discord meaning: Listening

Activity value: 3
Common Discord meaning: Watching

Activity value: 5
Common Discord meaning: Competing

Activity value: 10
Common Discord meaning: Custom/status behavior used as the default in source.

Activity value	Common Discord meaning
`0`	Playing
`1`	Streaming
`2`	Listening
`3`	Watching
`5`	Competing
`10`	Custom/status behavior used as the default in source.

Delete Bot

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

API key permission: WRITE_BOTS

DELETE/api/v3/bots/{botId}

Delete bot

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

botIdRequired

Location: path
Type: string

Discord application/client id.

Parameter	Location	Type	Required
`botId` Discord application/client id.	path	string	Yes

Response

Example response JSON

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

If the bot is still used by servers, the route returns 409 RESOURCE_IN_USE with the server list that must be deleted or moved first.

Runtime Controls

Bot lifecycle desired state is written through Convex-backed runtime controls. The routes are owner-authenticated and require WRITE_BOTS for API keys.

Endpoint: POST /api/v3/bots/{botId}/runtime/start
Purpose: Queue a bot start command.

Endpoint: POST /api/v3/bots/{botId}/runtime/stop
Purpose: Queue a bot stop command.

Endpoint: POST /api/v3/bots/{botId}/runtime/restart
Purpose: Queue stop then start commands for the runtime.

Endpoint	Purpose
`POST /api/v3/bots/{botId}/runtime/start`	Queue a bot start command.
`POST /api/v3/bots/{botId}/runtime/stop`	Queue a bot stop command.
`POST /api/v3/bots/{botId}/runtime/restart`	Queue stop then start commands for the runtime.

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

Restart bot

Queue a restart through the Convex runtime control plane.

botIdRequired

Location: path
Type: string

Discord application/client id.

Parameter	Location	Type	Required
`botId` Discord application/client id.	path	string	Yes

Example response JSON

{
  "success": true,
  "message": "Bot restart queued",
  "stopCommandId": "stop:123456789012345678:1781690000000",
  "startCommandId": "start:123456789012345678:1781690000001"
}

Guild Helpers

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

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

List bot guilds

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

botIdRequired

Location: path
Type: string

Discord application/client id.

Parameter	Location	Type	Required
`botId` Discord application/client id.	path	string	Yes

List Guilds Response

Example response JSON

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

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

Leave guilds

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

botIdRequired

Location: path
Type: string

Discord application/client id.

guildIdsRequired

Location: body
Type: string[]

Discord guild ids, 1-50 items.

Parameter	Location	Type	Required
`botId` Discord application/client id.	path	string	Yes
`guildIds` Discord guild ids, 1-50 items.	body	string[]	Yes

Leave Guilds Response

Example response JSON

{
  "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"
    }
  ]
}

Guild lists are cached briefly.
Leave operations run one guild at a time with spacing between Discord requests.
A partial failure returns per-guild result rows.

Status and Errors

Status/code: 200
When it appears: Successful list, get, update, or guild response.

Status/code: 201
When it appears: Bot created.

Status/code: 400 MISSING_FIELD
When it appears: Required bot token, secret, or guild list missing.

Status/code: 400 INVALID_INPUT / VALIDATION_ERROR
When it appears: Invalid token format, read-only client id in an update body, invalid activity, or guild id.

Status/code: 400 INVALID_CREDENTIALS
When it appears: Discord rejects the bot token or the token does not match the client id.

Status/code: 403 FORBIDDEN
When it appears: Missing API-key permission or plan limit reached.

Status/code: 404 NOT_FOUND
When it appears: Bot or guild resource is not accessible.

Status/code: 409 DUPLICATE_RESOURCE
When it appears: Bot token, client secret, or client id is already registered.

Status/code: 409 RESOURCE_IN_USE
When it appears: Bot deletion blocked because RestoreCord servers still use it.

Status/code: 429 / 503 RATE_LIMITED
When it appears: RestoreCord or Discord rate limiting.

Status/code: 502 EXTERNAL_SERVICE_ERROR
When it appears: Discord API failure.

Status/code	When it appears
`200`	Successful list, get, update, or guild response.
`201`	Bot created.
`400 MISSING_FIELD`	Required bot token, secret, or guild list missing.
`400 INVALID_INPUT` / `VALIDATION_ERROR`	Invalid token format, read-only client id in an update body, invalid activity, or guild id.
`400 INVALID_CREDENTIALS`	Discord rejects the bot token or the token does not match the client id.
`403 FORBIDDEN`	Missing API-key permission or plan limit reached.
`404 NOT_FOUND`	Bot or guild resource is not accessible.
`409 DUPLICATE_RESOURCE`	Bot token, client secret, or client id is already registered.
`409 RESOURCE_IN_USE`	Bot deletion blocked because RestoreCord servers still use it.
`429` / `503 RATE_LIMITED`	RestoreCord or Discord rate limiting.
`502 EXTERNAL_SERVICE_ERROR`	Discord API failure.