hosting

PUT `/v1/sites/{siteId}/php-config`

Set a site's PHP settings.

身份验证

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

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

免费试用

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

curl -X PUT https://api.zinndigital.com/v1/sites/{siteId}/php-config \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "values": <object> }'

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

详细信息

Applies the **complete** set of overrides. An omitted name is cleared, and `{}` resets every setting to the machine's defaults — deliberately not a PATCH, because *"return this to the platform default"* and *"pin it to the value that default happens to have today"* are different intentions and only a whole-set write can express the first. Values are validated against the **machine's own published range** before the vendor sees them, so a bad value is refused in our words rather than failing later as an unexplained vendor error. The write is then **read back off the machine** and a value it quietly declined is a failure here, never a success the customer discovers is untrue. `409` when the site has no machine to hold the setting. Requires `sites.view` + `sites.panel_access`.

参数

名称	类型	必填	内容简介
`siteId (path)`	`Uuid`	是	Site ID (UUIDv7).

请求正文

名称	类型	必填	内容简介
`values`	`object`	是	—

响应

名称	类型	必填	内容简介
`supported`	`boolean`	是	Whether this site's hosting publishes changeable PHP settings.
`reason`	`string`	是	Why there are none, in words a customer can act on. Empty when `supported` is true.
`options`	`SitePhpOption[]`	是	—
`moved_to_plan_settings`	`string[]`	否	Directives the vendor publishes but whose legal range is OUR policy, so they are returned by `getSitePhpSettings` (with the plan's cap) instead of here. Named rather than silent…

此端点可能返回的错误

401 · 403 · 404 · 409 · 422 · 429 · 503

PUT /v1/sites/{siteId}/php-config