Ticket Transcript

Overview

Create and retrieve Discord ticket transcripts. Messages are formatted into a .txt transcript with Discord usernames and display names resolved server-side via the Discord API. Stored in MongoDB and served as plain text. The POST endpoint requires authentication, while the GET endpoint is public.

Auth required + No auth required

Authentication

Include your API key in the Authorization header as a Bearer token with the BDTools- prefix for authenticated endpoints.

// Authorization header format
Authorization: Bearer BDTools-YOUR_API_KEY_HERE

Rate Limits & Restrictions

▸ POST /ticket-transcript is not rate limited.
▸ GET /t/{hash} is public and requires no authentication.

// Base URL for transcript creation
https://api.bdtools.xyz

POST /ticket-transcript

Creates a ticket transcript from raw message data. Accepts a JSON body with channelId, channelName, guildName, authorId, botId, and a messages array. Each message should be formatted as userId | content. The endpoint resolves all user IDs via the Discord API, formats the results into a readable transcript, stores it in MongoDB, and returns a shareable URL.

Auth required Rate limit: None

Headers

Header	Value
Authorization	`Bearer BDTools-YOUR_API_KEY`

Request Body

{
  "channelId": "123456789012345678",
  "channelName": "ticket-0042",
  "guildName": "My Cool Server",
  "authorId": "111222333444555666",
  "botId": "123456789012345678",
  "messages": [
    "111222333444555666 | hey i need help with my purchase",
    "999888777666555444 | sure what seems to be the issue",
    "111222333444555666 | i got charged twice",
    "999888777666555444 | let me look into that for you"
  ]
}

Responses

200 OK

{
  "url": "https://cdn.bdtools.xyz/t/a1b2c3d4e5f6g7h8"
}

400 Bad Request — Missing Fields

{ "error": "Missing required fields: channelId, channelName, guildName, authorId, botId, messages." }

400 Bad Request — Invalid JSON

{ "error": "Invalid JSON in request body." }

401 Unauthorized

{ "error": "Invalid or missing API key." }

405 Method Not Allowed

{ "error": "Method not allowed. Use POST." }

500 Internal Server Error — Database Connection

{ "error": "Database connection failed." }

Paste this into a BDFD command to automatically generate a ticket transcript when a ticket is closed. Full credit for the example code goes to Catearo.

BDFD Code

$nomention
$c[Replace this or add this variable in the app with the author/person who makes the ticket.]
$var[aid;$getUserVar[ticketAuthorId]]
$var[key;YOUR_API_KEY_HERE]

$c[DO NOT CHANGE ANYTHING FROM THIS POINT ONWARDS]
$defer
$var[i;0]
$jsonParse[[\]]
$var[code;.try .var(lastMsgID,.optOff(.lastMessageID)) .jsonArrayAppend(,.getMessage(.channelID,.var(lastMsgID),authorID) | .getMessage(.channelID,.var(lastMsgID),content)) .deleteMessage(.channelID,.var(lastMsgID)) .endtry]
$var[code;$replaceText[$replaceText[$replaceText[$replaceText[$var[code];.;$];,;\;];(;[]););\]]]
$eval[$repeatMessage[2;$repeatMessage[10;$repeatMessage[10;$var[code]]]]]
$httpAddHeader[Authorization;Bearer $var[key]]
$httpPost[https://api.bdtools.xyz/ticket-transcript;{
  "channelId": "$channelID",
  "channelName": "$channelName[$channelID]",
  "guildName": "$serverName[$guildID]",
  "authorId": "$getUserVar[$var[aid]]",
  "botId": "$botID",
  "messages": $jsonStringify
}]

$c[You can edit these messages below:]

$c[The DM channel ID of the person who made the ticket]
$var[id;$dmChannelID[$getUserVar[$var[aid]]]]
$c[Message to send]
$var[msg;Here is your ticket transcript, thank you for contacting support ❤️]
$c[The output URL]
$var[url;$httpResult[url]]

$c[The message that is sent to the person who made the ticket via DM]
$channelSendMessage[$var[id];$var[msg]
$var[url]]

$c[Add more stuff here maybe send the transcript url to a staff channel or anything else.]

API Key: Replace YOUR_API_KEY_HERE with your BDTools API key. Get your key at api.bdtools.xyz by signing in with Discord. The key expires every 30 days, visit api.bdtools.xyz to refresh it.

Known Limitations

▸
Always loops 200 times: the loop always runs 200 iterations (maximum limit) regardless of how many messages are in the channel, 1 message or 200 takes the same ~3 minutes. It's a BDFD limitation, there's no early exit.
▸
Embeds/Images show as placeholder: Embeds and Images cannot be fetched using $getMessage in BDFD, so they'll appear as [embed/image, could not be retrieved] instead.
▸
Keeps deleting after the ticket is closed: since the loop can't be stopped mid-way, it will keep deleting messages even after the ticket is fully closed. If someone sends a message while the loop is still running, that message will get deleted too.
▸
Same channel = transcript gets overwritten: the URL is tied to the channel ID, so if you reuse a channel for a new ticket, the old transcript is gone.

GET cdn.bdtools.xyz/t/{hash}

Retrieve a stored transcript as plain text. The URL is returned by the create endpoint. The hash is a 16-character hex string derived from SHA-256 of the channel ID.

No auth required Rate limit: None

URL Format

https://cdn.bdtools.xyz/t/a1b2c3d4e5f6g7h8

Responses

200 OK

Content-Type: text/plain

Transcript for #ticket-0042 (My Cool Server)
Ticket Author: John (john)
Date: 2026-05-25

John (john): hey i need help with my purchase
Jane (jane): sure what seems to be the issue
John (john): i got charged twice
Jane (jane): let me look into that for you
John (john): thanks!

404 Not Found

Transcript not found.

Ticket Transcript

Overview

Authentication

Rate Limits & Restrictions

Headers

Request Body

Responses

Example BDFD Command

Known Limitations

URL Format

Responses