REST API v1 · Developers · API reference

Ban appeals API reference

All 4 Ban appeals endpoints of the BotGG REST API v1: scopes, parameters, fields, errors and ready-to-run curl, JavaScript and Python examples.

Developer docs
On this page

Endpoints

Paths are relative to https://console.botgg.app/api/v1. Send your API key as Authorization: Bearer botgg_…; IDs are strings.

Ban appeals endpoints
EndpointScopeDescription
GET/guilds/{guildId}/appealsappeals:readList ban appeals
GET/guilds/{guildId}/appeals/{number}appeals:readGet a ban appeal
POST/guilds/{guildId}/appeals/{number}/approveappeals:writeApprove a ban appeal (unban)
POST/guilds/{guildId}/appeals/{number}/rejectappeals:writeReject a ban appeal

Besides its own errors below, every endpoint can return these common ones:

List ban appeals

GET/guilds/{guildId}/appeals

Scope: appeals:read

Newest first. status=open (default) = open + waiting for the user’s answer; all = every status. Pass before=<nextCursor> for the next page.

Needs this feature enabled on the server: Ban appeals

Parameters
NameInTypeRequiredDescription
guildIdpathstringYesYour server’s ID · Discord ID (string)
statusquerystringNoOne of open, question, approved, rejected, closed, all · Default "open"
userIdquerystringNoOnly this user’s appeals
Discord ID (string)
limitqueryintegerNo1–100 · Default 25
beforequeryintegerNo1–999,999,999

Response

Response fields · 200
FieldTypeRequiredDescription
itemsarray of objectYes
items[].numberintegerYes
items[].userIdstringYes
items[].userTagstring | nullYes
items[].statusstringYesOne of open, question, approved, rejected, closed
items[].banCaseNumberinteger | nullYes
items[].claimedBystring | nullYes
items[].decidedBystring | nullYesnull = system / API
items[].decidedAtstring | nullYesISO 8601 date-time
items[].reasonstring | nullYes
items[].createdAtstring | nullYesISO 8601 date-time
items[].lastActivityAtstring | nullYesISO 8601 date-time
nextCursorstring | nullYes
Response · 200
{
  "items": [
    {
      "number": 7,
      "userId": "876543210987654321",
      "userTag": "example",
      "status": "open",
      "banCaseNumber": 10,
      "claimedBy": "example",
      "decidedBy": "example",
      "decidedAt": "2026-10-07T12:00:00.000Z",
      "reason": "Tournament prize",
      "createdAt": "2026-10-07T12:00:00.000Z",
      "lastActivityAt": "2026-10-07T12:00:00.000Z"
    }
  ],
  "nextCursor": "98700"
}

Examples

curl
curl -s "https://console.botgg.app/api/v1/guilds/123456789012345678/appeals?status=open&limit=25" \
  -H "Authorization: Bearer $BOTGG_API_KEY"
JavaScript (fetch)
// Node.js 18+ (built-in fetch) — on your server, never in a browser
const res = await fetch('https://console.botgg.app/api/v1/guilds/123456789012345678/appeals?status=open&limit=25', {
  method: 'GET',
  headers: {
    Authorization: `Bearer ${process.env.BOTGG_API_KEY}`,
  },
});
const data = await res.json();
if (!res.ok) throw new Error(`${res.status} ${data.error}: ${data.message}`);
console.log(data);
Python (requests)
import os
import requests

res = requests.get(
    "https://console.botgg.app/api/v1/guilds/123456789012345678/appeals",
    headers={
        "Authorization": f"Bearer {os.environ['BOTGG_API_KEY']}",
    },
    params={
        "status": "open",
        "limit": 25,
    },
    timeout=10,
)
data = res.json()
if not res.ok:
    raise RuntimeError(f"{res.status_code} {data['error']}: {data['message']}")
print(data)

Errors

Get a ban appeal

GET/guilds/{guildId}/appeals/{number}

Scope: appeals:read

