Reboot, Shut Down or Power Cycle Your Server: Portal and API

Method 1: In the portal

Bare-metal servers

1. Log in at amoni.app and open Servers in the left-hand menu.
2. Click the server. The power controls sit at the top right of the page, next to the Running / Stopped badge. When the page opens, the portal reads the live state from the management controller; the badge shows checking for a moment.
3. Choose the control from the table above:
   • Shutdown and Reboot act straight away.
   • Stop asks you to confirm first, because it discards unsaved data. It also reminds you that stopping a server does not stop billing.
   • On a stopped server the row shows Start instead.
4. Click Status a few seconds later to see the new state. A reboot takes as long as the machine's own POST and boot, typically one to three minutes on a bare-metal server.

Cloud instances

1. Open Virtual Machines in the left-hand menu and click the instance.
2. The header shows the live state and, for a running VM, Console, Reboot and Stop. A stopped VM shows Start. The small refresh icon next to the badge re-reads the state from the hypervisor.
3. Click the action. A confirmation appears at the top of the page, and the badge follows the machine: a stop can take up to half a minute while the hypervisor waits for the guest, and a reboot passes through Stopped on the way back up.

Every power action is recorded on the Activity page with who did it and when.

Method 2: With the API

You need an API key with the Servers scope (servers.write) for bare metal, or the VMs scope (vms.write) for cloud instances. Create one under Account → API Keys; it is shown once. Full reference: api.amoni.app/v1/docs.

Bare metal

Find the server id in GET /v1/servers, then post the action. The four actions are status, start, shutdown and powercycle.

curl -s -X POST https://api.amoni.app/v1/servers/955/power \
  -H "Authorization: Bearer nr_live_..." \
  -H "Content-Type: application/json" \
  -d '{"action": "powercycle"}'

{ "success": true, "data": { "state": "on", "status": "on" } }

status in the response is normalised to on, off or null (the management controller did not answer); state carries the controller's own wording. Read the state without changing anything:

curl -s -X POST https://api.amoni.app/v1/servers/955/power \
  -H "Authorization: Bearer nr_live_..." \
  -H "Content-Type: application/json" \
  -d '{"action": "status"}'

A powercycle returns as soon as the controller accepted it, not when the machine is back. Poll status if a script needs to wait:

#!/usr/bin/env bash
KEY="nr_live_..."; ID=955
post() { curl -s -X POST "https://api.amoni.app/v1/servers/$ID/power" \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" -d "{\"action\": \"$1\"}"; }

post powercycle | jq -r '.data.state'
for i in $(seq 1 30); do
  sleep 10
  if nc -z -w 3 203.0.113.10 22; then echo "SSH is back"; break; fi
done

Cloud instances

A VM is addressed by its billing account id and its VM id, both in GET /v1/vms:

curl -s https://api.amoni.app/v1/vms -H "Authorization: Bearer nr_live_..." \
  | jq '.data.accounts[] | {account_id, vms: [.vms[] | {id, hostname, status}]}'

{ "account_id": 990204, "vms": [ { "id": 411, "hostname": "app1.example.com", "status": "running" } ] }

Then post start, stop or reset. stop is not a graceful shutdown.

curl -s -X POST https://api.amoni.app/v1/vms/990204/411/power \
  -H "Authorization: Bearer nr_live_..." \
  -H "Content-Type: application/json" \
  -d '{"action": "reset"}'

The live state, read from the hypervisor rather than from our cached inventory:

curl -s https://api.amoni.app/v1/vms/990204/411/status \
  -H "Authorization: Bearer nr_live_..."

{ "success": true, "data": { "status": "running", "live": true } }

live: false means the hypervisor did not answer and you are seeing our last recorded state.

What the API will tell you

About 422s: a rule the endpoint checks itself (a weak password, a duplicate key, a layout you may not use) answers in the usual envelope. A field that fails basic validation currently answers in the framework's own shape, {"message": "…", "errors": {"field": ["…"]}}, without success or code. Branch on the HTTP status for those; the envelope is being extended to cover them.