hosting

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

Get a site's changeable PHP settings.

All hosting endpoints

Authentication

Send an API key as a bearer token. The key must carry the sites.view permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

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

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

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

Parameters

NameTypeRequiredWhat it is
siteId (path)UuidYesSite ID (UUIDv7).

Response

NameTypeRequiredWhat it is
supportedbooleanYesWhether this site's hosting publishes changeable PHP settings.
reasonstringYesWhy there are none, in words a customer can act on. Empty when `supported` is true.
optionsSitePhpOption[]Yes
moved_to_plan_settingsstring[]NoDirectives 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…

Errors this endpoint can return

401 · 403 · 404 · 429 · 503