Servers and channels

#Servers

{
	"id": "103700000000000000",
	"name": "Game Night",
	"iconUrl": "https://cdn.baff.gg/icons/....webp",
	"ownerId": "103600000000000000",
	"channels": [ ... ],
	"roles": [ ... ],
	"myRoles": ["103700000000000123"],
	"invitesPaused": false,
	"types": ["verified", "partnered"],
	"community": true,
	"listed": true
}

channels only lists channels your bot can see. myRoles are your bot's roles (its own role, named after it, is one of them). roles is ordered highest first, ending with @everyone, whose ID is the server's ID.

#Server types

types lists the server's types, which the baff.gg team gives out (there's no API to set them). The app shows an icon for the most important one before the server's name.

community is whether it's a Community server and listed whether it's in Discovery (anyone can join it). Staff and developer servers are never listed. In those, only members with Manage Server (staff) or the owner and Administrators (developer) can make invites, developer-server invites work once and last at most an hour, and only a developer server's owner can add bots.

#Channels

A forum channel lists posts instead of messages; see Forum posts.

With Manage Channels:

Threads and forum posts can also be edited by whoever started them (name, autoArchiveMinutes, archived, and a post's appliedTags) and by anyone with Manage Threads there, who can also set locked, slowmodeSecs and delete them.

#Members

{
	"user": { "id": "103600000000000000", "username": "andre", "displayName": "Andre", "avatarUrl": null },
	"status": "online",
	"customStatus": "making a bot",
	"isOwner": true,
	"roles": ["103700000000000456"],
	"nick": null,
	"joinedAt": "2026-10-02T18:04:11Z",
	"pending": false
}

status is online, idle, dnd or offline. joinedAt is when they joined the server (for a bot, when it was added).

pending is true for someone who joined a server with Rules Screening on and hasn't agreed to its rules yet. Until they do, they can read but not send messages, react, use commands, join voice or DM members through the server (those answer 403 screening_pending). Bots are never pending. GET /api/servers/{serverId}/screening returns the server's { enabled, description, rules }.

#Roles

With Manage Roles, a bot can give and take roles below its own highest role:

PUT    /api/servers/{serverId}/members/{userId}/roles/{roleId}
DELETE /api/servers/{serverId}/members/{userId}/roles/{roleId}

A bot's own role can't be deleted or given to anyone else; it goes away when the bot leaves.

#Moderation

You can only kick or ban people whose highest role is below your bot's, never the owner. They get a notice from baff.gg saying they were removed. Kicks also take an optional body { "reason": "..." } for the audit log.

#Timeouts

A timed-out member can still read, but can't send messages, react (not even by joining a reaction), start threads, join voice or create invites until it ends: every permission except View Channel is gone, and those routes answer 403 timed_out. Leaving and coming back doesn't end it.

Same hierarchy as kicks, and never an Administrator (cant_timeout_admin). The member list shows timeoutUntil on timed-out members, and MEMBER_UPDATE carries timeoutUntil (null when it ends or is removed).

#Audit log

Every change worth knowing about, kept for 90 days, newest first. Needs View Audit Log or Manage Server.

GET /api/servers/{serverId}/audit-log?before={entryId}&limit=50&userId={who}&action={action}

All query parameters are optional: before pages back (pass the last entry's id), limit is 1 to 100 (default 50), userId keeps entries by one person, action keeps one kind.

{
	"entries": [
		{
			"id": "104546711128506368",
			"action": "member_timeout",
			"actorId": "103600000000000000",
			"targetType": "user",
			"targetId": "103600000000000777",
			"targetName": "sam",
			"reason": "Spamming",
			"changes": [{ "key": "timeoutUntil", "old": null, "new": "2026-10-16T09:00:00Z" }],
			"extra": {},
			"createdAt": "2026-10-16T08:50:00Z"
		}
	],
	"users": [{ "id": "103600000000000000", "username": "andre", "displayName": "Andre", "avatarUrl": null }],
	"hasMore": true
}

actorId is null for AutoMod. targetType is server, channel, role, user, invite, webhook, emoji or automod_rule; targetName is the name when it happened. changes lists { key, old, new }; permissions are decimal strings. users has everyone the page names.

#AutoMod

Servers can have AutoMod rules (Server Settings > AutoMod). They only check messages people send or edit: your bot's messages and webhooks are never stopped. When a rule blocks a person's message, the send or edit answers 400 automod_blocked.