Skip to main content
Events use a resource.action naming convention. Each event is delivered as a JSON object with the standard event envelope. You can subscribe to specific event types when creating an endpoint, or receive all events by leaving the filter empty.

Account events

Account events fire when a user’s linked financial accounts change.
A new financial account was linked.Fired when a user successfully connects a financial institution through the Yoshi link flow.
Account access was revoked.Fired when a financial account is disconnected — either by the user unlinking it or due to an institution-side error that revoked access.
Account metadata changed.Fired when an account’s name, type, or other metadata changes during a sync.

Transaction events

Transaction events fire when transactions are synced from financial institutions.
New transactions synced from an institution.Fired after new transactions are persisted during a transaction sync. The payload contains transaction IDs — fetch full details via GET /transactions.
Transaction details were modified.Fired when existing transactions are re-categorized, have merchant names corrected, or are otherwise updated by the institution.
Transactions were removed by the institution.Fired when an institution retroactively removes transactions — for example, when a pending transaction is voided.

Balance events

Account balance was refreshed.Fired when an account’s current or available balance changes during a sync.

Investment events

Investment holdings data was refreshed.Fired after an investment account sync updates holdings positions.
New investment transactions detected.Fired when new investment transactions (buys, sells, dividends) are synced.

Score events

Financial health scores were recalculated.Fired after a user’s financial health scores are recomputed based on new data.

Income events

Income stream identified or updated.Fired when income analysis detects or updates recurring income streams for a user.

Recurring events

Recurring transaction streams were re-analyzed.Fired when Yoshi re-evaluates a user’s recurring transactions (subscriptions, bills, regular transfers).
Last modified on April 17, 2026