PUT · PHP & runtime
List or change an account's PHP extensions
List or change an account's PHP extensions
/api/v1/php/extensions
Description
action=list returns {supported, selectedVersion, extensions[]} — every extension as {name, state} (enabled, disabled or build-in; descriptions dropped). set takes extensions as a {name: "enabled"|"disabled"} map and changes only those (CloudLinux PHP Selector, account-wide). reset restores the node's default set. Writes require write:hosting.
Body
Send as application/json.
| Name | Type | Description |
|---|---|---|
input
required
|
string |
A domain, email address, website URL, or Inleed service id — for example example.se, [email protected] or 42976. Resolved to the owning account automatically, and the resolved target is echoed back in the response.
|
action
required
|
enum |
list all extensions with states, set to enable/disable the ones named in extensions, or reset to restore the node defaults. set and reset require write:hosting. One of list, set, reset.
|
extensions
|
object |
For set: a map of extension name to "enabled" or "disabled", e.g. {"imagick": "enabled"}.
|
version
|
string |
Pattern ^(\d+\.\d+|native)$.
|
Responses
The specification does not describe this response body; the note in the rail says what to expect.
Every non-2xx response is an RFC 7807 problem with a stable
code.
Commonly returned errors
The codes this operation reaches on its own path: the auth stack, its own validation and
ownership checks, and the transport. Not a closed set — a shared code from the
full registry can still surface. Each links to the code’s own page,
the same URL its type dereferences to.