The plain
/moderation/:guildId/ban, /unban, /mute, and /bans/active routes are dashboard-only. With a guild API key, use the roblox/ variants documented here.Read endpoints (
ban-status, mute-status, bans/active, mutes/active, logs) require the moderation:read scope. Write endpoints (roblox/ban, roblox/unban, roblox/mute, roblox/unmute) require moderation:write. See Scopes.Check ban status
The high-frequency check a game server runs when a player joins. Responses are cached briefly for performance.Check mute status
muted and mute_info (with muted_by instead of banned_by).
Create a ban
Bans a Roblox user. The ban syncs to your connected games and appears in the dashboard.Lift a ban
404 if the user has no active ban.
Create or lift a mute
Mutes mirror bans exactly. Use the same fields.mute accepts the same body as ban (roblox_id, reason, duration, moderator_roblox_id, and so on). unmute accepts the same body as unban.
List active punishments
Fetch every active ban or mute for the guild, for example to seed an admin system on startup.Read moderation logs
Read the guild’s moderation log history, for example to mirror punishments into your own audit tooling. Requires themoderation:read scope.
This is the API-key-accessible counterpart to the dashboard’s moderation log view. The bare
/moderation/:guildId/logs route remains dashboard-only.