Get an org's rule settings
Get an org's rule settings, through Ovok's Signals gateway.
Get an org's rule settings
| Method | Path |
|---|---|
GET | /v1/signals/api/settings/org |
- Sandbox: not available
- Staging: available
- Production: unknown
Deprecated
This route is deprecated. The description below names its successor.
Deprecated: a tenant's rule settings are orgSettings on GET and PATCH /api/tenant. This route still serves the per-project rows of a tenant several projects share.
The settings for project, or the tenant-wide row without it. {} when none were written.
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?, returnSeconds?, 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.
Through ovok
- Who can call it: Manager apps, and users whose access policy grants the capabilities.
- Capabilities, all required:
signals_config:read. Project admins have every capability; client applications get no admin bypass. - Your tenant keeps one org row, the tenant-wide one, so
projectisn't taken. - Deprecated. Use
/v1/signals/api/tenant.
Request
No parameters or body.
Responses
| Status | Meaning |
|---|---|
200 | The settings. |
400 | The query carries a raw #, or more than 200 parameters. |
401 | Your ovok access token, or your client id and secret, are missing or invalid. |
403 | ovok refused the call: you lack a capability this route needs, or your session has no project. From Signals: Authenticated, but the client's role does not permit this, or it is not attached to the patient. |
409 | Your project has no Signals tenant of its own (SIGNALS_TENANT_NOT_OWN), or it is moving to another one. |
422 | project was sent, or resolvedAt is more than 5 minutes ahead of now. From Signals: project is empty or longer than 200 characters. |
429 | Too many requests. Retry after the seconds in Retry-After. |
500 | ovok hit an unexpected fault, such as your project having no Signals submitter. |
502 | Signals answered with something ovok couldn't use, or refused ovok's own credential. |
503 | Signals is unavailable. Retry after the seconds in Retry-After. |
504 | Signals did not answer in time. |
Example
curl --request GET 'https://api.sandbox.ovok.com/v1/signals/api/settings/org' \
--user "${OVOK_CLIENT_ID}:${OVOK_CLIENT_SECRET}"Last updated on