GET /v1/catalog/app/site-hosting-lines

身份验证

请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限，因此请为您的密钥赋予所需的最小权限，并通过检查响应来确认，而不是盲目假设。

此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。

免费试用

将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。

curl -X GET https://api.zinndigital.com/v1/catalog/app/site-hosting-lines \
  -H "Authorization: Bearer zdk_live_…"

已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点

详细信息

The subset of listInAppProductLines a website can actually live on, and the catalogue half of what a deploy or migrate picker needs. ⚖️ Owner, 2026-09-09, on the migration flow: "When it allows them to select a hosting type to migrate to, does it only show them the hosting types they actually own and say for other hosting plans they need to buy it first type of thing?". Measured live the same day, the migration screen offered eighteen lines — of which four sell something that is not a website: Zinn® Boards, Zinn® Managed Databases, Zinn® Vector Databases and email for an external domain. A managed database has no document root; Boards is a project board. ⛔ The predicate is derived, never enumerated. A line appears here iff some purchasable plan on it grants a positive or unlimited max_sites — which is exactly the entitlement a site create spends, so this cannot drift from what POST /v1/sites accepts. A hand-written deny list would be right on the day it was typed and would silently offer the fifth non-hosting line an operator seeds tomorrow. ⛔ It says nothing about whether the caller can afford one. "Do I already have room" is getDeployablePlans, and the two stay apart: a screen composes them — the owned half to offer, the difference to upsell. Reseller clients see only the lines their provider still sells, exactly as listInAppProductLines does, so nothing here can be bought and then refused by the cart. internal lines (the staff tariff) are excluded: they grant unlimited sites and are assigned by staff, so offering one advertises a plan the customer cannot buy. Requires authentication and nothing else. Cache-Control: private, no-store — the list carries in-app-only lines, so a shared cache would hand them to the next anonymous visitor.

响应

此端点可能返回的错误

401 · 429