List the rules Prelude maintains
Beta. The request and response shapes may still change.
List the Prelude-authored rules every customer shares. These are the shared library a recipe may draw on alongside your own rules: reference one in a recipe by its identifier, give it a weight, and it scores like any other.
A managed rule is returned without its expression, and with a description in place of a name. A managed rule reads only Prelude signals, so it can never reference a recipe’s attributes or parameters.
What you get, and what you don’t
A managed rule is returned with an identifier, a type, and a description. It carries no expression, and a description stands in for the name. The identifier is always disclosed, which is what matters in practice: a rule whose condition you can’t read is still one you can reweight, switch off, or ask us about.What they can read
A managed rule reads Prelude signals only. It can never reference a recipe’sattr. or param. names - a recipe referencing one that does is refused, because a shared rule bound to one customer’s recipe stops being shared.
Writing to a managed rule’s identifier is refused with managed_rule_read_only. Reading one through Get a rule answers 404: it exists, but not as something you own.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
Maximum number of rules to return per page. A larger value is clamped to 200 rather than refused.
1 <= x <= 200Pagination cursor from the previous response.