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

Tabbatar da Asali

Aika maɓallin API azaman alamar ɗauka (bearer token). Dole ne maɓallin ya kasance yana da izinin sites.view; idan babu shi, za a ƙi amfani da maɓallin tare da lambar 403, ba 404 ba.

Wannan wurin ƙarewa ba ya buƙatar ID na ƙungiya. Maɓallin ku ya riga ya gano ƙungiyar da yake ciki, kuma an iyakance amsa a kanta.

Gwada

May gurbin komai da ke cikin kusurwa da ƙimar ka, kuma may gurbin maballi da maballi daga allon sarrafa ka.

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

An shiga? Na'urar sarrafa API da ke cikin sashin kulawarka tana cika ainihin lambar ƙungiyarka da maɓallinka naka, sannan tana gudanar da buƙatar a kan ainihin API don haka zaka iya ganin amsar gaske. Buɗe wannan tashar a cikin na'urar kula da API

Bayani

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`.

Sigogi

Martani

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 404 · 429 · 503