hosting

PATCH `/v1/uptime/monitors/{monitor_id}`

Pause, resume or rename a monitored address.

身份验证

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

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

免费试用

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

curl -X PATCH https://api.zinndigital.com/v1/uptime/monitors/{monitor_id} \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

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

详细信息

Gated on `uptime.manage`. ⛔ The **URL cannot be changed**: a monitor's Core Web Vitals readings are joined back to it by that canonical string, so a mutable URL would silently re-point a monitor at another address's history. Change an address by deleting the monitor and adding another. Pausing closes any open incident, so a paused monitor cannot accrue an outage out of us not looking.

参数

名称	类型	必填	内容简介
`monitor_id (path)`	`string`	是	—

请求正文

名称	类型	必填	内容简介
`enabled`	`boolean`	否	Pause or resume. Pausing closes any open incident.
`name`	`string`	否	—

响应

名称	类型	必填	内容简介
`id`	`string`	是	—
`url`	`string`	是	—
`name`	`string`	否	—
`state`	`string<unknown, up, down, paused>`	是	⛔ `unknown` is a real state and is not a synonym for `up` — it means "not checked yet" and is excluded from every uptime percentage.
`enabled`	`boolean`	是	—
`expect_text`	`string`	否	—
`site_id`	`string`	否	Set only when the address happens to be one of this organisation's own sites. Navigation only — the monitor works identically without it, and must, because the product exists to…
`last_result_at`	`string`	否	—
`last_up_at`	`string`	否	—
`last_down_at`	`string`	否	—
`created_at`	`string`	是	—
`summary`	`UptimeSummary`	否	—
`history`	`UptimeHistoryPoint[]`	否	—
`incidents`	`UptimeIncident[]`	否	—
`vitals`	`UptimeVitalsPoint[]`	否	—
`migration_offer`	`UptimeMigrationOffer`	否	—

此端点可能返回的错误

401 · 403 · 404

PATCH /v1/uptime/monitors/{monitor_id}