Register a Home Screen widget push token (iOS WidgetKit or Android FCM)
const url = 'https://api.tovarifinancial.com/widget/push-tokens';const options = { method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{"platform":"ios","token":"example","apnsEnvironment":"sandbox"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.tovarifinancial.com/widget/push-tokens \ --header 'Content-Type: application/json' \ --data '{ "platform": "ios", "token": "example", "apnsEnvironment": "sandbox" }'KAN-3608 (iOS), KAN-3881 (Android). NOT a Cognito route: the bearer is a WIDGET KEY (Authorization: Bearer tvw_…), resolved exactly as GET /widget/summary resolves it, after which the app’s own verification, policy and subscription gates run as that member (not exempt). Stores the push token the widget received (the iOS extension’s WidgetKit token, or the Android app’s FCM registration token), against THIS key (one token per key; the same member’s token for the same platform moves to the presenting key), so a change made outside the app can send the widget a data-free reload signal. The body is a union on platform: an iOS body may omit platform (byte-identical to what shipped iOS extensions send); an Android body is exactly { platform: 'android', token } and must not carry apnsEnvironment. Unknown keys are refused. A re-POST of the same token changes nothing. The X-Idempotency-Key header is REQUIRED. The response never echoes the token. X-Client-Timezone is ignored.
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
Optional. A body with no platform key is iOS.
Hex of the APNs device token (lowercased by the server first).
Sandbox for a development-signed build; production for TestFlight / App Store.
object
The FCM registration token, case preserved.
Responses
Section titled “Responses”Registered (an idempotent replay answers the same)
object
object
Example
{ "data": { "registered": true }}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"}WIDGET_CREDENTIAL_INVALID — a missing, malformed, unknown, revoked or expired key, or a removed member (one indistinguishable answer)
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"}