The caller's own dashboard preferences document
const url = 'https://api.tovarifinancial.com/dashboard/preferences';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.tovarifinancial.com/dashboard/preferences \ --header 'Authorization: Bearer <token>'PER-USER, not per-org: row-level security here requires user_id = current_user_id with no admin carve-out, so one household member can never read the other’s board. A user who has never saved gets 200 with [] and null rather than a 404 — “nothing watched yet” and “never customized the board” are legitimate states. Both values are PRUNED ON READ: a watched id whose category was hard-deleted, and a widget entry whose id is retired or malformed, are dropped from the response (the stored document is left untouched), so what a GET returns is always something a PUT will accept.
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”The preferences document, pruned
object
object
ORDERED — the array IS the widget’s display order. At most five.
The board layout, in display order. null means never customized; [] means reset to defaults, NOT all-hidden (all-hidden is a full-length list of visible: false).
object
A widget id from the shared allowlist. An unrecognised id is a 400 on write and is pruned on read.
Examplegenerated
{ "data": { "watchedBudgetCategoryIds": [ "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0" ], "widgets": [ { "id": "example", "visible": true } ] }, "message": "example", "requestId": "example", "timestamp": "2026-04-15T12:00:00Z"}Missing, invalid, or expired bearer token
object
Machine-readable error code (AUTH_ERROR_CODES).
Optional field-level validation errors, keyed by field name.
object
Example
{ "errorCode": "INVALID_EMAIL_FORMAT"}Authenticated, but the tenant gate refuses the request until the caller resolves a precondition. errorCode is one of EMAIL_NOT_VERIFIED, POLICY_ACCEPTANCE_REQUIRED, or SUBSCRIPTION_REQUIRED, evaluated in exactly that order (contract term CCR-1: email verification first, then policy acceptance, then subscription — so a subscriber who has merely not re-accepted the current policies always sees POLICY_ACCEPTANCE_REQUIRED). A POLICY_ACCEPTANCE_REQUIRED body additionally carries details.outstanding (the policy versions still to accept) and details.firstAcceptance. The SUBSCRIPTION_REQUIRED arm is INERT unless the server-side BILLING_ENABLED flag is exactly the string true; while it is off, only the first two codes are reachable. Not retryable as sent — resolve the named condition, then resend.
object
Which precondition refused the request. Evaluated in this order (CCR-1); SUBSCRIPTION_REQUIRED is unreachable while BILLING_ENABLED is not exactly true.
object
Active policy versions the user has not yet accepted.
object
True when the user has accepted no policy before — the client renders the new-signup screen rather than the re-acceptance one.
Example
{ "errorCode": "EMAIL_NOT_VERIFIED"}Internal error (no internal detail leaked)
object
Machine-readable error code (AUTH_ERROR_CODES).
Optional field-level validation errors, keyed by field name.
object
Example
{ "errorCode": "INVALID_EMAIL_FORMAT"}Service temporarily unavailable — errorCode is SERVICE_UNAVAILABLE. A TRANSIENT, RETRYABLE condition rather than a defect in the request: a query that exceeded its time budget, a lost or refused database connection, a saturated connection pool, or an outage at an upstream provider the request depends on (the authentication provider, or the bank data provider on a bank-connection operation). The identical request may succeed on retry — back off briefly and, on a write, resend the same X-Idempotency-Key where the operation accepts one.
object
Machine-readable error code (AUTH_ERROR_CODES).
Optional field-level validation errors, keyed by field name.
object
Example
{ "errorCode": "INVALID_EMAIL_FORMAT"}