connections
GET /v1/waap/domains
Domains protected by the organisation's WAAP account, and what the policy did.
身份验证
请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限,因此请为您的密钥赋予所需的最小权限,并通过检查响应来确认,而不是盲目假设。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织,且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值,并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/waap/domains \
-H "Authorization: Bearer zdk_live_…"已登录?您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥,并针对实时 API 运行请求,以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
Web application and API protection on the customer's own account. ⛔⛔ **`mode` is mandatory reading and no client may render a domain as "protected" without it.** `monitor` evaluates every rule, logs every match and **delivers the traffic anyway** — it produces analytics, shows threats detected, and blocks nothing. On a dashboard it is indistinguishable from `block` unless the mode is shown. `locked` is a fourth state the **provider** assigns (usually for billing) and the customer cannot change; it is not a mode they chose and a toggle will not clear it. ⛔ `total_requests` and `blocked_requests` are `null` when the provider does not report them — never `0`. "Nothing was blocked" and "we cannot see what was blocked" are opposite answers.
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
domains | WaapDomain[] | 是 | — |
此端点可能返回的错误
401 · 429