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.Check ban status
The high-frequency check a game server runs when a player joins. Responses are cached briefly for performance.Your guild ID. Must match the key’s guild.
The Roblox user ID to check.
The Roblox place ID. Lets the check honour place-specific bans in addition to global ones.
Set to
true to bypass the cache and read live.Present only when
banned is true.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.The Roblox user ID to ban.
The Roblox ID of the staff member issuing the ban.
The target’s Roblox username, for nicer logs.
A duration like
5m, 1h, 7d, or permanent. Omit for a permanent ban.Whether the ban applies across all games or only the source place.
The
game.JobId of the server issuing the ban, used to prevent echo loops.Lift a ban
Defaults to “Unbanned via game server”.
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.The list of active ban records. The mutes endpoint returns
data.mutes.