Skip to main content
GET
List managed rules
Managed rules are Prelude’s own: a shared library every customer can score over and none can edit. Name one in a recipe by its identifier, give it a weight, and it behaves like a rule you wrote.

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’s attr. 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

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 rules 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

rules
object[]
required
next_cursor
string

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

Example:

"rul_01jc0t6fwwfgfsq1md24mhyztj"