Skip to main content

​
Prerequisites

You need a VMArea account and at least one available billing credit to provision a VM.
1

Create an API token

Sign in to vmarea.com/dashboard and navigate to Settings → API Keys. Create a new token, select the scopes you need, and optionally set an expiry date.
The secret is shown only once. Copy it immediately and store it in an environment variable or secrets manager.
export VMAREA_TOKEN="vmk_..."
See Scopes & permissions for a full list of available scopes and what they grant.
2

List available plans and regions

Before creating a VM, fetch the catalog to find a valid planId, regionId, and osTemplateId. Catalog reads require any valid token — no specific scope needed.
curl https://api.vmarea.com/api/public/v1/plans \
  -H "x-api-key: $VMAREA_TOKEN"
3

Create a VM

curl -X POST https://api.vmarea.com/api/public/v1/vms \
  -H "x-api-key: $VMAREA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "my-server",
    "hostname": "my-server",
    "planId": "<plan-id>",
    "regionId": "<region-id>",
    "osTemplateId": "<os-template-id>"
  }'
A successful response returns 201 with { "success": true, "data": { "id", "status", ... } }. The VM starts provisioning immediately.
4

Poll for status

VM creation is asynchronous. Poll until status reaches RUNNING (or FAILED):
curl https://api.vmarea.com/api/public/v1/vms/<vm-id> \
  -H "x-api-key: $VMAREA_TOKEN"
Subscribe to a vm.created webhook to avoid polling entirely. See Webhooks.
5

Run lifecycle actions

Once running, control your VM with action endpoints:
# Start
curl -X POST https://api.vmarea.com/api/public/v1/vms/<vm-id>/start \
  -H "x-api-key: $VMAREA_TOKEN"

# Stop
curl -X POST https://api.vmarea.com/api/public/v1/vms/<vm-id>/stop \
  -H "x-api-key: $VMAREA_TOKEN"

# Restart
curl -X POST https://api.vmarea.com/api/public/v1/vms/<vm-id>/restart \
  -H "x-api-key: $VMAREA_TOKEN"
All lifecycle actions require the vms:write scope.

​
Next steps

See the API reference for the full surface: firewall rules, private networks, SSH keys, backups, snapshots, and billing endpoints.