Moderation

These endpoints let a Roblox game server check whether a player is banned or muted, and create or lift Roblox punishments that sync back to the dashboard. The guild ID lives in the path and must match your API key’s guild.

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.

GET /moderation/:guildId/ban-status/:identifier

string

required

Your guild ID. Must match the key’s guild.

number

required

The Roblox user ID to check.

number

The Roblox place ID. Lets the check honour place-specific bans in addition to global ones.

boolean

Set to true to bypass the cache and read live.

boolean

object

Present only when banned is true.

Show properties

string

number

number | null

boolean

{
  "status": "success",
  "code": 200,
  "message": "User is banned",
  "data": {
    "banned": true,
    "ban_info": {
      "reason": "Exploiting",
      "banned_by": "987654321",
      "created_at": 1746712921,
      "expires_at": null,
      "is_permanent": true
    }
  }
}

{
  "status": "success",
  "code": 200,
  "message": "User is not banned",
  "data": { "banned": false }
}

Check mute status

GET /moderation/:guildId/mute-status/:identifier

Same path params and query options as the ban check. The response uses muted and mute_info (with muted_by instead of banned_by).

{
  "status": "success",
  "code": 200,
  "message": "User is muted",
  "data": {
    "muted": true,
    "mute_info": {
      "reason": "Spam",
      "muted_by": "987654321",
      "created_at": 1746712921,
      "expires_at": 1746799321,
      "is_permanent": false
    }
  }
}

Create a ban

Bans a Roblox user. The ban syncs to your connected games and appears in the dashboard.

POST /moderation/:guildId/roblox/ban

string

required

string

required

The Roblox user ID to ban.

string

required

string

required

The Roblox ID of the staff member issuing the ban.

string

The target’s Roblox username, for nicer logs.

string

A duration like 5m, 1h, 7d, or permanent. Omit for a permanent ban.

boolean

default:"true"

Whether the ban applies across all games or only the source place.

string

The game.JobId of the server issuing the ban, used to prevent echo loops.

curl "https://api.technified.xyz/api/v1/moderation/$GUILD_ID/roblox/ban" \
  -H "X-API-Key: $TECHNIFIED_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "roblox_id": "261",
    "username": "Shedletsky",
    "reason": "Exploiting",
    "duration": "7d",
    "moderator_roblox_id": "1",
    "moderator_username": "Builderman"
  }'

{
  "status": "success",
  "code": 200,
  "message": "User banned successfully via game server",
  "data": {
    "banned": true,
    "expires_at": 1747317721,
    "is_permanent": false
  }
}

A second ban on an already-banned user returns 400. Check status first if you are unsure.

Lift a ban

POST /moderation/:guildId/roblox/unban

string

required

string

required

string

required

string

Defaults to “Unbanned via game server”.

string

Returns 404 if the user has no active ban.

Create or lift a mute

Mutes mirror bans exactly. Use the same fields.

POST /moderation/:guildId/roblox/mute
POST /moderation/:guildId/roblox/unmute

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.

GET /moderation/:guildId/roblox/bans/active
GET /moderation/:guildId/roblox/mutes/active

array

The list of active ban records. The mutes endpoint returns data.mutes.

number

{
  "status": "success",
  "code": 200,
  "message": "Active bans retrieved",
  "data": {
    "bans": [
      {
        "id": 42,
        "identifier": "261",
        "reason": "Exploiting",
        "banned_by": "1",
        "expires_at": null,
        "is_active": 1
      }
    ],
    "total": 1
  }
}

Read moderation logs

Read the guild’s moderation log history, for example to mirror punishments into your own audit tooling. Requires the moderation:read scope.

GET /guilds/:guildId/moderation/logs

string

required

Your guild ID. Must match the key’s guild.

number

Maximum number of log entries to return.

number

Number of entries to skip, for pagination.

curl "https://api.technified.xyz/api/v1/guilds/$GUILD_ID/moderation/logs?limit=50" \
  -H "X-API-Key: $TECHNIFIED_API_KEY"

This is the API-key-accessible counterpart to the dashboard’s moderation log view. The bare /moderation/:guildId/logs route remains dashboard-only.

Developer API

Endpoints

Playground

Reference

Check ban status

Check mute status

Create a ban

Lift a ban

Create or lift a mute

List active punishments

Read moderation logs

​Check ban status

​Check mute status

​Create a ban

​Lift a ban

​Create or lift a mute

​List active punishments

​Read moderation logs

Check ban status

Check mute status

Create a ban

Lift a ban

Create or lift a mute

List active punishments

Read moderation logs