Patch the delivery preferences (atomic)
const url = 'https://api.tovarifinancial.com/notifications/preferences';const options = { method: 'PUT', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"emailEnabled":true,"push":{"masterEnabled":true},"quietHours":{"startMinute":1,"endMinute":1},"digest":{"enabled":true,"weekday":1,"hourLocal":1},"types":[{"type":"example","inAppEnabled":true,"emailEnabled":true,"pushEnabled":true}]}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request PUT \ --url https://api.tovarifinancial.com/notifications/preferences \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "emailEnabled": true, "push": { "masterEnabled": true }, "quietHours": { "startMinute": 1, "endMinute": 1 }, "digest": { "enabled": true, "weekday": 1, "hourLocal": 1 }, "types": [ { "type": "example", "inAppEnabled": true, "emailEnabled": true, "pushEnabled": true } ] }'PATCH SEMANTICS, APPLIED ATOMICALLY: every field is optional and only supplied fields move, but the whole patch commits or none of it does. Two refusals are 400s with a field error naming the offending type code rather than silent ignores — disabling an ALWAYS-ON type (security and data-export notices), and setting pushEnabled on a type the registry marks push-unsupported. quietHours is paired or an explicit null; a wrapping range is normal, and quiet hours affect EMAIL QUEUE TIMING only — they never gate an in-app row and never delay an always-on message. The 200 is the SAME fully-resolved shape the GET returns, so a client seeds its cache from it and never re-fetches. Subscription-exempt.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Header Parameters
Section titled “Header Parameters”Optional idempotency key for safe write retries. Every operation that declares this header reads it. Three cases, told apart per operation: (1) where the operation also documents a 409 whose codes include IDEMPOTENCY_CONFLICT, replaying this key with a different payload returns 409 IDEMPOTENCY_CONFLICT and replaying it with the same payload returns the original response; (2) where it documents no 409, a replay is reconciled optimistically against a unique key column and answers the original 200; (3) where it documents a 409 whose codes do NOT include IDEMPOTENCY_CONFLICT, a conflict on this key is impossible — a replay answers a 200, and that 409 is a resource-state conflict described by the operation’s own 409 schema.
Request Bodyrequired
Section titled “Request Bodyrequired”object
object
Both 0..1439, or an explicit null to clear. A half-set range is a 400.
object
object
object
A known registry type code. An unknown code is a 400.
An UNSPECIFIED value leaves the user with no push opinion for the type, which resolves to the registry default — it is never written as true.
Examplegenerated
{ "emailEnabled": true, "push": { "masterEnabled": true }, "quietHours": { "startMinute": 1, "endMinute": 1 }, "digest": { "enabled": true, "weekday": 1, "hourLocal": 1 }, "types": [ { "type": "example", "inAppEnabled": true, "emailEnabled": true, "pushEnabled": true } ]}Responses
Section titled “Responses”The resolved preferences document, exactly as GET returns it
object
object
The STORED IANA zone. Null until an X-Client-Timezone header has ever been observed.
The zone scheduling actually uses. Never null — ‘UTC’ is the one fallback.
Paired or null; both are 0..1439. A wrapping range (22:00 -> 07:00) is normal. Affects EMAIL QUEUE TIMING only.
object
object
0..6, 0 = Sunday.
0..23, in effectiveTimezone.
object
PUSH_ENABLED AND NOTIFICATIONS_ENABLED. False renders no push UI at all, and no device row is read.
Available AND masterEnabled AND at least one live device. Server-derived; never re-computed by a client.
At most 20 LIVE rows, most-recently-seen first. Never the push token or its fingerprint.
object
The app-generated handle: 8–128 characters of A-Z, a-z, 0-9, _ or -.
object
The registry type code, e.g. bills.due_rollup. OPEN vocabulary — a newer deployment may add one.
Server-supplied heading. Clients must not carry a category-to-heading map.
The order the rows are returned in; render positionally.
Security and data-export notices. Attempting to disable one is a 400.
Served on EVERY row, always-on ones included, so no client hard-codes which types support push.
The RESOLVED answer (stored override, else the registry default). False whenever pushSupported is false.
Example
{ "data": { "push": { "devices": [ { "platform": "ios" } ] }, "types": [ { "category": "connection" } ] }}Validation failed — see errorCode / fieldErrors
object
Machine-readable error code (AUTH_ERROR_CODES).
Optional field-level validation errors, keyed by field name.
object
Example
{ "errorCode": "INVALID_EMAIL_FORMAT"}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"}Conflict. errorCode is IDEMPOTENCY_CONFLICT when an X-Idempotency-Key was replayed with a different request payload; where the operation instead detects a resource-state conflict it carries that endpoint’s own errorCode (a duplicate name, an import that is no longer committable, an account already linked to a bank connection).
object
Machine-readable error code (AUTH_ERROR_CODES).
Optional field-level validation errors, keyed by field name.
object
Example
{ "errorCode": "INVALID_EMAIL_FORMAT"}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"}