Read data
The order of sources the merged view ranks by
GET
The user's own orders, keyed by metric (a quantity type, sleep or workouts), by
group (activity, heart, recovery, body, sleep, workouts) or * for every
metric, and the built-in orders that apply where the user set none. The most specific
order wins: metric, then group, then the user's *, then the built-in group order. A
source missing from an order ranks after every listed one. See docs/data-model.md.
tenantKeyheader
AuthorizationBearer <token>Tenant API key, ohs_sk_ + 43 base62 characters.
id*stringFormat
uuidThe orders.
application/json- response
priorities*Orders of source slugs, best first, keyed by metric, group or *.
defaults*Orders of source slugs, best first, keyed by metric, group or *.
curl -X GET 'http://localhost:8080/v1/users/497f6eca-6276-4993-bfeb-53cbbbba6f08/source-priorities' \ -H 'Authorization: Bearer ohs_sk_...'{ "priorities": { "property1": [ "string" ], "property2": [ "string" ] }, "defaults": { "property1": [ "string" ], "property2": [ "string" ] }}