ZennoHosting API documentation
This portal documents the ZennoHosting API for provisioning and operating virtual machines built for automation workloads. It is written for teams running ZennoPoster, browser automation, scraping and test environments who need a precise technical layer rather than a product overview.
The authored sections explain the resource model and the working scenarios. The API reference remains the source of exact request, parameter and response schemas.
What this portal covers
ZennoHosting is an API-first virtual machine platform. The documentation follows the real order of work: get access, create a project, gather the inputs, create a VM, set up networks and public IPs, then manage state and recovery.
Quickstart
The shortest path from an access token to a running VM.
Authentication
Access tokens, the authorization header and your first request.
Platform model
How projects, tariffs, images, networks, addresses and backups relate.
Networking model
Private networks, public IPs, internal addresses and port forwarding.
Statuses and lifecycle
The status field, an operation's outcome, and how the two differ.
Limits and quotas
What you may create, where to read the remainder, and name-length rules.
API errors
The error body format, status codes and how to read 409 conflicts.
Create and access a VM
Image, tariff, access and the public IP decision.
Inventory and monitoring
A fleet summary without walking list pages.
API reference
Endpoints, schemas, parameters and cURL examples.
Where to start
Quickstart — when you want the shortest path to a working VM.
Authentication — before wiring the API into your own client.
Platform model, Networking model and Statuses and lifecycle — to understand how the platform behaves.
Limits and quotas and API errors — so your client behaves correctly at the boundaries and on refusals.
- The guides when you need a concrete sequence, and the reference when you need the exact request shape.
What this was written for
The material targets ZennoHosting scenarios: running ZennoPoster, browser automation, scraping and short-lived test environments. It is not a general-purpose cloud infrastructure reference.
What is out of scope
Payments and billing are deliberately left out of this documentation layer. If such an endpoint appears in the reference, treat it as a technical surface outside the main provisioning and operations story.