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

Ìfàṣẹ́pọ̀

Fi bọ́ọ̀lù (bearer token) ranṣẹ gẹ́gẹ́ bí kọ́kọ́rọ́ API. Kọ́kọ́rọ́ náà gbọ́dọ̀ ní ìyọ̀ǹda sites.view; a ó kọ̀ ọ́ silẹ pẹlu 403, kii ṣe 404, ti kọ́kọ́rọ́ náà kò bá ní i.

Ojú abánisọ̀rọ̀ yìí kò gba id ajọ kankan. Kọ́kọ́rọ́ rẹ ti mọ ajọ ti o jẹ ti e, a o si fèsì nipa rẹ̀.

Gbiyanju rẹ

Rọ́pọ̀ èyíkéyìí nínú àwọn àmì ìtọ́ka < > pẹ̀lú iye tirẹ̀, àti àmì ìdánimọ̀ bọ́tìnnì náà pẹ̀lú bọ́tìnnì kan láti inú dásibọ̀ọ̀dù rẹ.

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

Ṣé o ti wọlé? Iwọ̀n api ní nú ìgbékalẹ̀ rẹ kún id àjọ gidi rẹ ati bọtini tirẹ, o si nṣiṣẹ ibeere na lòdì si api gidi ki o le rii esi gidi na. Ṣí ojú abáná yìí sílẹ̀ nínú kọnsólù API

Àwọn kúlẹ̀kúlẹ̀

Applies the **complete** desired state. An omitted name is cleared — 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. The change is **pushed to the machine as part of this call and read back**, so a `200` means the interpreter a visitor's request runs has actually loaded it. A value the box quietly declined is a failure here, never a success the customer discovers is untrue later. A value above the plan's ceiling is a `422` **naming the plan and the tier that would allow it**, so the panel can offer the upgrade rather than showing a dead end. A staff-only directive is also a `422` and not a `403`: the caller is entitled to change PHP settings, and this particular one is not among them — a `403` reads as "you need a different key" and sends them to support to ask for one that does not exist. Requires `sites.view` + `sites.panel_access`.

Àwọn ìpìlẹ̀

Akoonu ibeere naa

Idahun

Awọn aṣiṣe ti ibudo ipari yii le da pada

401 · 403 · 404 · 422 · 429