Technical Docs
ZennoHosting API Documentation
This portal documents the ZennoHosting API for provisioning and operating virtual machines built for automation workloads. It is written for teams that automate ZennoPoster workloads, browser automation, scraping, and test environments, and need a reliable technical layer rather than a marketing overview.
The authored pages explain the resource model and operational workflows first. The generated API Reference remains the contract source for exact request schemas, parameters, and response payloads.
What this portal covers
ZennoHosting is an API-first infrastructure surface for virtual machines used in automation pipelines. The documentation focuses on the actual operating model: obtain access, create a project, resolve provisioning inputs, create a VM, connect networks and public IPs, and manage recovery flows.
Quickstart
Shortest reliable path from access token to a created ZennoHosting VM.
Authentication
Access token model, bearer header usage, and the first authenticated request.
Platform Model
Project-first relationships between tariffs, images, networks, VMs, public IPs, and backups.
Networking
Private networks, public IP resources, internal addressing, and port forwarding.
Operations and Statuses
How to interpret accepted commands, async work, and final resource state.
Create and Access a VM
Provision a VM with the right image, tariff, access inputs, and public IP strategy.
API Reference
Generated endpoint documentation, schemas, parameters, and cURL snippets.
Recommended reading order
Start with Quickstart when you need the shortest path to a provisioned VM.
Read Authentication before wiring ZennoHosting into a client or automation tool.
Use Platform Model, Networking, and Operations and Statuses to understand how the platform behaves.
Move to the workflow guides when you need a concrete sequence, then open the generated reference for payload details.
Use case fit
The authored layer is optimized for ZennoHosting workflows such as ZennoPoster execution, browser automation, scraping, and temporary test environments. It is not a general cloud-computing handbook.
Current documentation scope
Billing and payment flows are intentionally excluded from the authored documentation layer. If a billing-related endpoint appears in the generated API Reference, treat it as a technical surface outside the main provisioning and operations narrative.