Skip to main content

API Overview

The WebberStop REST API lets you automate everything you can do in the portal. Provision VPCs, deploy instances, manage Kubernetes clusters, run backups, attach storage, and query usage, all from your own code.

The API powers our own portal (Stack Console) and is exposed to customers under the same authentication and authorization rules. If the portal can do it, the API can do it.

Base URL​

https://portal.webberstop.com/backend/api

Interactive reference​

The complete, always-current reference lives at:

https://portal.webberstop.com/backend/api/docs/administrator

It is a Swagger UI built from our OpenAPI 3 specification. You can:

  • Browse every endpoint, parameter, and response schema.
  • Click Authorize, paste a JWT, and run real calls against your account from the browser.
  • Download the OpenAPI spec to generate clients in any language.

What you can build​

  • Infrastructure as code: provision VPCs, network tiers, ACLs, instances, volumes, and load balancers from Terraform, Pulumi, or your own scripts.
  • Custom dashboards: pull instance state, billing data, and Kubernetes cluster health into your existing tools.
  • CI/CD integration: deploy applications to managed Kubernetes clusters, attach storage on demand, rotate credentials.
  • Cost automation: query usage and bill data to feed your finance systems.
  • Capacity automation: react to load by scaling instances or Kubernetes node pools through the API.

Architecture​

The WebberStop platform runs Apache CloudStack as the orchestration layer. Our REST API sits in front of CloudStack and exposes a cleaner, JSON-based surface with first-class JWT authentication.

You do not call CloudStack directly. The CloudStack management server is on a private network and not reachable from outside our platform, by design. All tenant traffic goes through portal.webberstop.com/backend/api, which handles authentication, authorization, audit, rate limiting, and request validation before forwarding work to CloudStack.

This means:

  • You authenticate once against our REST API and use that token for everything.
  • Audit logs, quotas, and policies apply uniformly whether you use the portal or the API.
  • You do not need CloudStack apikey/secret credentials.

Getting started​

  1. Generate a JWT by calling POST /login with your portal credentials.
  2. Make your first call using curl to list your VPCs.
  3. Walk through the call sequence to provision a complete stack.
  4. Browse the Swagger reference for full endpoint details.

Support​

Include your account name, the endpoint you called, the request body (redact secrets), and the full response when reporting an API issue.