Versioning Policy
v1 is stable forever — no breaking change ships under /api/v1/.
Backwards-incompatible work goes through /api/v2/, deployed in
parallel with a 15-month deprecation window for v1.
The full policy (header conventions, deprecation timelines, deprecation
warnings) is documented in
docs/developer/versioning-policy.md.
Feature discovery
Capabilities keep arriving within v1 — a new route, or new behaviour of an
existing one — and the version number does not tell a client which of them a
server has. GET /api/v1/system/info answers api_features, the names of the
optional capabilities this server offers:
{
"status": "success",
"data": {
"api_features": ["account_ip_blocks", "account_password", "bandwidth_usage", "login_token", "tenant_phpmyadmin"],
"hostname": "server.example.com",
"os": { /* … */ }
}
}
Check the list before relying on a capability. A missing name means the
server predates that capability; a missing api_features field means the
server predates the list itself — read it as an empty list. Within v1 names
are only added, never removed or renamed. A client that keeps the list per
server reads it again from time to time: an update adds names.
account_passwordA full-access key changes an account's password — Password changes (billing keys)login_tokenOne-time client sign-in links — Client sign-in links (billing systems)tenant_phpmyadminphpMyAdmin restricted to the account's own databases — Customer phpMyAdmin sign-in (billing systems)bandwidth_usageThe account's monthly traffic (web, email and FTP) in GET /accounts/{username}/usage: bandwidth_used_mb, bandwidth_period, bandwidth_breakdown_mbaccount_ip_blocksThe account's own IP block list — Account IP blocksOur support team is here around the clock for anything you can't find above.