GET /v1/sites/{siteId}/php-settings

身份验证

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

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

免费试用

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

curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/php-settings \
  -H "Authorization: Bearer zdk_live_…"

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

详细信息

Everything the site's PHP screen needs, in one read. extensions lists Tier 0 and Tier 1 as locked: true — always on, not a choice — alongside the Tier 2 extensions the customer may switch. They are rendered rather than hidden because "does this host have ImageMagick?" is one of the commonest pre-sales and migration questions there is, and an empty list answers it worse than a locked switch does. ini carries only the two customer-editable bands. The staff-only band (disable_functions, open_basedir, sendmail_path, upload_tmp_dir, expose_php and extension loading itself) is absent from the payload, not merely hidden by the panel: those directives are the per-site isolation boundary, and a customer who can edit disable_functions can re-enable shell_exec. Each capped directive carries cap — the ceiling this site's plan allows — so the panel can stop the control at the right place rather than let the customer type a value and meet a refusal. cap_raised_by_support and override_expires_at are how a staff override is made visible to the customer, which is one of the three properties docs/204 §7a requires of one. lve reports the site's resource tier and what each limit does when it is reached. ⭐ ep is the one that emits 508 Resource Limit Is Reached — a status code that names no resource, no number and no remedy, so a customer who meets it concludes the host is broken. applied_at is null when no settings have ever been pushed to the machine — a different fact from "pushed and confirmed", and the only one of the two that needs an engineer. Requires sites.view.

参数

响应

此端点可能返回的错误

401 · 403 · 404 · 429