Skip to main content
You can script almost anything you do in the client area. Reboot a fleet, pull invoices into your accounting, open a ticket when monitoring trips, resell stock at your own rate. It’s the same backend with the same permissions. The panel is just another client of this API.

Quickstart

Create a token and make your first call in about two minutes.

Authentication

Token format, the 14 scopes, expiry and revoking.

Errors and rate limits

The response envelope, every status code, and what gets your IP blocked.

API reference

Every public endpoint, with a playground you can call from the browser.

​
Guides

Servers

List, power, rescue, snapshot, reinstall and cancel cloud and dedicated servers.

Billing and tickets

Read and pay invoices, download PDFs, and open or reply to tickets.

Reselling

Read live stock at your own price and place real orders.

​
Base URL

Every path in these docs is relative to that, so /cloud means https://my.server.express/api/v1/cloud. It’s HTTPS only, with JSON in and JSON out. Send Content-Type: application/json on anything with a body.

​
What it doesn’t cover

Here are the edges, so you don’t find them the hard way:
  • Most of the account. Tokens reach only the endpoints that name a required scope in the API reference. Account settings, passkeys, one-click apps, IP and rDNS changes, and the token endpoints themselves need a browser session. A token can never mint another token.
  • Storefront checkout. You can’t use the cart over the API. If you need to order programmatically, use the reseller endpoints. They place real orders against your account.
If one of those blocks something you’re building, tell us. The scope list grows based on what people actually ask for.

​
Versioning

The /v1 prefix is a promise. We’ll add fields and endpoints inside v1, but we won’t remove fields or change what an existing one means. Anything that would break your client gets a /v2. Write clients that ignore unknown fields.