Events

Event contracts for the Insight Service on the default EventBridge bus. Rules and queues are in Infrastructure; flow behaviour is on the linked pages.

Published

Field Value

Event type

user_new_insights_available

Source

insight-service.miner

Payload

The user ID as a bare string inside the standard fmsdk event envelope (version v1). The envelope id is a hash of the payload, so every event for a user carries the same id; nothing identifies the upload run

Published by

site-insight-miner, at least once per completed Pave upload run — Miner. A redelivered SQS message republishes it and a failed publish is dropped, so consumers must treat the event as an idempotent signal to refresh, not a count of runs

Consumers

Downstream services subscribe with their own EventBridge rules; none is defined in this repository

Consumed

Each inbound event is tapped from EventBridge into a dedicated SQS queue with a DLQ.

Event Source Queue Handled by

new_account

txn-service.feeder

site-insight-balance-alert-event-tap

balance-alert — Balance Alerts. detail is an account object (user_id, is_main, balances)

new_bank_account_added

txn-service.api

site-insight-institution-change-handler-sqs-tap

institution-change-handler — Institution Change. Payload {user_id, account_id}

user_new_txns_batch_completed

txn-service.refiner

site-insight-savings-snapshot-event-tap

savings-snapshot — Savings Snapshot. Payload is the user ID string

The feeder’s Kinesis input and the Pave webhook are not EventBridge events; see Pave Mining.