Get the customer's RiseUp budget for a given month. The budget groups transactions into envelopes (categories) and shows planned vs. actual amount for each. Use this when the user asks about their budget as a whole, categories, envelopes, planned vs. actual spending, or overspending; use get_transactions instead when they ask about individual transactions or merchants.

Input parameters:

• date (string, required): The month to fetch. One of:

  • "YYYY-MM" — a specific month (e.g. "2026-05")

  • "current" — the current cashflow month

  • "previous" — the previous cashflow month

Response shape: { budgetDate: "YYYY-MM", // the month this response covers lastUpdatedAt: ISO datetime, // when the cashflow was last refreshed envelopes: [ { id: string, type: "fixed" | "variable" | "variableIncome" | "trackingCategory" | "riseupGoal", balancedAmount: number, // planned/budgeted amount for this envelope (ILS, negative for expenses) originalAmount: number, // original budgeted amount before any customer adjustment balanceDate: string, // when this envelope was last balanced isCustomPrediction: boolean, // true if customer overrode the prediction sequenceCustomerComment: string, // customer's own note about this envelope actuals: [ { transactionId: string, transactionDate: "YYYY-MM-DD", // when the transaction happened billingDate: "YYYY-MM-DD", // when it was billed businessName: string, // merchant name isIncome: boolean, // true = income, false = expense billingAmount: number | null, // ILS amount for EXPENSES; null when isIncome is true incomeAmount: number | null, // ILS amount for INCOMES; null when isIncome is false // exactly one of billingAmount / incomeAmount is non-null per transaction originalAmount: number, // amount in original currency / before conversions accountNickname: string | null, // customer-defined label for the source account, set in the RiseUp app; null if the customer hasn't set one accountNumberHash: string | null, // stable 6-character opaque identifier for the source account. Use to distinguish actuals across multiple accounts under the same source (e.g. two different Isracard cards on the same customer). Same account → same hash across every response. Not a cryptographic hash and not the raw account number. Null when no matching identifier is available. isInstallment: boolean, // true when part of a payment plan paymentNumber: number, // 1..totalNumberOfPayments (installments only) totalNumberOfPayments: number, // total installments (installments only) expense: string, // system-computed fallback category label (Hebrew), e.g. "ביגוד", "מסעדות"; used when no specific category is set // ... plus sequenceId, placement, transactionBudgetDate, isPostponed, // sourceType, source, monthsInterval when applicable } ] } ], excluded: [...], // transactions the customer marked as one-offs _meta: { source: "riseup-external-api", tokenRef: string } }

Envelope type semantics:

• 'fixed': Fixed customer expenses (rent, subscriptions, insurance) — recurring with known amounts.

• 'trackingCategory': A category the customer has chosen to track with a spending goal (e.g. "restaurants" with an 800 ILS/month target). balancedAmount here represents the goal.

• 'variable': "Other" day-to-day discretionary spending — not fixed and not in a tracked category. When users ask about "variable expenses" they mean this bucket.

• 'variableIncome': Variable (non-fixed) income — freelance, one-off payments, etc. There is no tracked-category concept for incomes.

• 'riseupGoal': A savings goal the customer set through the RiseUp product.

excluded contains transactions the customer marked as one-offs to exclude from the monthly cashflow — atypical spending they don't want counted as regular. Same shape as the transactions inside envelope actuals.

All money fields are in Israeli shekels (ILS). On each actual, billingAmount is populated for expenses and incomeAmount for incomes — exactly one is non-null per transaction (use isIncome to pick which). Envelope-level balancedAmount uses a signed convention: negative for expense categories, positive for income categories.

Get individual transactions from the customer's RiseUp cashflow, filtered by month, exact date, or merchant name. Use this when the user asks about specific transactions, purchases, or spending at particular merchants — as opposed to overall budget categories which live in get_budget.

Filters combine with AND. At least one of cashflowMonth or transactionDate is required — unfiltered queries are rejected server-side to avoid unbounded results.

Input parameters:

• cashflowMonth (string, optional): The cashflow month in "YYYY-MM" format (e.g. "2026-06"). Compute the current month from today's date if the user asks about "this month" — the API does not accept "current" or "previous".

• transactionDate (string, optional): An exact transaction date in "YYYY-MM-DD" format (e.g. "2026-06-15"). Matches transactions whose transactionDate equals this value.

• businessName (string, optional): A substring of the merchant name. Matched case-insensitively as a substring — passing "restaurant" matches "Some Restaurant Chain". Max 100 chars, no HTML/code chars (<>{}[]/"').

Response shape: { transactions: [ { transactionId: string, transactionDate: ISO datetime, // when the transaction occurred, e.g. "2026-06-15T00:00:00.000Z" — always UTC midnight; the date part is the transaction day billingDate: ISO datetime, // when it was billed (differs from transactionDate for credit cards); absent on some transactions cashflowDate: "YYYY-MM", // the cashflow month this transaction is allocated to businessName: string, // merchant name isIncome: boolean, // true = income, false = expense amount: number, // money value in ILS (absolute); use isIncome to determine direction accountNickname: string | null, // customer-defined label for the source account, set in the RiseUp app; null if the customer hasn't set one accountNumberHash: string | null, // stable 6-character opaque identifier for the source account. Use to distinguish transactions across multiple accounts under the same source (e.g. two different Isracard cards on the same customer). Same account → same hash across every response. Not a cryptographic hash and not the raw account number. Null when no matching identifier is available. isInstallment: boolean, // true if part of a payment plan installmentNumber: number, // current installment index (only meaningful when isInstallment) totalNumberOfInstallments: number, // total planned installments (only meaningful when isInstallment) totalNumberOfPayments: number, // legacy alias for totalNumberOfInstallments; may also appear isPostponed: boolean, // true if pushed to the next month's cashflow (credit-card postponement) sourceType: string, // account type enum, e.g. "creditCard", "checkingAccount" source: string, // specific source name/identifier (bank / credit-card provider) commitmentId: string | null, // populated when the transaction is part of a recurring/fixed commitment (rent, subscription, etc.); null for variable/one-off expenses. Same signal as actualType === "fixed". actualType: "fixed" | "variable", // whether the transaction is a recurring fixed expense/income or a variable/one-off. May be absent for older transactions. categoryLabel: string, // customer-facing category name (Hebrew string, e.g. "מסעדות", "ביגוד"). Can be "אחר" (other) when unclassified. categoryType: "default" | "custom" | "other", // "default": one of RiseUp's built-in system categories. "custom": a category the customer created themselves. "other": the transaction didn't fit any known category (unclassified). May be absent for older transactions. }, ... ], _meta: { source: "riseup-external-api", tokenRef: string } }

All money values are in Israeli shekels (ILS) and stored as positive numbers — use isIncome to determine income vs expense, don't infer from sign. Installment fields (installmentNumber, totalNumberOfInstallments, totalNumberOfPayments) are only meaningful when isInstallment is true. Fields that aren't populated for a given transaction may be absent.