Skip to content
How to install

Plugin recipes

How the panel activates pro-plugin licenses (docs/licenses.md). Recipes come from the public catalog, the bundled files or your own JSON; what you enter for their inputs is stored per recipe, and secret inputs such as license keys are never returned.

Reading needs Read only and changes need Full, unless an endpoint says otherwise. How to read this page.

Every recipe the panel knows, whether it is installed and enabled, and what is entered for its inputs.

  • Level: Read only
  • Returns: {items: [{id, name, plugin, version, source, installed, enabled, sites, inPluginCatalog, inputs: [{id, label, secret, set, display, ...}], ...}]}

Add or replace a recipe of your own; installed and enabled at once, shadows a catalog id.

  • Level: Full
  • Notes: Destructive
  • Input: {recipe}

The recipe as the panel has it, to copy or fork.

  • Level: Read only
  • Returns: the recipe JSON

Take a known recipe into use; a catalog recipe keeps following the catalog.

  • Level: Full

Stop using a recipe and forget its key; a local recipe is deleted outright.

  • Level: Full
  • Notes: Destructive

Switch an installed recipe off or on without uninstalling it.

  • Level: Full
  • Input: {enabled}

Enter the value for one of a recipe’s inputs, such as its license key (write-only when secret).

  • Level: Full
  • Notes: Destructive
  • Input: {value}

Forget the value entered for an input.

  • Level: Full
  • Notes: Destructive

The public recipe catalog as this panel sees it: entries, last fetch, last error.

  • Level: Read only
  • Returns: {url, entries, unsupported, generatedAt, commit, fetchedAt, changedAt, error, keyId, recipes}

Fetch and verify the catalog now, ignoring the cached ETag.

  • Level: Manage. Only fetches the signed catalog now instead of within the hour
  • Returns: {outcome: "updated"|"unchanged"|"failed"|"disabled", catalog} (sync, <=15 s)