Skip to main content
GET
List signals
A signal is a name Prelude resolves for the evaluation being scored: a fact about the request, the device, or the number that Prelude determines for you. Every customer gets the same signals, and each one means the same thing for all of them.

Your own values are separate

A rule can also read the attr. names a recipe declares and the param. names it is configured with. Those belong to you, they exist only in the recipe that declares them, and they are not listed here.

An absent signal is not a zero

Any signal can be missing from a given evaluation. A rule that reads a signal that did not arrive reports NOT_EVALUATED instead of scoring. It does not read the absence as false, as 0, or as an empty string. Write the condition you mean, and let the engine report the absence.

The listing grows

Prelude publishes the catalog progressively, so this listing grows over time. Treat it as the supported vocabulary: a signal it does not list is one Prelude has not committed to, so read it rather than keeping a copy.

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

signals
object[]
required
next_cursor
string

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

Example:

"hardware_manufacturer"