hosting
GET /v1/sites/{siteId}/protection/file-permissions
Run the vendor's file-permission check on a site.
身份验证
请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 sites.view 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/protection/file-permissions \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
⛔ **This `GET` RUNS the scan — it is not a cached read.** The vendor's read *is* the check, so it walks the site's filesystem. It is an explicit *"check my permissions"* action and must never fire on mount or on window focus. `check_id` is the handle the fix needs, and it is **nullable**: null means the vendor gave us no handle, so `actionable` is false and there is nothing to apply. `recommended` on each failure is nullable for the same reason — the platform sometimes names a file without naming a mode, and a guessed `644` would be applied to the customer's file. `404` for a site with no vendor hosting package. Requires `sites.view`.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
siteId (path) | Uuid | 是 | Site ID (UUIDv7). |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
check_id | integer | 是 | The vendor's handle for this check. **Null** when the vendor gave us none, in which case there is nothing to apply and `actionable` is false. ⛔ A client never sends it back: `fi… |
public_html_wrong | boolean | 是 | Whether the document root's own mode is wrong. |
root_wrong | boolean | 是 | Whether the package root's own mode is wrong. |
failures | SitePermissionFailure[] | 是 | The individual files the check flagged. |
actionable | boolean | 是 | Whether *Fix these* can do anything: a live check handle **and** something to fix. Its own field so the button is not offered against a report that can only be refused. |
此端点可能返回的错误
401 · 403 · 404 · 429 · 503