GET · Applications
List, install, update, toggle or uninstall WordPress plugins
List, install, update, toggle or uninstall WordPress plugins
/api/v1/wordpress/plugins
This scope is inferred from the method and the endpoint's group — the OpenAPI document does
not carry one per operation. The wire is authoritative; whoami reports what your
token actually holds.
Description
action=list returns each plugin {name, status, version, update} and needs only read access. install needs slug (optional activate); update / activate / deactivate / uninstall need slug. Those five require write:hosting.
Query parameters
| 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 |
One of list, install, update, activate, deactivate, uninstall.
|
slug
|
string | |
path
|
string |
Up to 64 characters. Pattern ^[A-Za-z0-9._\/-]+$.
|
activate
|
boolean |
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.