hosting
GET /v1/hosting/fleet-applications
List the applications we install ourselves on our own fleet.
身份验证
请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限，因此请为您的密钥赋予所需的最小权限，并通过检查响应来确认，而不是盲目假设。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/hosting/fleet-applications \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
The own-fleet counterpart of GET /v1/hosting/applications, and deliberately a separate operation rather than a flag on it, because the two answer different questions from different authorities. That one reports what the resold platform's installer offers and is read live from the vendor. This one reports what we have written an installer for, which is a fact about this platform at this release — Nextcloud, ownCloud, the headless-CMS choice (docs/139) and the PHP applications of the php_app stack: Drupal, Joomla, Moodle, PrestaShop and the rest of the application range (docs/681). Authenticated but not tenant-scoped: like the locations and applications endpoints it is a statement about what this platform sells, and the create-site form needs it at the one moment no site exists to read it from.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
stack_type (query) | StackType | 否 | Narrow to the applications that answer one stack. headless_cms returns the CMS choice and php_app the PHP application choice; nextcloud and owncloud return exactly one… |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
data | FleetApplication[] | 是 | — |
此端点可能返回的错误
401 · 403 · 429