No requests sent — client-side only

Payload Builder

Fill in only the fields you need. Empty fields are excluded from the JSON automatically. Copy and paste into your BDFD bot or HTTP client.

POST https://ulquiorracifer.xyz/api/transcript Content-Type: application/json
🔑 Core 0 / 5
botToken required
Your Discord bot token
channelId required
Ticket channel ID
transcriptChannelId
Where transcript is posted
ticketId
Unique ticket ID
ticketCreatorId
User who opened the ticket
ticketCloserId
User who closed the ticket
👥 User & Ticket Data 0 / 3
supportRoles
Comma-separated role IDs → array
claimedBy
Staff member who claimed ticket
ticketType
Category of the ticket
📝 Transcript Config 0 / 4
includeMessages
Include message content
includeAttachments
Include file attachments
includeEmbeds
Include message embeds
saveImages
Save image attachments
🎨 Embed Customization 0 / 7
✦ Embed Templates Hover to flip · Click to apply
Standard
Plain text · Exact example format
My Server Ticket Transcript
Opened by: @UserName
Users: @UserName, @Staff
Channel ID: 123456789
Channel Name: ticket-0042
Closed by: @StaffName
Hover to preview · Click to apply
Standard
The base format. Opener, all users, channel ID, channel name, closer — exactly the layout from the example.
serverNameticketOpenerusersticketChannelIDchannelNameticketCloser
↩ Click to apply
Bold Fields
Markdown bold · Channel inline
📋 Transcript | ticket-0042
Opened by: @UserName
Closed by: @StaffName
Users involved: @UserName, @Staff
Channel: ticket-0042 (123456789)
Hover to preview · Click to apply
Bold Fields
Same data but with Discord bold markdown. Channel name and ID shown inline on one line. Full date footer.
channelNameticketOpenerticketCloserusersticketChannelIDserverName
↩ Click to apply
Channel First
Channel info at top · Participants below
🛡️ My Server — Ticket Log
Channel: ticket-0042
Channel ID: 123456789

Ticket Opener: @UserName
Ticket Closer: @StaffName
Participants: @UserName, @Staff
Hover to preview · Click to apply
Channel First
Channel info at the top, then opener / closer / all users below. Good for logs sorted by channel.
serverNamechannelNameticketChannelIDticketOpenerticketCloserusers
↩ Click to apply
Sentence Style
Natural prose · Less formal
Transcript — ticket-0042
@UserName opened this ticket.
@StaffName closed this ticket.

All users: @UserName, @Staff
Channel ID: 123456789
Hover to preview · Click to apply
Sentence Style
Reads as natural sentences instead of label: value pairs. More conversational, less corporate. Relative timestamp.
channelNameticketOpenerticketCloserusersticketChannelIDserverName
↩ Click to apply
Full Archive
All fields · Long-term log channels
📁 My Server · Archived Transcript
Server: My Server
Channel: ticket-0042
Channel ID: 123456789

Opened by: @UserName
Closed by: @StaffName
Users: @UserName, @Staff
Hover to preview · Click to apply
Full Archive
Every field in one embed. Server name, channel, channel ID, opener, closer, all users. Ideal for archive channels.
serverNamechannelNameticketChannelIDticketOpenerticketCloserusers
↩ Click to apply
Compact
Server · Channel in title
My Server · ticket-0042
Opened by @UserName and closed by @StaffName.

Participants: @UserName, @Staff
Channel ID: 123456789
Hover to preview · Click to apply
Compact
Server and channel in the title, prose sentence for opener/closer, then participants and channel ID. Short and clean.
serverNamechannelNameticketOpenerticketCloserusersticketChannelID
↩ Click to apply
Support Log
Grouped sections · Users separated
📝 Support Transcript | ticket-0042
Ticket opened by: @UserName
Ticket closed by: @StaffName

Users in ticket: @UserName, @Staff

