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

Ì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 GET https://api.zinndigital.com/v1/sites/{siteId}/php-config \
  -H "Authorization: Bearer zdk_live_…"

Ṣé 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ẹ̀

The `php.ini` settings this site's machine will let a customer change, **as the machine describes them** — each with its type (`bool`/`list`/`value`), its default, the legal values for a list, and a sentence explaining it. ⭐ The schema is the box's, not ours. A hardcoded field list would drift the first time the hosting changed a range and nothing would go red: the write would simply be refused later, at the vendor, in the vendor's words. `value` is `null` when the site is **inheriting** the default rather than having set it — a different fact from setting it to the same text, and the only one of the two that survives a change of the platform default. `supported: false` with an empty `options` list is a real answer, not an error: the hosting may publish no changeable settings at all. `reason` says which silence it is. Requires `sites.view` + `sites.panel_access`.

Àwọn ìpìlẹ̀

Idahun

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

401 · 403 · 404 · 429 · 503