Skip to main content
DELETE
/
api
/
admin
/
servers
/
:id
curl -X DELETE "https://panel.example.com/api/admin/servers/a1b2c3d4" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json"
{
  "data": {
    "success": true,
    "message": "Server deleted successfully"
  }
}

Authentication

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

Path Parameters

id
string
required
Server ID or UUID

Query Parameters

force
boolean
default:"false"
Force delete from panel even if Wings deletion fails. Accepts “true” or “1”.

Response

data
object
curl -X DELETE "https://panel.example.com/api/admin/servers/a1b2c3d4" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json"
{
  "data": {
    "success": true,
    "message": "Server deleted successfully"
  }
}

Deletion Process

  1. Without force: Server is deleted from Wings first, then from the panel database
  2. With force: Server is deleted from the panel database even if Wings deletion fails

What Gets Deleted

  • Server record
  • Server limits
  • All allocations (freed for reuse)
  • Environment variables
  • Schedules
  • Databases
  • Subusers
  • Backups
  • Mount associations

Error Handling

  • 409 Conflict: Wings deletion failed and force was not specified
  • 404 Not Found: Server doesn’t exist (treated as success if force=true)
  • If the node is offline, use force=true to delete from the panel

Build docs developers (and LLMs) love