Skip to main content
PATCH
/
api
/
admin
/
servers
/
:id
curl -X PATCH "https://panel.example.com/api/admin/servers/a1b2c3d4" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
    "memory": 4096,
    "cpu": 200,
    "disk": 20480,
    "databaseLimit": 2,
    "backupLimit": 5
  }'
{
  "data": {
    "success": true,
    "message": "Build configuration updated successfully"
  }
}

Authentication

This endpoint requires admin authentication and the servers:write permission.

Path Parameters

id
string
required
Server ID or UUID

Request Body

cpu
number
CPU limit percentage (minimum: 0)
memory
number
Memory limit in MB (minimum: 0)
swap
number
Swap space in MB (minimum: -1, -1 = unlimited)
disk
number
Disk space in MB (minimum: 0)
io
number
Block I/O weight (10-1000)
threads
string
CPU thread pinning (e.g., “0-3,8”)
oomDisabled
boolean
Disable OOM killer
databaseLimit
integer
Database limit (null = unlimited)
allocationLimit
integer
Additional allocation limit (null = unlimited)
backupLimit
integer
Backup limit (null = unlimited)

Response

data
object
curl -X PATCH "https://panel.example.com/api/admin/servers/a1b2c3d4" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
    "memory": 4096,
    "cpu": 200,
    "disk": 20480,
    "databaseLimit": 2,
    "backupLimit": 5
  }'
{
  "data": {
    "success": true,
    "message": "Build configuration updated successfully"
  }
}

Notes

  • Updates are applied to the database immediately
  • The server configuration is synchronized with Wings after database update
  • If Wings sync fails, an error is returned but database changes persist
  • Changes will be applied on next server restart if sync fails
  • Only provided fields are updated; omitted fields remain unchanged

Build docs developers (and LLMs) love