身份验证
请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 sites.view 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。
您的组织 ID 应填在此处
此端点将 org_id 作为查询参数。不填则调用涵盖您的整个租户子树；发送该参数则将调用范围缩小到一个组织。
您的组织ID位于控制面板的API密钥屏幕上，就在密钥本身的旁边。这是您在每次调用时使用的相同ID。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/compute/servers \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
Every machine the caller can see, or — with `?org_id=` — one organisation's. The scoped form is what a reseller's console sends. An organisation outside the readable scope narrows to nothing rather than `403`-ing, exactly as `listSites` does: a `403` would confirm the organisation exists. ⛔ **Resolved from our own rows, not from the provider's listing**, which is every customer on the reseller account. `status` is ours (how far the order got) and `power_state` is the machine's (what it is doing now); they are separate facts and rounding the provider's word into ours would silently make an unrecognised state `active`, which is what unlocks the power and resize controls. `operable` is read rather than re-derived from `status`, so a screen never offers a control the engine refuses. Requires `sites.view`.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
org_id (query) | Uuid | 否 | Narrow the list to one organisation the caller can read. |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
data | ComputeServer[] | 是 | The machines, across every organisation the caller can read. |
此端点可能返回的错误
401 · 403 · 404 · 422 · 429 · 503