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. You'll find the power controls at the top right, beside the Running / Stopped badge. As the page loads, the portal fetches the live state from the management controller, so the badge reads checking for a moment first.
3. Pick a control from the table above:
   • Shutdown and Reboot run the moment you click.
   • Stop wants a confirmation first, since it throws away unsaved data. The same card reminds you that a stopped server is still billed.
   • If the server is already stopped, you'll see Start in that row instead.
4. Give it a few seconds, then click Status for the new state. A reboot lasts as long as the machine's own POST and boot, which on bare metal is usually one to three minutes.

Cloud instances

1. Open Virtual Machines in the left-hand menu and click the instance.
2. The header shows the live state. A running VM gets Console, Reboot and Stop; a stopped one gets Start. To re-read the state from the hypervisor, click the small refresh icon beside the badge.
3. Click the action. A confirmation shows up at the top of the page and the badge tracks the machine from there. A stop can take up to half a minute, because the hypervisor waits for the guest. A reboot goes through Stopped on its way back up.

Each power action lands on the Activity page, along with who clicked 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 it under Account → API Keys and copy it right away, because it's only shown once. Full reference: api.amoni.app/v1/docs.

Bare metal

Look up the server id in GET /v1/servers and post the action to it. There are four actions: 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 normalized to on, off or null (the management controller didn't answer), while state keeps the controller's own wording. To read the state and change nothing:

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 the moment the controller accepts it, not once the machine is back up. If your script has to wait, poll status:

#!/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

You address a VM by its billing account id plus its VM id. GET /v1/vms gives you both:

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" } ] }

Next, post start, stop or reset. Be aware that 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"}'

For the live state, straight from the hypervisor instead of 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 didn't respond, so what you see is the last state we recorded.

What the API will tell you

About 422s: when the endpoint checks a rule itself (a weak password, a duplicate key, a layout you may not use), the answer comes in the usual envelope. A field that fails basic validation still answers in the framework's own shape for now, {"message": "…", "errors": {"field": ["…"]}}, with no success or code. For those, branch on the HTTP status. We're extending the envelope to cover them.