Introduction

The VPS-Server.Host Public API lets you control your VPS infrastructure, account, billing, and support programmatically. Everything you can do in the client area, you can do over HTTP.

What you can do

• Provision and control VPS servers — start, stop, reboot, rebuild, rescue, VNC console, snapshots, password reset
• Manage reverse DNS (PTR) — required for SMTP deliverability
• Handle billing — list invoices, pay, top up credit, accept quotes
• Manage your account — profile, 2FA, KYC, sub-users (contacts), payment methods
• Domains — register, renew, nameservers, lock/unlock, WHOIS, EPP
• Support — open tickets, reply, browse the knowledge base
• Subscribe to webhooks — invoice paid, operation succeeded, more

How it's organized

Surface	What it's for
REST API	The canonical interface. Bearer-token auth, JSON over HTTPS.
CLI (vpsctl)	Single-binary Go CLI for power users and CI scripts.
Terraform provider	Infrastructure-as-code for servers, snapshots, DNS, SSH keys.
MCP server	Lets Claude, Cursor, and other AI assistants manage your VPS in chat.
Postman collection	Auto-generated from the OpenAPI spec on every release.

Conventions at a glance

• Base URL: https://api.vps-server.host/v1
• Sandbox: https://sandbox.api.vps-server.host/v1 — separate data, fake gateways, pat_test_… tokens
• Auth: Authorization: Bearer pat_live_…
• Errors: RFC 7807 application/problem+json
• Async actions: return 202 Accepted + an Operation you can poll or subscribe to
• Step-up: destructive or billed actions require an X-Confirm-Token (why?)

ℹ

OpenAPI 3.1, source of truth

The whole API is described in a single openapi.yaml you can download or import into Postman / Insomnia / VS Code. See the API Reference for the live spec.

Next steps

1. Create a Personal Access Token
2. Make your first API call — under two minutes
3. Browse the API Reference