billing
GET /v1/sla/periods
Recent months for every monitored site, and what may be claimed.
身份验证
请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限，因此请为您的密钥赋予所需的最小权限，并通过检查响应来确认，而不是盲目假设。
您的组织 ID 应填在此处
此端点将 org_id 作为查询参数。不填则调用涵盖您的整个租户子树；发送该参数则将调用范围缩小到一个组织。
您的组织ID位于控制面板的API密钥屏幕上，就在密钥本身的旁边。这是您在每次调用时使用的相同ID。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/sla/periods \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
One row per monitored site per calendar month, over the last six months. Only monitors attached to a site we host appear: we do not promise uptime for a URL we do not serve, and watching URLs we do not serve is the uptime product's whole purpose. ⛔⛔ verdict has three values and they must not be folded into a boolean — met, missed, and unadjudicable when our own coverage was too thin to decide. Reading unadjudicable as met is the convenient fold and it is the one that saves us money, so it is refused here (§2.44). uptime_percent is null when no check was made: zero checks is not zero uptime. Gated on billing.view.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
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 an org… |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
policy | SlaPolicy | 是 | — |
periods | SlaPeriod[] | 是 | — |
此端点可能返回的错误
401 · 403