API, webhooks and MCP

Connect billing systems, scripts and AI agents to VMStack with API keys, signed webhooks, the MCP server and the SolusVM-compatible API.

VMStack has a REST JSON API at /api/v1 on the panel's own domain. Each request uses an API key. The key belongs to one account and acts as that account, with the same rules, refusals and audit entries as the panel's pages. Webhooks push events to your URLs as they happen. The MCP server lets AI agents use the same API with a key. The SolusVM-compatible layer keeps billing modules written for SolusVM 1 working unchanged.

The full reference for every operation, schema and webhook body is at /docs/api. Your own panel serves the same reference at https://panel.example.com/api/docs.

  • API keys: creating keys, scopes, authentication, rate limits and the API log.
  • Webhooks: endpoints, events, signature verification and retries.
  • MCP server: connecting Claude and other MCP clients, and choosing which tools a key may use.
  • SolusVM-compatible API: the migration aid for SolusVM 1 billing modules (beta).
  1. API keysCreate VMStack API keys, choose their scopes and allowed addresses, call the REST API with curl, and read the API log and rate limits.
  2. WebhooksHave VMStack POST signed events to your URLs when servers, tasks, backups, accounts or nodes change, and verify and retry them correctly.
  3. MCP serverConnect Claude and other MCP clients to VMStack with an API key, and choose tool by tool what an AI agent may do on the panel.
  4. SolusVM-compatible API BetaKeep a SolusVM 1 billing module for WHMCS or Blesta working against VMStack unchanged, with the SolusVM-compatible admin API layer.