List the tenant's patient rule settings by key

The patients of the tenant that have a settings row, ascending by patientId, each with only the requested top-level keys it holds (a key it lacks is left out). refId is the patient's reference id, or null. nextCursor is null on the last page; pass it back as cursor for the next.

Signals stores settings as given and reads it only through the triggers it holds (triggers, the home's and the resident's own): what each other key means is theirs, so the object is checked for shape and size only. The default pack reads bands — per code { low?, high? }, { mode: 'baseline', pct, low?, high? } (outside either band fires; a patient's own baseline band with no sides of its own is judged alone) or "NO_THRESHOLD" — and outOfBed: { limitSeconds, enabled?, window?: { start: 'HH:MM', end: 'HH:MM', timeZone } }. A patient's own key wins over the org's; extra keys are ignored. See tech/RULES-ENGINE.md.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
keys
array of strings
required
length ≥ 1

The top-level settings keys to return, comma-separated: residentLimits,bands.

keys*
number
≥ 1

Page size, 1 to 500. Defaults to 200.

string
length ≤ 512

Opaque keyset cursor: a previous answer's nextCursor, passed back verbatim.

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json