One page of the caller's own notification feed
const url = 'https://api.tovarifinancial.com/notifications?unreadOnly=1&category=connection';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/notifications?unreadOnly=1&category=connection' \ --header 'Authorization: Bearer <token>'PER-USER at the row layer: the select policy requires user_id = current_user_id with NO admin carve-out, so in a two-person household an admin cannot read a partner’s feed even by crafting a request. Keyset-paginated on (createdAt DESC, id DESC): pass the previous response’s nextCursor back as cursor. THE CURSOR IS OPAQUE — never parse or construct one; a malformed value is a 400, never a silent restart at page one. dataTrust must be rendered from THIS response rather than re-derived from GET /plaid/items’ feedFreshness, which collapses “stalled” and “quiet” into one value and would fire on an ordinary dormant account.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Page size, 1–50. Default 20. Anything else is a 400.
Opaque cursor from a previous response’s nextCursor.
Set to ‘1’ to return unread rows only. Any other value is ignored.
Restrict to one category.
Responses
Section titled “Responses”One page, newest first
object
object
object
The registry type code, e.g. connection.reauth_required. OPEN vocabulary by contract — a client must not switch exhaustively on it.
Server-rendered prose. The card renders this verbatim and never re-derives it from payload.
Per-type structured payload, discriminated on kind. An unrecognised shape resolves to { kind: 'generic' }. Every money member is integer minor units in a *Cents field.
object
How many underlying events this row rolls up, when it rolls up any.
Null on the last page. Opaque — pass it back verbatim as cursor.
The caller’s WHOLE unread count, not the count on this page.
object
TRUE only when a suppressible type is ACTUALLY being withheld under the scoped gate.
The notification type codes currently withheld. Empty when nothing is suppressed.
Example
{ "data": { "notifications": [ { "category": "connection", "severity": "info" } ], "dataTrust": { "reason": "feed_stalled" } }}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"}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"}