Skip to main content

Install a plugin from a registry

POST 

/plugins/:id/install

Downloads the release, checks its sha256 and signature against the keys of the registry it comes from, loads it, grants the capabilities it declares and starts it along with any installed dependency that is off. Without a version the newest compatible release is used; naming an older one pins the plugin there. A bundled plugin at its shipped version needs no download. capabilities must list exactly what the consent prompt showed; when it differs from what the release asks for, nothing is downloaded and the answer is 409 CONSENT_MISMATCH with the real list.

Request​

Responses​

The installed version and the plugin's state.