Channel: ticket-0042
Channel ID: 123456789
Hover to preview · Click to apply
Support Log
Three visual sections separated by blank lines: opener/closer, then users, then channel info. Easy to scan.
channelNameticketOpenerticketCloserusersticketChannelIDserverName
↩ Click to apply
Full Detail
Every field · Message count included
📊 Full Transcript Log | My Server
Server: My Server
Channel: ticket-0042
Channel ID: 123456789

Opened by: @UserName
Closed by: @StaffName
Users: @UserName, @Staff
Messages: 24
Hover to preview · Click to apply
Full Detail
Maximum information — server, channel, channel ID, opener, closer, all users, and total message count. Nothing left out.
serverNamechannelNameticketChannelIDticketOpenerticketCloserusersmessageCount
↩ Click to apply
One-liner
Ultra-compact · Dot-separated
Transcript: ticket-0042 (My Server)
Opened: @UserName · Closed: @StaffName
Users: @UserName, @Staff
Channel ID: 123456789
Hover to preview · Click to apply
One-liner
Ultra-compact. Opener and closer on one dot-separated line, users on the next, channel ID on the last. Minimal footer.
channelNameserverNameticketOpenerticketCloserusersticketChannelID
↩ Click to apply
Formal Report
Official · Everything labelled
📄 Ticket Transcript Report
Server: My Server
Channel Name: ticket-0042
Channel ID: 123456789

Ticket Opener: @UserName
Ticket Closer: @StaffName
All Users: @UserName, @Staff
Total Messages: 24
Closed: Mon, 7 Apr 2025
Hover to preview · Click to apply
Formal Report
The most complete format. Every field labelled, message count, and a full date. Footer acts as an official watermark.
serverNamechannelNameticketChannelIDticketOpenerticketCloserusersmessageCountclosedAt
↩ Click to apply
embedTitle
Title of the transcript embed
embedColor
Hex color for embed sidebar
embedDescription
Supports {placeholders} — see reference below
embedFooter
Supports {placeholders} — e.g. {server}
embedTimestamp
Show timestamp in embed
embedThumbnail
Thumbnail image URL
embedImage
Large image URL in embed
⚙️ Advanced 0 / 3
timezone
Timezone for timestamps
autoDeleteAfter
Seconds until auto-delete
customFields
Extra JSON object — e.g. {"key":"value"}
🧠 Pro Features 0 / 5
showJoinLeave
Track who joined / left ticket
showEdits
Include message edit history
showDeletes
Show deleted messages
generateSummary
AI-powered summary (coming soon)
watermark
Branding text on transcript
0
Fields set
Payload bytes
Generated JSON empty
Fill in any field to see your payload…
✦ Placeholder Functions Use in embedTitle · embedDescription · embedFooter
{ticketOpener}
Mentions the ticket creator — <@userId>
{ticketOpenerID}
Raw user ID of the ticket creator
{ticketCloser}
Mentions the ticket closer — <@userId>
{ticketCloserID}
Raw user ID of the ticket closer
{ticketID}
The unique ticket ID you passed
{ticketType}
The ticket category — support, billing, etc.
{claimedBy}
Mentions the staff who claimed the ticket
{claimedByID}
Raw user ID of the claimer
{channel}
Discord channel name
{server}
Discord server/guild name
{closedAt}
Full date+time Discord timestamp — <t:…:F>
{closedAtR}
Relative Discord timestamp — <t:…:R>
{messageCount}
Total number of messages in transcript
{serverName}
Your Discord server/guild name
{channelName}
Name of the ticket channel — e.g. ticket-0042
{ticketChannelID}
The Discord channel ID of the ticket
{users}
All non-bot users who sent messages — as <@id> mentions
💡 Example: Opened by: {ticketOpener} · Users: {users} · Channel ID: {ticketChannelID} · Channel: {channelName} · Closed by: {ticketCloser}
Copied to clipboard!