hosting
GET /v1/sites/{siteId}/php-settings
Get a site's PHP extensions, php.ini settings and resource tier.
Упълномощаване
Изпратете API ключ като токен за носене. Ключът трябва да притежава разрешението sites.view; ключ без него се отхвърля с 403, а не с 404.
Този ендпойнт не изисква идентификатор на организация. Вашият ключ вече идентифицира организацията, към която принадлежи, и отговорът е ограничен до нея.
Опитайте
Заменете всичко в квадратни скоби със собствени стойности, а ключовия заместващ символ – с ключ от вашето табло за управление.
curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/php-settings \
-H "Authorization: Bearer zdk_live_…"Влязохте ли в профила си? API конзолата във вашето табло за управление попълва действителното идентификационно число на вашата организация и вашия собствен ключ и изпълнява заявката спрямо реалното API, за да можете да видите действителния отговор. Отворете този крайpoint в 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`.
Параметри
| Име | Тип | Задължително | Какво представлява |
|---|---|---|---|
siteId (path) | Uuid | Да | Site ID (UUIDv7). |
Отговор
| Име | Тип | Задължително | Какво представлява |
|---|---|---|---|
php_version | string | Да | The alt-php version this site runs, dotted (`8.3`). Empty if unset. |
extensions | SitePhpExtension[] | Да | — |
ini | SitePhpBandedOption[] | Да | — |
lve | SiteLveState | Да | The site's CloudLinux LVE resource tier — `docs/204` §7b. ⭐ `ep` is the limit that emits `508 Resource Limit Is Reached`, which is why this is on a customer screen at all: it co… |
applied_at | string | Да | When these settings were last confirmed by the machine. `null` means they have never been pushed — a different fact from "pushed and matched", and the only one of the two that n… |
Грешки, които този крайpoint може да върне
401 · 403 · 404 · 429