Server Manager

Server Manager lets staff control live Roblox servers from the dashboard: see who is online, kick, ban, mute, message, broadcast, or shut a server down. It works as a command queue, and your game server speaks to it with a guild API key.

The queue endpoints (servers/heartbeat, servers/:serverId/commands, and the command ack) require the server:write scope. Quick-installed plugin keys have it automatically. See Scopes.

How the queue works

Dashboard (staff clicks Kick)        Your Roblox server (API key)
        |                                     |
        |  enqueues a command                 |  1. heartbeat: report state + players
        v                                     |  2. read pending commands from the
   server_commands  <------------ heartbeat --+     heartbeat response
        |                                     |  3. run each command in-game
        +------------------ ack --------------+  4. ack: report the result

Only these three endpoints accept a guild API key. The dashboard side, listing servers and enqueuing a command (/guilds/:guildId/servers...), requires a logged-in dashboard session with the server_manager permission and is not callable with an API key.

These endpoints use camelCase field names, like the rest of the plugin protocol.

Heartbeat

Report a live server and its current player list. Send this on a short loop, for example every 10 seconds (a server counts as stale after 30 seconds without a heartbeat). It keeps the server marked online, feeds the player list shown in the dashboard, and its response carries any pending commands for this server, so no separate poll loop is needed.

POST /roblox/servers/heartbeat

string

required

Must match your API key’s guild.

string

required

The Roblox game.JobId.

string

required

string

number

required

number

required

number

Seconds since the server started.

number

object[]

required

The current players.

Show player object

string

required

string

required

string

number

required

Unix timestamp when the player joined.

string

curl "https://api.technified.xyz/api/v1/roblox/servers/heartbeat" \
  -H "X-API-Key: $TECHNIFIED_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "guildId": "'$GUILD_ID'",
    "serverId": "abc123-...",
    "placeId": "987654321",
    "gameName": "My Game",
    "playerCount": 2,
    "maxPlayers": 50,
    "serverAge": 3600,
    "players": [
      { "robloxId": "261", "username": "Shedletsky", "joinTime": 1746712900 }
    ]
  }'

{
  "status": "success",
  "code": 200,
  "data": {
    "success": true,
    "commands": [
      {
        "id": 42,
        "type": "kick",
        "targetRobloxId": "261",
        "targetUsername": "Shedletsky",
        "parameters": { "reason": "AFK" },
        "issuedByUsername": "Febreeze"
      }
    ]
  }
}

Players missing from a heartbeat are treated as having left and are removed from the server’s live list. data.commands holds up to 20 pending commands (oldest first, including broadcast commands targeted at every server); they are marked as delivered on return, so execute and acknowledge each one.

Poll for commands

Alternative to heartbeat-delivered commands: fetch the pending commands queued for this server on a dedicated loop. The response also includes broadcast commands targeted at every server. Polled commands are marked as delivered. If you already send heartbeats, you do not need this endpoint.

GET /roblox/servers/:serverId/commands

string

required

The same game.JobId you heartbeat with.

object[]

Up to 20 pending commands, oldest first.

Show command object

number

The command ID, needed to acknowledge it.

string

One of kick, ban, mute, message, teleport, broadcast, shutdown.

string | null

The target player, for player commands.

string | null

object

Command-specific data, for example reason, duration, or message.

string

{
  "status": "success",
  "code": 200,
  "data": {
    "commands": [
      {
        "id": 17,
        "type": "kick",
        "targetRobloxId": "261",
        "targetUsername": "Shedletsky",
        "parameters": { "reason": "Breaking rules" },
        "issuedByDiscordId": "123456789012345678",
        "issuedByUsername": "Builderman"
      }
    ]
  }
}

Command types

Type	Scope	Common parameters
`kick`	Player	`reason`
`ban`	Player	`reason`, `duration`
`mute`	Player	`reason`, `duration`
`message`	Player	`message`
`teleport`	Player	destination data
`broadcast`	Server	`message`
`shutdown`	Server	none

Player commands carry a targetRobloxId. Server-level commands like broadcast and shutdown do not. A broadcast is queued for every server at once.

Acknowledge a command

After running a command, report the outcome. This moves the command to acknowledged so it is not retried, and surfaces the result in the dashboard.

POST /roblox/servers/:serverId/commands/:commandId/ack

string

required

number

required

The id from the poll response.

boolean

required

string

A short human-readable result, for example “Kicked Shedletsky”.

string

An error message when success is false.

curl "https://api.technified.xyz/api/v1/roblox/servers/abc123-.../commands/17/ack" \
  -H "X-API-Key: $TECHNIFIED_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "success": true, "result": "Kicked Shedletsky" }'

If you run the Roblox integration or Technified Admin, this whole loop is already implemented. You only need these endpoints when building a custom admin system.

Developer API

Endpoints

Playground

Reference

How the queue works

Heartbeat

Poll for commands

Command types

Acknowledge a command

​How the queue works

​Heartbeat

​Poll for commands

​Command types

​Acknowledge a command

How the queue works

Heartbeat

Poll for commands

Command types

Acknowledge a command