Skip to main content
GET
List managed recipes
Managed recipes are Prelude’s own: ready-made protections every customer can extend and none can edit. To use one, create a recipe with 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: a BOOL, an INT or DOUBLE between value_min and value_max, a STRING, or an ENUM from its values. A parameter you leave unset uses its default_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

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

limit
integer
default:50

Maximum number of recipes to return per page. A larger value is clamped to 200 rather than refused.

Required range: 1 <= x <= 200
cursor
string

Pagination cursor from the previous response.

Response

OK

recipes
object[]
required
next_cursor
string

Pass this back as cursor for the next page. Absent on the last page.

Example:

"rcp_01jc0t6fwwfgfsq1md24mhyztj"