List the recipes Prelude maintains
Beta. The request and response shapes may still change.
List the Prelude-authored recipes you can extend. To use one, create a recipe of your own with base_recipe_id set to its identifier: your recipe scores the managed recipe’s rules, which you cannot change, plus any rules you add, and sets the parameters the managed recipe exposes within their bounds.
A managed recipe is opaque: it is returned with a description, its threshold and the parameters you may set. Its rules are not returned.
base_recipe_id set to its identifier, and add the recipe to a flow.
What you can change
A recipe extending a managed recipe:- Scores the managed recipe’s rules, which Prelude maintains. They are not listed, and you cannot change or remove them.
- Can add rules of its own - yours or managed rules - with weights you choose.
- Sets the parameters the managed recipe exposes, by the keys of its
parameters, within their bounds: aBOOL, anINTorDOUBLEbetweenvalue_minandvalue_max, aSTRING, or anENUMfrom itsvalues. A parameter you leave unset uses itsdefault_value. - Moves the threshold within
threshold_bounds. Without bounds, the threshold is the managed recipe’s.
What you get, and what you don’t
A managed recipe is returned with an identifier, a description, its threshold and the parameters you may set. Its name and its rules are not returned: a managed recipe is opaque. A recipe extending it lists only the rules you add.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
Maximum number of recipes to return per page. A larger value is clamped to 200 rather than refused.
1 <= x <= 200Pagination cursor from the previous response.