POST /v1/wordpress/refresh

身份验证

请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 sites.view 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。

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

免费试用

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

curl -X POST https://api.zinndigital.com/v1/wordpress/refresh \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "site_ids": <string[]> }'

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

详细信息

Collects up to 25 sites' WordPress posture from their platforms. ⛔ Capped because each site is a real vendor conversation, and a customer with four hundred sites pressing "refresh everything" must not be able to turn their own screen into a rate-limit incident. ⛔ One site's failure never fails the call. The response reports per site, because the interesting answer on an estate is usually "eleven collected and one refused, here is which" — and a 4xx for the whole batch would hide it. A site outside the caller's scope comes back skipped, never 404, so this can never confirm whether a foreign site id exists. Requires sites.view and sites.panel_access.

请求正文

响应

此端点可能返回的错误

401 · 403 · 422 · 429