Skip to main content
Yoshi organizes your financial data into a set of core resources. This page explains what each one represents and how to interpret key fields.

Accounts

An account represents a single financial account — a checking account, savings account, credit card, investment account, or loan. Each account belongs to a financial institution and has a current balance.
FieldDescription
typeTop-level category: depository, credit, investment, loan
subtypeMore specific: checking, savings, credit card, 401k, mortgage, etc.
balance_currentMost recent balance as reported by the institution
balance_availableAvailable to spend or withdraw (may differ from current for credit/checking)
balance_limitCredit limit (credit accounts only)
as_ofWhen the balance was last refreshed
hiddenWhether the user has hidden this account from their dashboard
balance_available may be null for accounts that don’t report available balances, such as some investment accounts.

Transactions

A transaction is a single financial event — a purchase, payment, deposit, transfer, or fee. Transactions belong to an account and include merchant information, categorization, and timing data.

Amount and direction

FieldDescription
amountSigned amount. Negative for outflows, positive for inflows.
amount_absoluteUnsigned amount (always positive). Use this for display.
cash_flow_direction"outflow" (you spent money) or "inflow" (you received money)
The sign of amount follows accounting convention — a credit card purchase appears as a positive value on a credit account but as an outflow in cash_flow_direction. Always use cash_flow_direction for logic and amount_absolute for display.

Dates

FieldDescription
date_postedWhen the transaction settled (final). Use this for reporting.
date_authorizedWhen the transaction was first authorized. May be null.
pendingtrue if the transaction hasn’t settled yet
Pending transactions may change amount, date, or disappear entirely before posting. Use the transaction id for deduplication — don’t match on amount or description.

Categories

FieldDescription
category_labelHuman-readable label, e.g. “Groceries”
category_tier1Top-level category, e.g. “Food & Drink”
category_tier2Sub-category, e.g. “Groceries”. May be null.

Merchant

FieldDescription
counterparty_nameCleaned merchant name, e.g. “Whole Foods”
counterparty_logo_urlMerchant logo URL. May be null.
original_descriptionRaw transaction description from the institution

Recurring streams

A recurring stream is a detected pattern of repeated transactions — subscriptions, monthly bills, or regular income. Yoshi identifies these automatically from transaction history.
FieldDescription
direction"outflow" (bill/subscription) or "inflow" (income)
frequencyDetected pattern: monthly, weekly, biweekly, annual, etc.
status"active" or "inactive" (stream appears to have stopped)
average_amountTypical amount based on recent occurrences
predicted_next_dateWhen the next occurrence is expected

Scores

Yoshi calculates four financial health scores, each on a 0–100 scale:
ScoreWhat it measures
yoshiComposite overall financial health
recoveryHow quickly you recover from spending dips
capacityAvailable financial cushion relative to obligations
baselineConsistency and stability of your financial patterns
Scores are recalculated daily. The observation_date field indicates when the scores were last computed.

Goals

A goal represents a financial objective the user is working toward:
FieldDescription
goal_typeWhat kind of goal: savings, debt_payoff, etc.
statusactive, paused, or completed
target_amountDollar amount the user is trying to reach
current_valueProgress toward the target
target_dateWhen the user wants to reach the goal

Income

The income resource provides an analysis of the user’s income sources:
FieldDescription
total_income_annualEstimated annual income across all sources
total_income_monthlyEstimated monthly income
income_sourcesArray of detected income streams
income_sources[].confidencehigh, medium, or low — how confident the detection is

Investments

Investment data shows the user’s holdings grouped by asset class:
FieldDescription
symbolTicker symbol, e.g. “AAPL”
current_valueMarket value of the position
quantityNumber of shares held
cost_basis_totalOriginal purchase cost
total_gain_lossUnrealized gain or loss
day_changeChange in value today
percent_of_accountPosition as a percentage of the total account (0–100)

Resource relationships

User
├── Accounts
│   ├── Transactions
│   └── Balance history
├── Recurring streams
├── Scores
├── Goals
├── Income sources
└── Investments (holdings by account)
Every resource is scoped to the authenticated user. You can only access your own data — there is no cross-user access.
Last modified on April 30, 2026