With the answers, the ban reason and the conversation the appellant sees. Internal staff notes are never returned.

Needs this feature enabled on the server: Ban appeals

Parameters
NameInTypeRequiredDescription
guildIdpathstringYesYour server’s ID · Discord ID (string)
numberpathstringYes

Response

Response fields · 200
FieldTypeRequiredDescription
numberintegerYes
userIdstringYes
userTagstring | nullYes
statusstringYesOne of open, question, approved, rejected, closed
banCaseNumberinteger | nullYes
claimedBystring | nullYes
decidedBystring | nullYesnull = system / API
decidedAtstring | nullYesISO 8601 date-time
reasonstring | nullYes
createdAtstring | nullYesISO 8601 date-time
lastActivityAtstring | nullYesISO 8601 date-time
banReasonstring | nullYes
answersarray of objectYes
answers[].idstringYes
answers[].typestringYes
answers[].labelstringYes
answers[].valueanyYes
messagesarray of objectYesThe conversation the appellant sees (staff questions + replies). Internal notes are never included.
messages[].authorstringYesOne of user, staff
messages[].authorIdstring | nullYes
messages[].textstringYes
messages[].createdAtstring | nullYesISO 8601 date-time
applyingbooleanYesA console/API decision is still being applied in Discord
failedActionobject | nullYes
failedAction.typestringYes
failedAction.errorstring | nullYes
Response · 200
{
  "number": 7,
  "userId": "876543210987654321",
  "userTag": "example",
  "status": "open",
  "banCaseNumber": 10,
  "claimedBy": "example",
  "decidedBy": "example",
  "decidedAt": "2026-10-07T12:00:00.000Z",
  "reason": "Tournament prize",
  "createdAt": "2026-10-07T12:00:00.000Z",
  "lastActivityAt": "2026-10-07T12:00:00.000Z",
  "banReason": "example",
  "answers": [
    {
      "id": "example",
      "type": "example",
      "label": "Example",
      "value": null
    }
  ],
  "messages": [
    {
      "author": "user",
      "authorId": "234567890123456789",
      "text": "Example answer",
      "createdAt": "2026-10-07T12:00:00.000Z"
    }
  ],
  "applying": true,
  "failedAction": {
    "type": "example",
    "error": "example"
  }
}

Examples

curl
curl -s "https://console.botgg.app/api/v1/guilds/123456789012345678/appeals/234567890123456789" \
  -H "Authorization: Bearer $BOTGG_API_KEY"
JavaScript (fetch)
// Node.js 18+ (built-in fetch) — on your server, never in a browser
const res = await fetch('https://console.botgg.app/api/v1/guilds/123456789012345678/appeals/234567890123456789', {
  method: 'GET',
  headers: {
    Authorization: `Bearer ${process.env.BOTGG_API_KEY}`,
  },
});
const data = await res.json();
if (!res.ok) throw new Error(`${res.status} ${data.error}: ${data.message}`);
console.log(data);
Python (requests)
import os
import requests

res = requests.get(
    "https://console.botgg.app/api/v1/guilds/123456789012345678/appeals/234567890123456789",
    headers={
        "Authorization": f"Bearer {os.environ['BOTGG_API_KEY']}",
    },
    timeout=10,
)
data = res.json()
if not res.ok:
    raise RuntimeError(f"{res.status_code} {data['error']}: {data['message']}")
print(data)

Errors

Approve a ban appeal (unban)

POST/guilds/{guildId}/appeals/{number}/approve

Scope: appeals:writeSensitiveIdempotency-Key

Same as Approve in the console: the bot unbans within a few seconds (an unban moderation case when Moderation is enabled), creates a single-use invite and DMs the user per the appeal settings. Written to the audit log.

Needs this feature enabled on the server: Ban appeals

Parameters
NameInTypeRequiredDescription
guildIdpathstringYesYour server’s ID · Discord ID (string)
numberpathstringYes
Idempotency-KeyheaderstringNoOptional. Send a unique value (a UUID) and reuse it when you retry: the change happens only once. How it works

