The household planning window and cushion, with all three previews
const url = 'https://api.tovarifinancial.com/settings/safe-to-spend';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/settings/safe-to-spend \ --header 'Authorization: Bearer <token>'NO HOUSEHOLD ID ANYWHERE — the org comes from the bearer token and nothing else. AN ABSENT ROW IS NOT AN ERROR: a household that has never saved reads the defaults (window 2, automatic) with a 200 and settings.isExplicit === false; there is no 404 on this endpoint. The response carries ALL THREE window projections, so the settings screen previews a change by selecting over projections rather than by a second request — which is also why a client must never recompute a projected figure itself.
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”The settings, the product limits, and the three projections
object
object
object
Planning window counted in scheduled paychecks.
Integer minor units. Persisted independently of cushionMode; null when never set.
The OPAQUE concurrency token — round-trip it verbatim on the next PUT. Never parse or format it; null when no row exists yet.
FALSE when no row exists: these are the defaults and the household never chose them. An absent row is a 200, never a 404.
object
Integer minor units (cents)
Integer minor units (cents)
Server-authored ceiling copy. Render THIS string — never a client-side number.
object
Calendar date, ‘YYYY-MM-DD’
Exactly three, ordered paycheckWindow 1,2,3 — the settings screen previews a change by selecting over these rather than by a second request.
object
Planning window counted in scheduled paychecks.
The figure the dashboard will render after saving THIS window, to the cent.
Always resolved — end-of-month when windowIsFallback.
Equals paycheckWindow unless windowIsFallback, when it is 0.
Integer minor units (cents)
Integer minor units (cents)
Integer minor units (cents)
Example
{ "data": { "settings": { "paycheckWindow": 1, "cushionMode": "automatic" }, "projections": [ { "paycheckWindow": 1 } ] }}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"}