domains
GET /v1/domain-watches
The domains this customer is watching — ours, theirs and third parties'.
身份验证
请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限，因此请为您的密钥赋予所需的最小权限，并通过检查响应来确认，而不是盲目假设。
您的组织 ID 应填在此处
此端点将 org_id 作为查询参数。不填则调用涵盖您的整个租户子树；发送该参数则将调用范围缩小到一个组织。
您的组织ID位于控制面板的API密钥屏幕上，就在密钥本身的旁边。这是您在每次调用时使用的相同ID。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/domain-watches \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
The domain monitor (⚖️ owner 2026-08-30, `docs/296` §5). Every domain registered with us and every domain attached to hosting with us is on this list automatically; the customer may add any other name they like, mute one, or remove it. ⛔ **A removed watch is soft-removed and never returned here.** Auto-add runs on every provision, so a hard delete would let tomorrow's provision resurrect a domain the customer deliberately took off their list — for ever, with no way for them to make it stop. `last_checked_at` is when the registry last answered, and it is rendered beside every value on the row for a reason: these facts are a snapshot of the outside world and go stale silently (§2.36). A tick with no date on it is indistinguishable from a live one. `expires_at` and `days_until_expiry` are `null` when the registry did not say — which is a different fact from "it expires in a decade" and must not render as one.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
org_id (query) | string | 否 | Narrow to one organisation in the caller's subtree — what the dashboard's org switcher sends. ⛔ **Narrow only:** intersected with what the caller may already read, so it can nev… |
source (query) | string<registered, hosting, manual> | 否 | Only watches that arrived this way. |
limit (query) | integer | 否 | — |
offset (query) | integer | 否 | — |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
items | DomainWatch[] | 是 | — |
total | integer | 是 | The full match, so the screen can page all of it. |
此端点可能返回的错误
401 · 403