Request body

Request body
FieldTypeRequiredDescription
reasonstring | nullNoSent to the appellant (DM / appeal page)
up to 1,000 characters

Response

Response fields · 202
FieldTypeRequiredDescription
numberintegerYes
userIdstringYes
userTagstring | nullYes
statusstringYesOne of open, question, approved, rejected, closed
banCaseNumberinteger | nullYes
claimedBystring | nullYes
decidedBystring | nullYesnull = system / API
decidedAtstring | nullYesISO 8601 date-time
reasonstring | nullYes
createdAtstring | nullYesISO 8601 date-time
lastActivityAtstring | nullYesISO 8601 date-time
banReasonstring | nullYes
answersarray of objectYes
answers[].idstringYes
answers[].typestringYes
answers[].labelstringYes
answers[].valueanyYes
messagesarray of objectYesThe conversation the appellant sees (staff questions + replies). Internal notes are never included.
messages[].authorstringYesOne of user, staff
messages[].authorIdstring | nullYes
messages[].textstringYes
messages[].createdAtstring | nullYesISO 8601 date-time
applyingbooleanYesA console/API decision is still being applied in Discord
failedActionobject | nullYes
failedAction.typestringYes
failedAction.errorstring | nullYes
Response · 202
{
  "number": 7,
  "userId": "876543210987654321",
  "userTag": "example",
  "status": "open",
  "banCaseNumber": 10,
  "claimedBy": "example",
  "decidedBy": "example",
  "decidedAt": "2026-10-07T12:00:00.000Z",
  "reason": "Tournament prize",
  "createdAt": "2026-10-07T12:00:00.000Z",
  "lastActivityAt": "2026-10-07T12:00:00.000Z",
  "banReason": "example",
  "answers": [
    {
      "id": "example",
      "type": "example",
      "label": "Example",
      "value": null
    }
  ],
  "messages": [
    {
      "author": "user",
      "authorId": "234567890123456789",
      "text": "Example answer",
      "createdAt": "2026-10-07T12:00:00.000Z"
    }
  ],
  "applying": true,
  "failedAction": {
    "type": "example",
    "error": "example"
  }
}

Examples

curl
curl -s -X POST "https://console.botgg.app/api/v1/guilds/123456789012345678/appeals/234567890123456789/approve" \
  -H "Authorization: Bearer $BOTGG_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"reason":"Tournament prize"}'
JavaScript (fetch)
// Node.js 18+ (built-in fetch) — on your server, never in a browser
const res = await fetch('https://console.botgg.app/api/v1/guilds/123456789012345678/appeals/234567890123456789/approve', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.BOTGG_API_KEY}`,
    'Content-Type': 'application/json',
    'Idempotency-Key': crypto.randomUUID(), // reuse it when you retry this request
  },
  body: JSON.stringify({
    reason: 'Tournament prize',
  }),
});
const data = await res.json();
if (!res.ok) throw new Error(`${res.status} ${data.error}: ${data.message}`);
console.log(data);
Python (requests)
import os, uuid
import requests

res = requests.post(
    "https://console.botgg.app/api/v1/guilds/123456789012345678/appeals/234567890123456789/approve",
    headers={
        "Authorization": f"Bearer {os.environ['BOTGG_API_KEY']}",
        "Idempotency-Key": str(uuid.uuid4()),  # reuse it when you retry this request
    },
    json={
        "reason": "Tournament prize",
    },
    timeout=10,
)
data = res.json()
if not res.ok:
    raise RuntimeError(f"{res.status_code} {data['error']}: {data['message']}")
print(data)

Errors

Reject a ban appeal

POST/guilds/{guildId}/appeals/{number}/reject

Scope: appeals:writeSensitiveIdempotency-Key

Same as Reject in the console: the user gets the rejection DM per the appeal settings and the re-appeal cooldown starts. Written to the audit log.

Needs this feature enabled on the server: Ban appeals

Parameters
NameInTypeRequiredDescription
guildIdpathstringYesYour server’s ID · Discord ID (string)
numberpathstringYes
Idempotency-KeyheaderstringNoOptional. Send a unique value (a UUID) and reuse it when you retry: the change happens only once. How it works

Request body

Request body
FieldTypeRequiredDescription
reasonstring | nullNoSent to the appellant (DM / appeal page)
up to 1,000 characters

Response

Response fields · 202
FieldTypeRequiredDescription
numberintegerYes
userIdstringYes
userTagstring | nullYes
statusstringYesOne of open, question, approved, rejected, closed
banCaseNumberinteger | nullYes
claimedBystring | nullYes
decidedBystring | nullYesnull = system / API
decidedAtstring | nullYesISO 8601 date-time
reasonstring | nullYes
createdAtstring | nullYesISO 8601 date-time
lastActivityAtstring | nullYesISO 8601 date-time
banReasonstring | nullYes
answersarray of objectYes
answers[].idstringYes
answers[].typestringYes
answers[].labelstringYes
answers[].valueanyYes
messagesarray of objectYesThe conversation the appellant sees (staff questions + replies). Internal notes are never included.
messages[].authorstringYesOne of user, staff
messages[].authorIdstring | nullYes
messages[].textstringYes
messages[].createdAtstring | nullYesISO 8601 date-time
applyingbooleanYesA console/API decision is still being applied in Discord
failedActionobject | nullYes
failedAction.typestringYes
failedAction.errorstring | nullYes
Response · 202
{
  "number": 7,
  "userId": "876543210987654321",
  "userTag": "example",
  "status": "open",
  "banCaseNumber": 10,
  "claimedBy": "example",
  "decidedBy": "example",
  "decidedAt": "2026-10-07T12:00:00.000Z",
  "reason": "Tournament prize",
  "createdAt": "2026-10-07T12:00:00.000Z",
  "lastActivityAt": "2026-10-07T12:00:00.000Z",
  "banReason": "example",
  "answers": [
    {
      "id": "example",
      "type": "example",
      "label": "Example",
      "value": null
    }
  ],
  "messages": [
    {
      "author": "user",
      "authorId": "234567890123456789",
      "text": "Example answer",
      "createdAt": "2026-10-07T12:00:00.000Z"
    }
  ],
  "applying": true,
  "failedAction": {
    "type": "example",
    "error": "example"
  }
}

Examples

curl
curl -s -X POST "https://console.botgg.app/api/v1/guilds/123456789012345678/appeals/234567890123456789/reject" \
  -H "Authorization: Bearer $BOTGG_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"reason":"Tournament prize"}'
JavaScript (fetch)
// Node.js 18+ (built-in fetch) — on your server, never in a browser
const res = await fetch('https://console.botgg.app/api/v1/guilds/123456789012345678/appeals/234567890123456789/reject', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.BOTGG_API_KEY}`,
    'Content-Type': 'application/json',
    'Idempotency-Key': crypto.randomUUID(), // reuse it when you retry this request
  },
  body: JSON.stringify({
    reason: 'Tournament prize',
  }),
});
const data = await res.json();
if (!res.ok) throw new Error(`${res.status} ${data.error}: ${data.message}`);
console.log(data);
Python (requests)
import os, uuid
import requests

res = requests.post(
    "https://console.botgg.app/api/v1/guilds/123456789012345678/appeals/234567890123456789/reject",
    headers={
        "Authorization": f"Bearer {os.environ['BOTGG_API_KEY']}",
        "Idempotency-Key": str(uuid.uuid4()),  # reuse it when you retry this request
    },
    json={
        "reason": "Tournament prize",
    },
    timeout=10,
)
data = res.json()
if not res.ok:
    raise RuntimeError(f"{res.status_code} {data['error']}: {data['message']}")
print(data)

Errors

Ready to level up your server?

Add BotGG for free, then switch features on in the web console.