@lunch-money/v2-api-spec 2.11.1-preview.1 → 2.11.1-preview.11

package/lunch-money-api-v2.yaml

@@ -2,37 +2,40 @@ openapi: 3.0.2
 info:
   title: Lunch Money API - v2
   description: |-
-    Welcome to the Lunch Money v2 API reference. This is the **v2.11.1** spec. It includes previews of the proposed `/crypto` and `/balance_history` endpoints. Only the mock service works with these endpoints.<br><br>
-    The most recent stable version of the API is v2.9.4 and is available at:
-    `https://api.lunchmoney.dev/v2`
-
-    ------------------------------------------------------------------------------------------------
-
     ### Introduction
 
+    Welcome to the Lunch Money v2 API reference. This is the **v2.11.1** spec.
+
     The API is available at `https://api.lunchmoney.dev/v2`. Get your access token from the [Lunch Money developers page](https://my.lunchmoney.app/developers).
 
-    <span class="red-text"><strong>The v2 API is in open alpha and is still subject to change. Use the mock server or a test budget when getting started.</strong></span>
+    
+    **Try it from these docs**
 
-    **Static Mock Server**
+    These docs are interactive — use **Test request** on any endpoint to call the API from this page.
+    Choose a LIVE or MOCK service from the Server dropdown.
+    Requests sent to `https://api.lunchmoney.dev/v2` can <span class="red-text"><strong>change or delete</strong></span> your data and are <span class="red-text"><strong>permanent</strong></span>.
+    See the [Getting Started Guide](https://lunchmoney.dev/v2/getting-started) before using the live API.
+    
+    **Static mock server**
 
-    Explore the API without an access token or risk to real data. Select **"Static Mock v2 Lunch Money API Server"** from the Server dropdown, then set your Bearer token to any string with 11 or more characters.
+    Explore without risk to real data. Select `http://mock.lunchmoney.dev/v2` in the Server dropdown to work with static mock data.
+    POST, PUT, and DELETE requests will return realistic responses, but do not change the mock data.
+    
 
     **Client Libraries & SDKs**
 
-    An official TypeScript SDK is available on [NPM](https://www.npmjs.com/package/@lunch-money/v2-api-spec) and [GitHub](https://github.com/lunch-money/lunch-money-js-v2). For Python or other languages, see [lunchmoney-clients](https://github.com/juftin/lunchmoney-clients) or generate a client from this OpenAPI spec.
+    An official TypeScript SDK is available on [NPM](https://www.npmjs.com/package/@lunch-money/v2-api-spec) and [GitHub](https://github.com/lunch-money/lunch-money-js-v2). For Python or other languages, see [lunchmoney-clients](https://github.com/juftin/lunchmoney-clients) or generate a client from [this OpenAPI spec](/v2/openapi).
 
     **Migrating from v1**
 
-    The v2 API is not backwards compatible with v1. See the [Migration Guide](https://alpha.lunchmoney.dev/v2/migration-guide) for details.
+    The v2 API is not backwards compatible with v1. See the [Migration Guide](https://lunchmoney.dev/v2/migration-guide) for details.
 
     **Useful links**
-    - [Developer Portal](https://alpha.lunchmoney.dev/v2/introduction)
-    - [Getting Started Guide](https://alpha.lunchmoney.dev/v2/getting-started)
-    - [v2 API Overview](https://alpha.lunchmoney.dev/v2/overview)
-    - [Version History](https://alpha.lunchmoney.dev/v2/version-history)
-    - [Migration Guide](https://alpha.lunchmoney.dev/v2/migration-guide)
-    - [Rate Limits](https://alpha.lunchmoney.dev/v2/rate-limits)
+    - [Getting Started Guide](https://lunchmoney.dev/v2/getting-started)
+    - [v2 API Overview](https://lunchmoney.dev/v2/overview)
+    - [Version History](https://lunchmoney.dev/v2/version-history)
+    - [Migration Guide](https://lunchmoney.dev/v2/migration-guide)
+    - [Rate Limits](https://lunchmoney.dev/v2/rate-limits)
   termsOfService: https://lunchmoney.dev/#current-status
   contact:
     email: devsupport@lunchmoney.app
@@ -43,17 +46,18 @@ info:
 
 servers:
   - url: https://api.lunchmoney.dev/v2
-    description: v2 Lunch Money API Server - changes will affect real data!
-#  - url: https://mock.lunchmoney.dev/v2
-  - url: https://lm-v2-api-next-a7fabcab8e9a.herokuapp.com/v2/
-    description: Static mock version of the v2 Lunch Money API Server
+    description: ⚠ LIVE — changes real Lunch Money data
+  - url: http://mock.lunchmoney.dev/v2
+    description: MOCK — static demo data, no API key required
 
 tags:
   - name: me
     description: View details and settings for the current user and account.<p>
-      Use [/me/account/settings](#tag/me/GET/me/account/settings) and
-      [/me/user/settings](#tag/me/GET/me/user/settings) for account- and
-      user-level preferences.
+      Use [/me/user/settings](#tag/me/GET/me/user/settings) for user-wide
+      preferences, [/me/account/settings](#tag/me/GET/me/account/settings) for
+      account-wide preferences, and
+      [/me/user/account/settings](#tag/me/GET/me/user/account/settings) for
+      preferences specific to the current user and budgeting account.
   - name: categories
     description: Work with categories
     externalDocs:
@@ -80,7 +84,11 @@ tags:
       description: Learn more about crypto assets
       url: https://support.lunchmoney.app/setup/crypto
   - name: balance_history
-    description: View and update historical account balances. Balance history is what drives the [Net Worth](https://my.lunchmoney.app/net-worth) views in the Lunch Money app. Balance history is generated for each account's balance on the first day of each month and can be edited in the Lunch Money app or via the API.
+    description: >-
+      View and update monthly account balances used by the
+      [Net Worth](https://my.lunchmoney.app/net-worth) views in the Lunch Money app.
+      History is monthly. The current month may be calculated on demand when
+      requested.
   - name: recurring_items
     description: Work with recurring items
     externalDocs:
@@ -994,16 +1002,19 @@ components:
           example: Cold Wallet BTC
         display_name:
           type: string
+          nullable: true
           minLength: 1
           maxLength: 45
-          description: Optional display name for the manual crypto asset. If
-            omitted, clients may derive one from `institution_name` + `name`.
+          description: Display name for the manual crypto asset. If omitted or
+            `null`, clients may derive one from `institution_name` + `name`.
           example: Cold Storage
         institution_name:
           type: string
+          nullable: true
           minLength: 1
           maxLength: 50
-          description: Optional institution or wallet provider display name
+          description: Institution or wallet provider display name. If omitted
+            or `null`, no institution name is set.
           example: Ledger
         balance:
           oneOf:
@@ -1259,15 +1270,19 @@ components:
           example: My Savings Account
         institution_name:
           type: string
+          nullable: true
           example: Bank of the West
-          description: Name of institution holding the manual account
+          description: Name of the institution holding the manual account. If
+            omitted or `null`, no institution name is set.
           minLength: 1
           maxLength: 50
         display_name:
           type: string
-          description: Display name of the manual account as set by user or
-            derived from the `institution_name` and `name` if not explicitly
-            set.<br> This must be unique for the budgeting account.
+          nullable: true
+          description: Display name of the manual account. If omitted or
+            `null`, it is derived from `institution_name` and `name`. An
+            explicitly set display name must be unique for the budgeting
+            account.
           example: Savings
         type:
           description: The type of manual account
@@ -1275,8 +1290,10 @@ components:
             - $ref: "#/components/schemas/accountTypeEnum"
         subtype:
           type: string
-          description: An optional manual account subtype. Examples include<br>
-            - retirement - checking - savings - prepaid credit card
+          nullable: true
+          description: Manual account subtype. If omitted or `null`, no subtype
+            is set. Examples include retirement, checking, savings, and prepaid
+            credit card.
           minLength: 1
           maxLength: 100
           example: prepaid credit card
@@ -1650,7 +1667,7 @@ components:
         type:
           type: string
           enum: [manual]
-          description: Identifies this entry as belonging to a manually-managed account.
+          description: Identifies this entry as belonging to a manual account.
         manual_account_id:
           type: integer
           format: int32
@@ -1679,14 +1696,14 @@ components:
 
     balanceHistorySourceCryptoManual:
       type: object
-      description: Source information for a manually-tracked cryptocurrency balance history entry.
+      description: Source information for a manual cryptocurrency balance history entry.
       additionalProperties: false
       x-internal: true
       properties:
         type:
           type: string
           enum: [crypto_manual]
-          description: Identifies this entry as belonging to a manually-tracked crypto account.
+          description: Identifies this entry as belonging to a manual crypto account.
         crypto_manual_id:
           type: integer
           format: int32
@@ -1729,10 +1746,11 @@ components:
       type: object
       x-internal: true
       description: >
-        Source information for a balance history entry whose account has since been deleted.
+        Source information for balance history whose account has since been deleted.
         Historical balances are preserved when a user chooses to keep history on account deletion.
         This object contains details that can be used to display the deleted account in the UI.
-        The `deleted_account_id` can be passed to `PUT /v2/balance_history/deleted/{account_id}/details`
+        The `deleted_account_id` can be passed to
+        [PUT /balance_history/deleted/{account_id}/details](#tag/balance-history/PUT/balance_history/deleted/{account_id}/details)
         to update the archived source metadata.
       additionalProperties: false
       properties:
@@ -1763,11 +1781,11 @@ components:
         subtype:
           type: string
           nullable: true
-          description: Archived `subtype`` of the deleted account source
+          description: Archived `subtype` of the deleted account source
         mask:
           type: string
           nullable: true
-          description: Archived account `mask` for a deleted plaid account source
+          description: Archived account `mask` for a deleted Plaid account source
         symbol:
           type: string
           nullable: true
@@ -1789,12 +1807,14 @@ components:
       type: object
       title: balance history for an account object
       additionalProperties: false
-      description: Historical balance entries grouped under a single account source.
+      description: Monthly balance entries grouped under a single account source.
       properties:
         source:
           description: >
-            Identifies the account this balance entry belongs to. The shape varies by
-            `source.type`. Use `source.type` to determine which account id field is present.
+            Identifies the account these balance entries belong to. The shape varies by
+            `source.type`. Each source type exposes a type-specific account id field
+            (`manual_account_id`, `plaid_account_id`, `crypto_manual_id`,
+            `crypto_synced_id`, or `deleted_account_id`).
           oneOf:
             - $ref: "#/components/schemas/balanceHistorySourceManual"
             - $ref: "#/components/schemas/balanceHistorySourcePlaid"
@@ -1812,38 +1832,48 @@ components:
         balances:
           type: array
           description: >
-            Monthly balance history entries for the source account. On GET responses,
-            this includes all entries in the requested range. On PUT upsert responses,
-            this includes only the entries modified by that request.
+            Monthly balance entries for this account source. A `historical` entry is
+            a stored snapshot of a past month and includes an `id`. A `current` entry
+            is an ephemeral snapshot based on the account's current balances and has
+            no balance-entry `id`. On PUT upsert responses, this array includes only
+            the `type: historical` entries modified by that request.
           items:
-            $ref: "#/components/schemas/balanceHistoryObject"
+            $ref: "#/components/schemas/balanceHistoryEntry"
       required:
         - source
         - balances
 
-    balanceHistoryObject:
+    historicalBalanceHistoryEntry:
       type: object
-      title: balance history entry object
+      title: historical balance history entry
       additionalProperties: false
       x-internal: true
-      description: A historical balance entry for a single account on a single date.
+      description: >
+        A stored monthly balance for a past month. The `id` may be used with
+        balance history entry endpoints. The balance represents the account
+        balance at or around the end of `month`.
       properties:
+        type:
+          type: string
+          enum: [historical]
+          description: Identifies this entry as a stored snapshot of a past month.
         id:
           type: integer
           format: int32
-          description: Unique identifier of this historical balance entry.
-        date:
+          description: Unique identifier for this historical balance entry.
+        month:
           type: string
-          format: date
-          description: Date of this historical balance entry in YYYY-MM-DD format. This is always the first day of a month.
+          pattern: '^\d{4}-(0[1-9]|1[0-2])$'
+          description: Calendar month for this entry in YYYY-MM format.
+          example: "2026-06"
         balance:
           type: string
           pattern: ^-?\d+(\.\d{1,4})?$
-          description: Historical balance stored for this entry, as a numeric string with up to four decimal places. Trailing zeros and decimal places are not guaranteed in responses. For manual and Plaid accounts this is in the account currency. For crypto accounts this is in the user's primary currency.
+          description: Historical balance for this entry, as a numeric string with up to four decimal places. Trailing zeros and decimal places are not guaranteed in responses. For manual and Plaid accounts this is in the account currency. For crypto accounts this is in the user's primary currency.
         currency:
           allOf:
             - $ref: "#/components/schemas/currencyEnum"
-          description: Currency of the stored `balance`. For crypto entries this is the user's primary currency.
+          description: Currency of `balance`. For crypto entries this is the user's primary currency.
         to_base:
           type: number
           format: double
@@ -1852,19 +1882,82 @@ components:
           type: string
           nullable: true
           pattern: ^-?\d+(\.\d{1,18})?$
-          description: Crypto quantity stored for this balance entry, when available. This may be present for crypto or deleted-account entries and is `null` otherwise.
+          description: Crypto quantity for this balance entry, when available. This may be present for crypto or deleted-account entries and is `null` otherwise.
       required:
+        - type
         - id
-        - date
+        - month
+        - balance
+        - currency
+        - to_base
+        - crypto_balance
+
+    currentBalanceHistoryEntry:
+      type: object
+      title: current balance history entry
+      additionalProperties: false
+      x-internal: true
+      description: >
+        An ephemeral snapshot based on the account's current balances. It may
+        change between requests.
+      properties:
+        type:
+          type: string
+          enum: [current]
+          description: Identifies this entry as an ephemeral current-month snapshot.
+        month:
+          type: string
+          pattern: '^\d{4}-(0[1-9]|1[0-2])$'
+          description: Calendar month for this entry in YYYY-MM format. For current entries this is the current month.
+          example: "2026-07"
+        balance:
+          type: string
+          pattern: ^-?\d+(\.\d{1,4})?$
+          description: Calculated balance for the current month, as a numeric string with up to four decimal places. Trailing zeros and decimal places are not guaranteed in responses. For manual and Plaid accounts this is in the account currency. For crypto accounts this is in the user's primary currency.
+        currency:
+          allOf:
+            - $ref: "#/components/schemas/currencyEnum"
+          description: Currency of the calculated `balance`. For crypto entries this is the user's primary currency.
+        to_base:
+          type: number
+          format: double
+          description: Calculated balance converted to the user's primary currency. When the entry currency is the user's primary currency, this is the numeric value of `balance`.
+        crypto_balance:
+          type: string
+          nullable: true
+          pattern: ^-?\d+(\.\d{1,18})?$
+          description: Crypto quantity for this calculated entry, when available. This may be present for crypto entries and is `null` otherwise.
+      required:
+        - type
+        - month
         - balance
         - currency
         - to_base
         - crypto_balance
 
+    balanceHistoryEntry:
+      title: balance history entry
+      x-internal: true
+      description: >
+        A monthly balance history entry. Discriminated by `type`. `historical`
+        entries are stored snapshots of past months with an `id`. `current`
+        entries are ephemeral snapshots with no balance-entry `id`.
+      oneOf:
+        - $ref: "#/components/schemas/historicalBalanceHistoryEntry"
+        - $ref: "#/components/schemas/currentBalanceHistoryEntry"
+      discriminator:
+        propertyName: type
+        mapping:
+          historical: "#/components/schemas/historicalBalanceHistoryEntry"
+          current: "#/components/schemas/currentBalanceHistoryEntry"
+
     balanceHistoryListResponseObject:
       type: object
       additionalProperties: false
       x-internal: true
+      description: >
+        List response for balance history GET endpoints. Entries are grouped by
+        account source under `balance_history`.
       properties:
         balance_history:
           type: array
@@ -1877,31 +1970,39 @@ components:
       type: object
       x-internal: true
       additionalProperties: false
+      description: >
+        A single monthly balance entry to upsert. Request bodies use this shape.
+        Responses return `type: historical` entries instead.
       properties:
         id:
           type: integer
           format: int32
           description: System-defined balance history entry id. Ignored if set.
           x-updatable: false
-        date:
+        month:
           type: string
-          format: date
-          description: Month to update, in YYYY-MM-DD format. This must be the first day of a month and must be in a past month.
+          pattern: '^\d{4}-(0[1-9]|1[0-2])$'
+          description: >
+            Calendar month to upsert, in YYYY-MM format. Must be a past month.
+            The current month cannot be written through PUT endpoints.
+          example: "2026-06"
         balance:
           oneOf:
             - type: number
               format: double
             - type: string
               pattern: ^-?\d+(\.\d{1,4})?$
-          description: Numeric value of the historical balance, up to four decimal places, as a number or string. For manual and Plaid accounts this is typically in the account currency. For crypto and deleted accounts this is typically in the user's primary currency. Do not include any special characters aside from a decimal point.
+          description: Numeric value of the historical balance, up to four decimal places, as a number or string. For manual and Plaid accounts this is in the account currency. For crypto and deleted accounts this is in the user's primary currency. Do not include any special characters aside from a decimal point.
         symbol:
           type: string
           nullable: true
           minLength: 1
           maxLength: 25
-          description: Optional for crypto balances, but if set it must match the account's symbol.
-            Tolerated for deleted-account balances. Do not provide this for manual or Plaid balances.
-            If provided when using the synced crypto path-based endpoint, this must match the symbol in the path.
+          description: >
+            Optional for crypto balances. If set, it must match the account's
+            symbol. Tolerated for deleted-account balances. Do not provide this
+            for manual or Plaid balances. On the synced crypto path endpoint, if
+            provided it must match the `symbol` path parameter.
           x-updatable: true
         crypto_balance:
           type: string
@@ -1917,10 +2018,10 @@ components:
         to_base:
           type: number
           format: double
-          description: System-defined historical balance converted to the user's primary currency. Ignored if set. Use `balance` to update the stored historical balance.
+          description: System-defined historical balance converted to the user's primary currency. Ignored if set. Use `balance` to update the historical balance.
           x-updatable: false
       required:
-        - date
+        - month
         - balance
 
     upsertBalanceHistoryRequestObject:
@@ -1931,7 +2032,11 @@ components:
         balances:
           type: array
           minItems: 1
-          description: One or more monthly balance history entries to upsert
+          description: >
+            One or more monthly balance history entries to upsert. Each entry uses
+            `month` (YYYY-MM) and `balance`. Do not include response-only fields such
+            as `type`. PUT responses return only the `type: historical` entries
+            modified by the request.
           items:
             $ref: "#/components/schemas/balanceHistoryUpdateItemObject"
       required:
@@ -1946,51 +2051,58 @@ components:
         name:
           type: string
           nullable: true
-          description: New archived account name for the deleted account source.
+          description: New archived account name for the deleted account source
         institution_name:
           type: string
           nullable: true
-          description: New archived institution name for the deleted account source.
+          description: New archived institution name for the deleted account source
         display_name:
           type: string
           nullable: true
-          description: New display name for the deleted account source.
+          description: New display name for the deleted account source
         account_type:
           type: string
           nullable: true
-          description: New archived account type for the deleted account source.
+          description: New archived account type for the deleted account source
         subtype:
           type: string
           nullable: true
-          description: New archived subtype for the deleted account source.
+          description: New archived subtype for the deleted account source
         mask:
           type: string
           nullable: true
-          description: New archived account mask for the deleted account source.
+          description: New archived account mask for the deleted account source
 
     updateBalanceHistoryDetailsResponseObject:
       type: object
       x-internal: true
       additionalProperties: false
+      description: Updated archived metadata for a deleted balance history source
       properties:
         name:
           type: string
           nullable: true
+          description: Archived account name for the deleted account source
         institution_name:
           type: string
           nullable: true
+          description: Archived institution name for the deleted account source
         display_name:
           type: string
           nullable: true
+          description: Archived display name for the deleted account source
         account_type:
           type: string
           nullable: true
+          description: Archived account type for the deleted account source
         subtype:
           type: string
           nullable: true
+          description: Archived subtype for the deleted account source
         mask:
           type: string
           nullable: true
+          description: Archived account mask for the deleted account source
       required:
         - name
         - institution_name
@@ -2946,7 +3058,7 @@ components:
         currency:
           description: Three-letter lowercase currency code of the transaction
             in ISO 4217 format. Must match one of the [supported
-            currencies](https://lm-v2-api-next-a7fabcab8e9a.herokuapp.com/v2/currencies). If not set
+            currencies](https://lunchmoney.dev/v2/currencies). If not set
             defaults to the user account's primary currency.
           allOf:
             - $ref: "#/components/schemas/currencyEnum"
@@ -3091,6 +3203,7 @@ components:
           description: |
             The new payee for the transaction.
           minLength: 0
+          x-updatable: true
         original_name:
           type: string
           nullable: true
@@ -3302,9 +3415,10 @@ components:
         category_id:
           type: integer
           format: int32
-          description: Unique identifier for associated category_id. Category
-            must already exist for the account. Will inherit category from the
-            parent if not defined.
+          nullable: true
+          description: Category ID for the child transaction. The category must
+            already exist for the account. If omitted, the child inherits the
+            parent category. If `null`, the child has no category.
         tag_ids:
           type: array
           description: The IDs of any tags to apply to this split child
@@ -3314,7 +3428,10 @@ components:
             format: int32
         notes:
           type: string
-          description: Will inherit notes from parent if not defined.
+          nullable: true
+          description: Notes for the child transaction. If omitted, the child
+            inherits the parent notes. If `null` or an empty string, the child
+            has no notes.
       required:
         - amount
 
@@ -3683,6 +3800,7 @@ components:
         - budget_rollover_left_to_budget
 
     weekStartsOnEnum:
+      x-internal: true
       type: string
       title: week starts on enum
       enum:
@@ -3691,6 +3809,7 @@ components:
       description: The day on which a calendar week begins.
 
     monthYearFormatEnum:
+      x-internal: true
       type: string
       title: month and year format enum
       description: Format string for displaying month and year values
@@ -3717,6 +3836,7 @@ components:
         - "YYYY/MM"
 
     monthDayYearFormatEnum:
+      x-internal: true
       type: string
       title: month, day and year format enum
       description: Format string for displaying full dates in the
@@ -3774,6 +3894,7 @@ components:
         - "M/DD/YYYY"
 
     monthDayFormatEnum:
+      x-internal: true
       type: string
       title: month and day format enum
       description: Format string for displaying month and day values
@@ -3816,6 +3937,98 @@ components:
         - "DD.M"
         - "DD/M"
 
+    localeEnum:
+      type: string
+      title: locale enum
+      description: Locale used for formatting numbers and currency amounts in
+        the Lunch Money app.
+      example: en-US
+      enum:
+        - sq-AL # Albanian (Albania)
+        - be-BY # Belarusian (Belarus)
+        - bg-BG # Bulgarian (Bulgaria)
+        - ca-ES # Catalan (Spain)
+        - zh-CN # Chinese (Simplified) (China)
+        - zh-HK # Chinese (Traditional) (Hong Kong)
+        - zh-TW # Chinese (Traditional) (Taiwan)
+        - hr-HR # Croatian (Croatia)
+        - cs-CZ # Czech (Czech Republic)
+        - da-DK # Danish (Denmark)
+        - nl-BE # Dutch (Belgium)
+        - nl-NL # Dutch (Netherlands)
+        - en-AU # English (Australia)
+        - en-CA # English (Canada)
+        - en-IN # English (India)
+        - en-IE # English (Ireland)
+        - en-MT # English (Malta)
+        - en-NZ # English (New Zealand)
+        - en-PH # English (Philippines)
+        - en-SG # English (Singapore)
+        - en-ZA # English (South Africa)
+        - en-GB # English (United Kingdom)
+        - en-US # English (United States)
+        - et-EE # Estonian (Estonia)
+        - fi-FI # Finnish (Finland)
+        - fr-BE # French (Belgium)
+        - fr-CA # French (Canada)
+        - fr-FR # French (France)
+        - fr-LU # French (Luxembourg)
+        - fr-CH # French (Switzerland)
+        - de-AT # German (Austria)
+        - de-DE # German (Germany)
+        - de-LU # German (Luxembourg)
+        - de-CH # German (Switzerland)
+        - el-CY # Greek (Cyprus)
+        - el-GR # Greek (Greece)
+        - iw-IL # Hebrew (Israel); modern replacement: he-IL
+        - hi-IN # Hindi (India)
+        - hu-HU # Hungarian (Hungary)
+        - is-IS # Icelandic (Iceland)
+        - in-ID # Indonesian (Indonesia); modern replacement: id-ID
+        - ga-IE # Irish (Ireland)
+        - it-IT # Italian (Italy)
+        - it-CH # Italian (Switzerland)
+        - ja-JP # Japanese (Japan)
+        - ko-KR # Korean (South Korea)
+        - lv-LV # Latvian (Latvia)
+        - lt-LT # Lithuanian (Lithuania)
+        - mk-MK # Macedonian (Macedonia)
+        - ms-MY # Malay (Malaysia)
+        - mt-MT # Maltese (Malta)
+        - no-NO # Norwegian (Norway)
+        - pl-PL # Polish (Poland)
+        - pt-BR # Portuguese (Brazil)
+        - pt-PT # Portuguese (Portugal)
+        - ro-RO # Romanian (Romania)
+        - ru-RU # Russian (Russia)
+        - sk-SK # Slovak (Slovakia)
+        - sl-SI # Slovenian (Slovenia)
+        - es-AR # Spanish (Argentina)
+        - es-BO # Spanish (Bolivia)
+        - es-CL # Spanish (Chile)
+        - es-CO # Spanish (Colombia)
+        - es-CR # Spanish (Costa Rica)
+        - es-DO # Spanish (Dominican Republic)
+        - es-EC # Spanish (Ecuador)
+        - es-SV # Spanish (El Salvador)
+        - es-GT # Spanish (Guatemala)
+        - es-HN # Spanish (Honduras)
+        - es-MX # Spanish (Mexico)
+        - es-NI # Spanish (Nicaragua)
+        - es-PA # Spanish (Panama)
+        - es-PY # Spanish (Paraguay)
+        - es-PE # Spanish (Peru)
+        - es-PR # Spanish (Puerto Rico)
+        - es-ES # Spanish (Spain)
+        - es-US # Spanish (United States)
+        - es-UY # Spanish (Uruguay)
+        - es-VE # Spanish (Venezuela)
+        - sv-SE # Swedish (Sweden)
+        - th-TH # Thai (Thailand)
+        - tr-TR # Turkish (Turkey)
+        - uk-UA # Ukrainian (Ukraine)
+        - vi-VN # Vietnamese (Vietnam)
+
     accountSettingsObject:
       type: object
       title: account settings object
@@ -3839,13 +4052,19 @@ components:
           description: Display name of the budgeting account in the Lunch Money
             app.
         locale:
-          type: string
-          description: Locale used for formatting dates and numbers in the
-            Lunch Money app (for example, `en-US`). When no locale is explicitly
-            stored for the account, the effective locale is derived from the
-            `default_locale` associated with `primary_currency` in the
-            currencies table (for example, `usd` → `en-US`, `cad` → `en-CA`,
-            `gbp` → `en-GB`).
+          allOf:
+            - $ref: "#/components/schemas/localeEnum"
+          example: en-US
+          description: Locale used for formatting numbers and currency amounts
+            in the Lunch Money app (for example, `en-US`). See
+            [Supported Locales](https://lunchmoney.dev/v2/locales) for accepted
+            values. Date presentation is configured separately through
+            [GET /me/user/settings](#tag/me/GET/me/user/settings) and
+            [PUT /me/user/settings](#tag/me/PUT/me/user/settings). When no
+            locale is explicitly stored for the account, the effective locale
+            is derived from the `default_locale` associated with
+            `primary_currency` in the currencies table (for example, `usd` →
+            `en-US`, `cad` → `en-CA`, `gbp` → `en-GB`).
         auto_create_category_rules:
           type: boolean
           default: true
@@ -3856,16 +4075,11 @@ components:
           default: true
           description: If `true`, suggested transaction rules are created
             automatically.
-        auto_review_transaction_on_update:
-          type: boolean
-          default: true
-          description: If `true`, transactions are marked as reviewed when
-            updated.
-        auto_review_transaction_on_creation:
+        include_pending_in_totals:
           type: boolean
           default: true
-          description: If `true`, transactions are marked as reviewed when
-            created.
+          description: If `true`, pending transactions are included in account
+            totals.
       required:
         - primary_currency
         - supported_currencies
@@ -3873,13 +4087,13 @@ components:
         - locale
         - auto_create_category_rules
         - auto_create_suggested_transaction_rules
-        - auto_review_transaction_on_update
-        - auto_review_transaction_on_creation
+        - include_pending_in_totals
 
     updateAccountSettingsRequestObject:
       x-internal: true
       type: object
       additionalProperties: false
+      minProperties: 1
       description: Request body for updating account settings. Include at least
         one property to update.
       properties:
@@ -3901,9 +4115,15 @@ components:
           description: If set, updates the display name of the budgeting account.
           x-updatable: true
         locale:
-          type: string
-          description: If set, updates the locale used for formatting dates and
-            numbers in the Lunch Money app.
+          allOf:
+            - $ref: "#/components/schemas/localeEnum"
+          example: en-US
+          description: If set, updates the locale used for formatting numbers
+            and currency amounts in the Lunch Money app. See
+            [Supported Locales](https://lunchmoney.dev/v2/locales) for accepted
+            values. Date presentation is configured separately through
+            [GET /me/user/settings](#tag/me/GET/me/user/settings) and
+            [PUT /me/user/settings](#tag/me/PUT/me/user/settings).
           x-updatable: true
         auto_create_category_rules:
           type: boolean
@@ -3915,15 +4135,70 @@ components:
           description: If set, updates whether suggested transaction rules are
             created automatically.
           x-updatable: true
+        include_pending_in_totals:
+          type: boolean
+          description: If set, updates whether pending transactions are included
+            in account totals.
+          x-updatable: true
+
+    userAccountSettingsObject:
+      type: object
+      title: user account settings object
+      additionalProperties: false
+      description: Settings specific to the authorized user within the current
+        budgeting account.
+      properties:
+        auto_review_transaction_on_update:
+          type: boolean
+          default: true
+          description: If `true`, transactions are marked as reviewed when their
+            date, category, payee, amount, account, or notes are changed.
+        auto_review_transaction_on_creation:
+          type: boolean
+          default: true
+          description: If `true`, new manual transactions start as reviewed. If
+            `false`, they start as unreviewed.
+        default_manual_account_id:
+          type: integer
+          nullable: true
+          description: Manual account selected by default when the user creates a
+            manual transaction in the current budgeting account. Must identify a
+            manual account returned by
+            [GET /manual_accounts](#tag/manual_accounts/GET/manual_accounts) for
+            the current budgeting account. Set to `null` to clear the selection.
+      required:
+        - auto_review_transaction_on_update
+        - auto_review_transaction_on_creation
+        - default_manual_account_id
+
+    updateUserAccountSettingsRequestObject:
+      x-internal: true
+      type: object
+      additionalProperties: false
+      minProperties: 1
+      description: Request body for updating settings specific to the authorized
+        user within the current budgeting account. Include at least one property
+        to update.
+      properties:
         auto_review_transaction_on_update:
           type: boolean
           description: If set, updates whether transactions are marked as reviewed
-            when updated.
+            when their date, category, payee, amount, account, or notes are
+            changed.
           x-updatable: true
         auto_review_transaction_on_creation:
           type: boolean
-          description: If set, updates whether transactions are marked as reviewed
-            when created.
+          description: If set, updates whether new manual transactions start as
+            reviewed or unreviewed.
+          x-updatable: true
+        default_manual_account_id:
+          type: integer
+          nullable: true
+          description: If set, updates the manual account selected by default when
+            the user creates a manual transaction in the current budgeting
+            account. Must identify a manual account returned by
+            [GET /manual_accounts](#tag/manual_accounts/GET/manual_accounts) for
+            the current budgeting account. Set to `null` to clear the selection.
           x-updatable: true
 
     userSettingsObject:
@@ -3999,6 +4274,7 @@ components:
       x-internal: true
       type: object
       additionalProperties: false
+      minProperties: 1
       description: Request body for updating user settings. Include at least one
         property to update.
       properties:
@@ -4822,22 +5098,10 @@ components:
   securitySchemes:
     bearerSecurity:
       type: http
-      # TODO Make this shorter?
-      # description: The Lunch Money API uses API keys to authenticate requests. To use
-      #   the v1 API you can view and manage your API keys on the [developers page
-      #   in the Lunch Money app](https://my.lunchmoney.app/developers). <p> To
-      #   interact with the Static Mock Server simply enter an API key of 11
-      #   characters or more. <p> To interact with the v2 service implemented on
-      #   top of the v1 API paste in a real API token associated with a Lunch
-      #   Money Budget.
-      description: To interact with the Static Mock Server simply enter an API
-        key of 11 characters or more.
+      description: >-
+        Required for the LIVE server. Optional for MOCK.
       scheme: bearer
       bearerFormat: JWT
-    cookieAuth:
-      type: apiKey
-      in: cookie
-      name: _lm_access_token
 
 paths:
   /me:
@@ -4847,11 +5111,14 @@ paths:
       summary: Get current user
       description: |-
         Get details about the user associated with the supplied authorization
-        token.<p> For account- and user-level preferences, prefer
-        [/me/account/settings](#tag/me/GET/me/account/settings) and
-        [/me/user/settings](#tag/me/GET/me/user/settings). Properties such as
-        `primary_currency` and `budget_name` remain on this response for
-        backwards compatibility.
+        token.<p> Use [/me/user/settings](#tag/me/GET/me/user/settings) for
+        user-wide preferences,
+        [/me/account/settings](#tag/me/GET/me/account/settings) for account-wide
+        preferences, and
+        [/me/user/account/settings](#tag/me/GET/me/user/account/settings) for
+        preferences specific to the current user and budgeting account.
+        Properties such as `primary_currency` and `budget_name` remain on this
+        response for backwards compatibility.
       operationId: getMe
       parameters: []
       responses:
@@ -4880,8 +5147,9 @@ paths:
       tags:
         - me
       summary: Get account settings
-      description: Returns account-level settings for the budgeting
-        account associated with the authorized API token.
+      description: >-
+        Returns settings for the current budgeting account. These settings apply
+        regardless of which user is accessing the account.
       operationId: getAccountSettings
       responses:
         "200":
@@ -4900,8 +5168,7 @@ paths:
                 locale: en-US
                 auto_create_category_rules: true
                 auto_create_suggested_transaction_rules: true
-                auto_review_transaction_on_update: true
-                auto_review_transaction_on_creation: true
+                include_pending_in_totals: true
         "401":
           $ref: "#/components/responses/unauthorizedToken"
         "429":
@@ -4914,11 +5181,10 @@ paths:
       summary: Update account settings
       description: |-
         Updates account-level settings for the budgeting account
-        associated with the authorized API token.<p> You may submit the response from a
-        `GET /me/account/settings` as the request body; however, only certain
-        properties can be updated.<p> It is also possible to provide only the
-        properties to be updated in the request body, as long as the request
-        includes at least one updatable property.
+        associated with the authorized API token. Submit the full response from
+        `GET /me/account/settings` with one or more properties changed, or
+        provide only the properties to update. The request body must include at
+        least one property.
       operationId: updateAccountSettings
       requestBody:
         required: true
@@ -4933,7 +5199,7 @@ paths:
               Update automation preferences:
                 value:
                   auto_create_category_rules: false
-                  auto_review_transaction_on_creation: false
+                  include_pending_in_totals: false
       responses:
         "200":
           description: Account settings updated successfully
@@ -4958,8 +5224,10 @@ paths:
       tags:
         - me
       summary: Get user settings
-      description: Returns user-level display and formatting preferences for the
-        user associated with the authorized API token.
+      description: >-
+        Returns display and formatting preferences for the authorized user.
+        These settings apply across every budgeting account the user owns or
+        collaborates on.
       operationId: getUserSettings
       responses:
         "200":
@@ -4990,11 +5258,10 @@ paths:
       summary: Update user settings
       description: |-
         Updates user-level display and formatting preferences for the user
-        associated with the authorized API token.<p> You may submit the response
-        from a `GET /me/user/settings` as the request body; however, only
-        certain properties can be updated.<p> It is also possible to provide
-        only the properties to be updated in the request body, as long as the
-        request includes at least one updatable property.<p> Updating
+        associated with the authorized API token. Submit the full response from
+        `GET /me/user/settings` with one or more properties changed, or provide
+        only the properties to update. The request body must include at least
+        one property.<p> Updating
         `show_debits_as_negative` affects display in the Lunch Money app only.
         Amount fields in API responses always use positive values for debits and
         negative values for credits.
@@ -5034,6 +5301,88 @@ paths:
           $ref: "#/components/responses/rateLimited"
         "500":
           $ref: "#/components/responses/serverError"
+  /me/user/account/settings:
+    get:
+      tags:
+        - me
+      summary: Get user account settings
+      description: >-
+        Returns settings specific to the authorized user within the current
+        budgeting account. These settings do not affect other users or the
+        authorized user's settings in other budgeting accounts.
+      operationId: getUserAccountSettings
+      responses:
+        "200":
+          description: Settings for the authorized user in the current budgeting
+            account
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/userAccountSettingsObject"
+              example:
+                auto_review_transaction_on_update: true
+                auto_review_transaction_on_creation: true
+                default_manual_account_id: null
+        "401":
+          $ref: "#/components/responses/unauthorizedToken"
+        "429":
+          $ref: "#/components/responses/rateLimited"
+        "500":
+          $ref: "#/components/responses/serverError"
+    put:
+      tags:
+        - me
+      summary: Update user account settings
+      description: |-
+        Updates settings specific to the authorized user within the current
+        budgeting account. Submit the full response from
+        `GET /me/user/account/settings` with one or more properties changed, or
+        provide only the properties to update. The request body must include at
+        least one property.
+      operationId: updateUserAccountSettings
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              $ref: "#/components/schemas/updateUserAccountSettingsRequestObject"
+            examples:
+              Update review preference:
+                value:
+                  auto_review_transaction_on_creation: false
+              Clear default manual account:
+                value:
+                  default_manual_account_id: null
+      responses:
+        "200":
+          description: User account settings updated successfully
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/userAccountSettingsObject"
+              examples:
+                Update review preference:
+                  value:
+                    auto_review_transaction_on_update: true
+                    auto_review_transaction_on_creation: false
+                    default_manual_account_id: null
+                Clear default manual account:
+                  value:
+                    auto_review_transaction_on_update: true
+                    auto_review_transaction_on_creation: true
+                    default_manual_account_id: null
+        "400":
+          description: Invalid request body
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/errorResponseObject"
+        "401":
+          $ref: "#/components/responses/unauthorizedToken"
+        "429":
+          $ref: "#/components/responses/rateLimited"
+        "500":
+          $ref: "#/components/responses/serverError"
   /summary:
     get:
       tags:
@@ -6281,12 +6630,9 @@ paths:
       tags:
         - crypto-manual
       summary: Get all supported cryptocurrencies
-      description: >
+      description: |-
         Retrieve the list of cryptocurrencies currently supported for manual tracking.<p>
-
-        When creating a new manual crypto balance via `POST /crypto/manual`, the
-        `symbol` you specify must match the `symbol` of one of the entries
-        returned by this endpoint.
+        When creating a new manual crypto balance via `POST /crypto/manual`, the `symbol` you specify must match the `symbol` of one of the entries returned by this endpoint.
       operationId: getAllCryptocurrencies
       responses:
         "200":
@@ -6324,16 +6670,9 @@ paths:
         - crypto-manual
       summary: Add a new supported cryptocurrency
       operationId: createCryptocurrency
-      description: >-
+      description: |-
         Adds a new cryptocurrency to the supported manual-crypto list.<br><br>
-
-        Lunch Money uses [CoinGecko](https://www.coingecko.com/us/coins/ethereum)
-        to convert crypto balances to the user's primary currency. Users add a
-        new supported cryptocurrency by submitting a CoinGecko coin-page URL.
-        The server validates the URL, extracts the id from `/coins/{id}`,
-        checks for an existing supported `coingecko_id`, validates the id
-        against CoinGecko, then confirms the resolved symbol is not already
-        supported before creating the new entry.
+        Lunch Money uses [CoinGecko](https://www.coingecko.com/us/coins/ethereum) to convert crypto balances to the user's primary currency. Users add a new supported cryptocurrency by submitting a CoinGecko coin-page URL. The server validates the URL, extracts the id from `/coins/{id}`, checks for an existing supported `coingecko_id`, validates the id against CoinGecko, then confirms the resolved symbol is not already supported before creating the new entry.
       requestBody:
         required: true
         content:
@@ -6412,8 +6751,8 @@ paths:
       tags:
         - crypto-manual
       summary: Get all manual crypto balances
-      description: Retrieve all manually managed crypto balances associated with
-        the user's account.
+      description: |-
+        Retrieve all manually managed crypto balances associated with the user's account.
       operationId: getAllCryptoManual
       responses:
         "200":
@@ -6447,11 +6786,9 @@ paths:
       tags:
         - crypto-manual
       summary: Create a manual crypto balance
-      description: >-
+      description: |-
         Create a manually managed crypto asset.<br><br>
-
-        If `display_name` is `null`, clients may derive one from
-        `institution_name` + `name`.
+        If `display_name` is `null`, clients may derive one from `institution_name` + `name`.
       operationId: createCryptoManual
       requestBody:
         required: true
@@ -6536,7 +6873,8 @@ paths:
       tags:
         - crypto-manual
       summary: Get a single manual crypto balance
-      description: Retrieve a single manually managed crypto balance by ID.
+      description: |-
+        Retrieve a single manually managed crypto balance by ID.
       operationId: getCryptoManualById
       parameters:
         - name: id
@@ -6604,11 +6942,9 @@ paths:
       tags:
         - crypto-manual
       summary: Update a manual crypto balance
-      description: >-
+      description: |-
         Modify a manually managed crypto balance.<br><br>
-
-        You may submit the response from `GET /crypto/manual/{id}` as the request body. System-defined properties
-        are accepted according to the `x-updatable` metadata in the update schema.
+        You may submit the response from `GET /crypto/manual/{id}` as the request body. System-defined properties are accepted according to the `x-updatable` metadata in the update schema.
       operationId: updateCryptoManual
       parameters:
         - name: id
@@ -6705,10 +7041,8 @@ paths:
       tags:
         - crypto-manual
       summary: Delete a manual crypto balance
-      description: Delete a single manually managed crypto asset by ID.<p> If
-        this crypto asset has a balance history, and you do not explicitly set
-        the query parameter`keep_history`, a 422 response will be returned
-        requesting you to explicitly set `keep_history` to `true` or `false`.
+      description: |-
+        Delete a single manually managed crypto asset by ID.<p> If this crypto asset has a balance history, and you do not explicitly set the query parameter`keep_history`, a 422 response will be returned requesting you to explicitly set `keep_history` to `true` or `false`.
       operationId: deleteCryptoManual
       parameters:
         - name: id
@@ -6773,8 +7107,8 @@ paths:
       tags:
         - crypto-synced
       summary: Get all synced crypto accounts
-      description: Retrieves all synced crypto accounts
-        associated with the user's account.
+      description: |-
+        Retrieves all synced crypto accounts associated with the user's account.
       operationId: getAllCryptoSynced
       responses:
         "200":
@@ -6836,8 +7170,8 @@ paths:
       tags:
         - crypto-synced
       summary: Get a single synced crypto account
-      description: Retrieves the synced crypto account and all nested balances
-        for the specified synced crypto account ID.
+      description: |-
+        Retrieves the synced crypto account and all nested balances for the specified synced crypto account ID.
       operationId: getCryptoSyncedById
       parameters:
         - name: id
@@ -6917,8 +7251,8 @@ paths:
       tags:
         - crypto-synced
       summary: Get a synced crypto balance by symbol
-      description: Retrieves a single balance from the specified synced crypto
-        account using the crypto symbol.
+      description: |-
+        Retrieves a single balance from the specified synced crypto account using the crypto symbol.
       operationId: getCryptoSyncedBalanceBySymbol
       parameters:
         - name: id
@@ -6997,8 +7331,8 @@ paths:
       tags:
         - crypto-synced
       summary: Refresh balances for a synced crypto account
-      description: Trigger a balance refresh for the specified synced crypto
-        account. Returns the refreshed synced crypto account.
+      description: |-
+        Trigger a balance refresh for the specified synced crypto account. Returns the refreshed synced crypto account.
       operationId: refreshCryptoSynced
       parameters:
         - name: id
@@ -7067,51 +7401,55 @@ paths:
       tags:
         - balance_history
       summary: Get balance history
-      description: >-
-        Retrieve historical balance entries.<br><br>
-
-        Balance history is monthly. When `start_date` and `end_date` are both provided,
-        they must be first-of-month dates. `start_date` must not be in the future,
-        while `end_date` may be in the future. If one of `start_date` or `end_date`
-        is provided, the other is required. If neither is provided, all available
-        balance history is returned.<br><br>
-
-        The response groups entries by source account. Each item in
-        `balance_history` contains a `source` object plus a `balances` array
-        containing one balance entry per month in the requested range, or all
-        stored entries when no range is provided.<br><br>
-
-        Historical entries for accounts that have been deleted may still
-        be returned. These entries use `source.type: deleted` and include
-        `deleted_account_id`, archived display fields, and account metadata on the
-        `source` object.
+      description: |-
+        Retrieve monthly balance history for all account sources.<br><br>
+        Balance history is monthly. Each entry represents the account balance at or around the end of the specified month. System-generated entries are generally captured near the boundary between months.<br><br>
+        Query with optional `start_month` and `end_month` in YYYY-MM format. The range is inclusive. If either parameter is provided, both are required. `start_month` must not be in the future. `end_month` may not be earlier than `start_month` and must not be in the future. Values must be valid calendar months in exact YYYY-MM format. A full date such as `2026-06-01` is invalid. If neither is provided, all available balance history is returned, including an ephemeral `current` entry for the current month when applicable.<br><br>
+        The response groups entries by source account. Each item in `balance_history` contains a `source` object plus a `balances` array. Within a requested range (or across all history when no range is provided), the array includes only months that have data — months with no data are omitted. A `current` entry is also included when the requested range includes the current month.<br><br>
+        Each balance entry has a `type`:<br>
+        - `historical`: stored snapshot of a past month for an active or deleted account. Includes an `id` that can be used with balance history entry endpoints<br>
+        - `current`: snapshot based on the account's current balances. It is ephemeral and may change between requests. To inspect the underlying account, use the type-specific source id for the `source.type` values:<br>
+        &nbsp;&nbsp;&nbsp;&nbsp;- `manual`: `source.manual_account_id` with [GET /manual_accounts/{id}](#tag/manual-accounts/GET/manual_accounts/{id})<br>
+        &nbsp;&nbsp;&nbsp;&nbsp;- `plaid`: `source.plaid_account_id` with [GET /plaid_accounts/{id}](#tag/plaid-accounts/GET/plaid_accounts/{id})<br>
+        &nbsp;&nbsp;&nbsp;&nbsp;- `crypto_manual`: `source.crypto_manual_id` with [GET /crypto/manual/{id}](#tag/crypto-manual/GET/crypto/manual/{id})<br>
+        &nbsp;&nbsp;&nbsp;&nbsp;- `crypto_synced`: `source.crypto_synced_id` and `source.symbol` with [GET /crypto/synced/{id}/{symbol}](#tag/crypto-synced/GET/crypto/synced/{id}/{symbol})
       operationId: getBalanceHistory
       parameters:
-        - name: start_date
+        - name: start_month
           in: query
-          description: Optional start date for the requested history range in YYYY-MM-DD format. If set, `end_date` is also required. This must be the first day of a month and must not be in the future.
+          description: >-
+            Optional start of the requested history range as a calendar month in
+            YYYY-MM format (for example `2026-06`). If set, `end_month` is also
+            required. The range is inclusive. `start_month` must not be in the
+            future. A full date such as `2026-06-01` is invalid.
           required: false
           schema:
             type: string
-            format: date
+            pattern: '^\d{4}-(0[1-9]|1[0-2])$'
           examples:
             range start:
-              summary: Start date
-              value: "2026-01-01"
-        - name: end_date
+              summary: Start month
+              value: "2026-01"
+        - name: end_month
           in: query
-          description: Optional end date for the requested history range in YYYY-MM-DD format. If set, `start_date` is also required. This must be the first day of a month. For a single month, set this to the same first-of-month date as `start_date`.
+          description: >-
+            Optional end of the requested history range as a calendar month in
+            YYYY-MM format (for example `2026-06`). If set, `start_month` is also
+            required. The range is inclusive. `end_month` may not be earlier than
+            `start_month` and must not be in the future. A full date such as
+            `2026-06-01` is invalid. For a single month, set this to the same
+            value as `start_month`.
           required: false
           schema:
             type: string
-            format: date
+            pattern: '^\d{4}-(0[1-9]|1[0-2])$'
           examples:
             range end:
-              summary: End date
-              value: "2026-03-01"
+              summary: End month
+              value: "2026-03"
       responses:
         "200":
-          description: Historical balance entries for the requested date range
+          description: Monthly balance history for the requested month range
           content:
             application/json:
               schema:
@@ -7124,14 +7462,16 @@ paths:
                           type: manual
                           manual_account_id: 119807
                         balances:
-                          - id: 101
-                            date: "2026-01-01"
+                          - type: historical
+                            id: 101
+                            month: "2026-01"
                             balance: "41000.0000"
                             currency: usd
                             to_base: 41000
                             crypto_balance: null
-                          - id: 102
-                            date: "2026-02-01"
+                          - type: historical
+                            id: 102
+                            month: "2026-02"
                             balance: "41211.8000"
                             currency: usd
                             to_base: 41211.8
@@ -7140,8 +7480,9 @@ paths:
                           type: plaid
                           plaid_account_id: 119808
                         balances:
-                          - id: 103
-                            date: "2026-01-01"
+                          - type: historical
+                            id: 103
+                            month: "2026-01"
                             balance: "5498.2800"
                             currency: usd
                             to_base: 5498.28
@@ -7151,8 +7492,9 @@ paths:
                           crypto_manual_id: 22001
                           symbol: btc
                         balances:
-                          - id: 104
-                            date: "2026-01-01"
+                          - type: historical
+                            id: 104
+                            month: "2026-01"
                             balance: "53124.7200"
                             currency: usd
                             to_base: 53124.72
@@ -7162,8 +7504,9 @@ paths:
                           crypto_synced_id: 33004
                           symbol: btc
                         balances:
-                          - id: 105
-                            date: "2026-01-01"
+                          - type: historical
+                            id: 105
+                            month: "2026-01"
                             balance: "6231.2800"
                             currency: usd
                             to_base: 6231.28
@@ -7179,12 +7522,34 @@ paths:
                           mask: "1234"
                           symbol: null
                         balances:
-                          - id: 106
-                            date: "2026-01-01"
+                          - type: historical
+                            id: 106
+                            month: "2026-01"
                             balance: "1250.0000"
                             currency: usd
                             to_base: 1250
                             crypto_balance: null
+                historical and current:
+                  summary: Historical month plus ephemeral current month
+                  value:
+                    balance_history:
+                      - source:
+                          type: manual
+                          manual_account_id: 162003
+                        balances:
+                          - type: historical
+                            id: 7437356
+                            month: "2026-06"
+                            balance: "62.8"
+                            currency: usd
+                            to_base: 62.8
+                            crypto_balance: null
+                          - type: current
+                            month: "2026-07"
+                            balance: "71.2"
+                            currency: usd
+                            to_base: 71.2
+                            crypto_balance: null
                 manual account history:
                   value:
                     balance_history:
@@ -7192,14 +7557,16 @@ paths:
                           type: manual
                           manual_account_id: 119807
                         balances:
-                          - id: 201
-                            date: "2026-01-01"
+                          - type: historical
+                            id: 201
+                            month: "2026-01"
                             balance: "41000.0000"
                             currency: usd
                             to_base: 41000
                             crypto_balance: null
-                          - id: 202
-                            date: "2026-02-01"
+                          - type: historical
+                            id: 202
+                            month: "2026-02"
                             balance: "41211.8000"
                             currency: usd
                             to_base: 41211.8
@@ -7211,8 +7578,9 @@ paths:
                           type: plaid
                           plaid_account_id: 119808
                         balances:
-                          - id: 301
-                            date: "2026-02-01"
+                          - type: historical
+                            id: 301
+                            month: "2026-02"
                             balance: "5498.2800"
                             currency: usd
                             to_base: 5498.28
@@ -7225,8 +7593,9 @@ paths:
                           crypto_synced_id: 33004
                           symbol: btc
                         balances:
-                          - id: 401
-                            date: "2026-02-01"
+                          - type: historical
+                            id: 401
+                            month: "2026-02"
                             balance: "6231.2800"
                             currency: usd
                             to_base: 6231.28
@@ -7245,8 +7614,9 @@ paths:
                           mask: "1234"
                           symbol: null
                         balances:
-                          - id: 501
-                            date: "2026-01-01"
+                          - type: historical
+                            id: 501
+                            month: "2026-01"
                             balance: "1250.0000"
                             currency: usd
                             to_base: 1250
@@ -7258,26 +7628,31 @@ paths:
               schema:
                 $ref: "#/components/schemas/errorResponseObject"
               examples:
-                missing paired date:
+                missing paired month:
                   value:
                     message: Request Validation Failure
                     errors:
-                      - errMsg: "`start_date` and `end_date` must either both be provided or both be omitted."
+                      - errMsg: "`start_month` and `end_month` must either both be provided or both be omitted."
                 invalid range:
                   value:
                     message: Request Validation Failure
                     errors:
-                      - errMsg: "`start_date` must be before or equal to `end_date`."
-                not first of month:
+                      - errMsg: "`end_month` may not be earlier than `start_month`."
+                invalid month format:
+                  value:
+                    message: Invalid Request Parameters
+                    errors:
+                      - errMsg: "Invalid value for parameter: 'start_month'. '2026-06-01' is not a valid month in YYYY-MM format."
+                future start month:
                   value:
                     message: Request Validation Failure
                     errors:
-                      - errMsg: "`start_date` and `end_date` must both be the first day of a month."
-                future start date:
+                      - errMsg: "`start_month` must not be in the future."
+                future end month:
                   value:
                     message: Request Validation Failure
                     errors:
-                      - errMsg: "`start_date` must not be in the future."
+                      - errMsg: "`end_month` must not be in the future."
         "401":
           $ref: "#/components/responses/unauthorizedToken"
         "429":
@@ -7289,23 +7664,16 @@ paths:
       tags:
         - balance_history
       summary: Get balance history for an account
-      description: >-
-        Retrieve historical balance entries for one manual, Plaid, manual crypto,
-        or deleted account.  Crypto synced accounts require an additional `symbol` path parameter.<br><br>
-
-        The `account_type` path parameter identifies the type of account and the
-        `account_id` path parameter identifies the specific id for that account type.<br><br>
-
-        When `start_date` and `end_date` are both provided, they must be first-of-month
-        dates. `start_date` must not be in the future, while `end_date` may be in the future.
-        If one of `start_date` or `end_date` is provided, the other is required. If neither is
-        provided, all available history for the source is returned.
+      description: |-
+        Retrieve monthly balance history for one manual, Plaid, manual crypto, or deleted account. For synced crypto symbol streams, use [GET /balance_history/crypto_synced/{account_id}/{symbol}](#tag/balance-history/GET/balance_history/crypto_synced/{account_id}/{symbol}).<br><br>
+        The `account_type` path parameter identifies the account family (`manual`, `plaid`, `crypto_manual`, or `deleted`) and `account_id` identifies the account within that family.<br><br>
+        `start_month`, `end_month`, and current-month entries behave as described in [GET /balance_history](#tag/balance-history/GET/balance_history).
       operationId: getBalanceHistoryForAccount
       parameters:
         - name: account_type
           in: path
           required: true
-          description: Source family to retrieve. Use `manual`, `plaid`, `crypto_manual`, or `deleted`.
+          description: Account family to retrieve. Use `manual`, `plaid`, `crypto_manual`, or `deleted`.
           schema:
             type: string
             enum: [manual, plaid, crypto_manual, deleted]
@@ -7316,23 +7684,27 @@ paths:
           schema:
             type: integer
             format: int32
-        - name: start_date
+        - name: start_month
           in: query
-          description: Optional start date for the requested history range in YYYY-MM-DD format. If set, `end_date` is also required. This must be the first day of a month and must not be in the future.
+          description: >-
+            Optional. Same format and constraints as `start_month` on
+            [GET /balance_history](#tag/balance-history/GET/balance_history).
           required: false
           schema:
             type: string
-            format: date
-        - name: end_date
+            pattern: '^\d{4}-(0[1-9]|1[0-2])$'
+        - name: end_month
           in: query
-          description: Optional end date for the requested history range in YYYY-MM-DD format. If set, `start_date` is also required. This must be the first day of a month.
+          description: >-
+            Optional. Same format and constraints as `end_month` on
+            [GET /balance_history](#tag/balance-history/GET/balance_history).
           required: false
           schema:
             type: string
-            format: date
+            pattern: '^\d{4}-(0[1-9]|1[0-2])$'
       responses:
         "200":
-          description: Historical balance entries for the requested source
+          description: Monthly balance history for the requested source
           content:
             application/json:
               schema:
@@ -7345,14 +7717,16 @@ paths:
                           type: manual
                           manual_account_id: 119807
                         balances:
-                          - id: 201
-                            date: "2026-01-01"
+                          - type: historical
+                            id: 201
+                            month: "2026-01"
                             balance: "41000.0000"
                             currency: usd
                             to_base: 41000
                             crypto_balance: null
-                          - id: 202
-                            date: "2026-02-01"
+                          - type: historical
+                            id: 202
+                            month: "2026-02"
                             balance: "41211.8000"
                             currency: usd
                             to_base: 41211.8
@@ -7371,8 +7745,9 @@ paths:
                           mask: "1234"
                           symbol: null
                         balances:
-                          - id: 501
-                            date: "2026-01-01"
+                          - type: historical
+                            id: 501
+                            month: "2026-01"
                             balance: "1250.0000"
                             currency: usd
                             to_base: 1250
@@ -7384,16 +7759,16 @@ paths:
               schema:
                 $ref: "#/components/schemas/errorResponseObject"
               examples:
-                missing paired date:
+                missing paired month:
                   value:
                     message: Request Validation Failure
                     errors:
-                      - errMsg: "`start_date` and `end_date` must either both be provided or both be omitted."
-                invalid range:
+                      - errMsg: "`start_month` and `end_month` must either both be provided or both be omitted."
+                invalid month format:
                   value:
-                    message: Request Validation Failure
+                    message: Invalid Request Parameters
                     errors:
-                      - errMsg: "`start_date` must be before or equal to `end_date`."
+                      - errMsg: "Invalid value for parameter: 'start_month'. '2026-06-01' is not a valid month in YYYY-MM format."
         "401":
           $ref: "#/components/responses/unauthorizedToken"
         "404":
@@ -7421,37 +7796,20 @@ paths:
       tags:
         - balance_history
       summary: Upsert balance history for an account
-      description: >-
-        Upsert one or more historical balance entries for a single manual, Plaid,
-        manual crypto, or deleted account. Crypto synced accounts require an additional `symbol` path parameter.<br><br>
-
-        The `account_type` path parameter identifies the type of account and the
-        `account_id` path parameter identifies the specific id for that account type.<br><br>
-
-        Submit one or more entries in the `balances` array. Each entry must specify
-        a `date` and `balance` value.<br><br>
-
-        Balance history is monthly. Each entry's `date` must be the first day of
-        a month and must be in a past month.<br><br>
-
-        `currency` may be provided for any balance entry. If omitted, it defaults
-        to the account currency for manual/Plaid accounts, or the user's primary
-        currency for crypto/deleted accounts.<br><br>
-
-        `symbol` may only be set when `account_type` is `crypto_manual` or
-        `crypto_synced`. It is optional for `crypto_manual` accounts and tolerated
-        for `deleted` accounts.<br><br>
-
-        `crypto_balance` may be provided for `crypto_manual`, `crypto_synced`, and
-        `deleted` accounts, and is invalid for `manual` or `plaid` accounts.<br><br>
-
-        The response contains only the balance entries that were submitted in this request. 
+      description: |-
+        Upsert one or more historical balance entries for a single manual, Plaid, manual crypto, or deleted account. For synced crypto symbol streams, use [PUT /balance_history/crypto_synced/{account_id}/{symbol}](#tag/balance-history/PUT/balance_history/crypto_synced/{account_id}/{symbol}).<br><br>
+        The `account_type` path parameter identifies the account family (`manual`, `plaid`, `crypto_manual`, or `deleted`) and `account_id` identifies the account within that family.<br><br>
+        Submit one or more entries in the `balances` array. Each entry must specify a `month` (YYYY-MM) and `balance` value. `month` must be a past calendar month. The current month cannot be written through this endpoint.<br><br>
+        `currency` may be provided for any balance entry. If omitted, it defaults to the account currency for manual/Plaid accounts, or the user's primary currency for crypto/deleted accounts.<br><br>
+        `symbol` may be set for `crypto_manual` (optional) and `deleted` (tolerated) accounts. Do not provide it for `manual` or `plaid` accounts.<br><br>
+        `crypto_balance` may be provided for `crypto_manual` and `deleted` accounts. It is invalid for `manual` or `plaid` accounts.<br><br>
+        The response contains only the `type: historical` balance entries that were submitted in this request.
       operationId: upsertBalanceHistoryForAccount
       parameters:
         - name: account_type
           in: path
           required: true
-          description: Source family to update. Use `manual`, `plaid`, `crypto_manual`, or `deleted`.
+          description: Account family to update. Use `manual`, `plaid`, `crypto_manual`, or `deleted`.
           schema:
             type: string
             enum: [manual, plaid, crypto_manual, deleted]
@@ -7472,21 +7830,21 @@ paths:
               manual account bulk upsert:
                 value:
                   balances:
-                    - date: "2026-03-01"
+                    - month: "2026-03"
                       balance: "41500.0000"
-                    - date: "2026-04-01"
+                    - month: "2026-04"
                       balance: "41625.5000"
               crypto manual balance with symbol:
                 value:
                   balances:
-                    - date: "2026-03-01"
+                    - month: "2026-03"
                       balance: "56011.1200"
                       symbol: btc
                       crypto_balance: "0.852341920145782301"
               deleted account bulk upsert:
                 value:
                   balances:
-                    - date: "2026-03-01"
+                    - month: "2026-03"
                       symbol: btc
                       crypto_balance: "0.020000000000000000"
                       currency: usd
@@ -7495,55 +7853,59 @@ paths:
                 value:
                   balances:
                     - id: 601
-                      date: "2026-03-01"
+                      month: "2026-03"
                       balance: "41500.0000"
                       currency: usd
                       to_base: 41500
                       crypto_balance: null
       responses:
         "200":
-          description: Returns the modified balance entries only. Other historical
-            entries for the account are omitted from `balances`.
+          description: >-
+            Returns only the `type: historical` entries modified by this request.
+            Other historical entries for the account are omitted from `balances`.
           content:
             application/json:
               schema:
                 $ref: "#/components/schemas/balanceHistoryAccountObject"
               examples:
                 manual account bulk upsert:
-                  summary: Two upserted rows returned (not full account history)
+                  summary: Two upserted entries returned (not full account history)
                   value:
                     source:
                       type: manual
                       manual_account_id: 119807
                     balances:
-                      - id: 601
-                        date: "2026-03-01"
+                      - type: historical
+                        id: 601
+                        month: "2026-03"
                         balance: "41500.0000"
                         currency: usd
                         to_base: 41500
                         crypto_balance: null
-                      - id: 602
-                        date: "2026-04-01"
+                      - type: historical
+                        id: 602
+                        month: "2026-04"
                         balance: "41625.5000"
                         currency: usd
                         to_base: 41625.5
                         crypto_balance: null
                 crypto manual balance with symbol:
-                  summary: Single upserted row returned
+                  summary: Single upserted entry returned
                   value:
                     source:
                       type: crypto_manual
                       crypto_manual_id: 22001
                       symbol: btc
                     balances:
-                      - id: 603
-                        date: "2026-03-01"
+                      - type: historical
+                        id: 603
+                        month: "2026-03"
                         balance: "56011.1200"
                         currency: usd
                         to_base: 56011.12
                         crypto_balance: "0.852341920145782301"
                 deleted account bulk upsert:
-                  summary: Single upserted row returned
+                  summary: Single upserted entry returned
                   value:
                     source:
                       type: deleted
@@ -7556,15 +7918,17 @@ paths:
                       mask: "1234"
                       symbol: btc
                     balances:
-                      - id: 504
-                        date: "2026-03-01"
+                      - type: historical
+                        id: 504
+                        month: "2026-03"
                         balance: "1255"
                         currency: usd
                         to_base: 1255
                         crypto_balance: "0.020000000000000000"
         "400":
-          description: Bad Request. The entire request is rejected if any row in
-            `balances` fails validation; no rows are updated.
+          description: >-
+            Bad Request. If any entry in `balances` fails validation, the entire
+            request is rejected and no entries are updated.
           content:
             application/json:
               schema:
@@ -7585,30 +7949,34 @@ paths:
                     message: Invalid Request Body
                     errors:
                       - errMsg: "Invalid property 'foo' in request body."
-                invalid date:
+                invalid month format:
+                  value:
+                    message: Invalid Request Body
+                    errors:
+                      - errMsg: "Invalid value for property 'balances.0.month'. '2026-06-01' is not a valid month in YYYY-MM format."
+                current month:
                   value:
                     message: Request Validation Failure
                     errors:
-                      - errMsg: "`date` must be the first day of a month."
+                      - errMsg: "`month` must not be the current month."
                         request_balances_index: 0
-                        code: VALIDATION_ERROR
-                future date:
+                future month:
                   value:
                     message: Request Validation Failure
                     errors:
-                      - errMsg: "`date` must be in a past month."
+                      - errMsg: "`month` must not be in the future."
                         request_balances_index: 1
                 crypto balance not allowed:
                   value:
                     message: Request Validation Failure
                     errors:
-                      - errMsg: "`crypto_balance` may only be set when `account_type` is `crypto_manual`, `crypto_synced`, or `deleted`."
+                      - errMsg: "`crypto_balance` may only be set when `account_type` is `crypto_manual` or `deleted`."
                         request_balances_index: 0
-                invalid row in bulk request:
+                invalid entry in bulk request:
                   value:
                     message: Request Validation Failure
                     errors:
-                      - errMsg: "`symbol` may only be set when `account_type` is `crypto_manual` or `crypto_synced`."
+                      - errMsg: "`symbol` may only be set when `account_type` is `crypto_manual` or `deleted`."
                         request_balances_index: 1
         "401":
           $ref: "#/components/responses/unauthorizedToken"
@@ -7630,15 +7998,14 @@ paths:
       tags:
         - balance_history
       summary: Delete all balance history for an account
-      description: >-
-        Delete all historical balance entries for a single manual, Plaid,
-        manual crypto, or deleted account. Crypto synced accounts require an additional `symbol` path parameter.
+      description: |-
+        Delete all historical balance entries for a single manual, Plaid, manual crypto, or deleted account. For synced crypto symbol streams, use [DELETE /balance_history/crypto_synced/{account_id}/{symbol}](#tag/balance-history/DELETE/balance_history/crypto_synced/{account_id}/{symbol}).
       operationId: deleteBalanceHistoryForAccount
       parameters:
         - name: account_type
           in: path
           required: true
-          description: Source family to delete. Use `manual`, `plaid`, `crypto_manual`, or `deleted`.
+          description: Account family to delete. Use `manual`, `plaid`, `crypto_manual`, or `deleted`.
           schema:
             type: string
             enum: [manual, plaid, crypto_manual, deleted]
@@ -7675,16 +8042,10 @@ paths:
       tags:
         - balance_history
       summary: Get balance history for a synced crypto symbol
-      description: >-
-        Retrieve historical balance entries for a single synced crypto symbol stream.<br><br>
-
-        Use the `crypto_synced` account id together with a `symbol` path parameter
-        to select one balance stream within that synced crypto account.<br><br>
-
-        When `start_date` and `end_date` are both provided, they must be first-of-month
-        dates. `start_date` must not be in the future, while `end_date` may be in the future.
-        If one of `start_date` or `end_date` is provided, the other is required. If neither is
-        provided, all available history for the symbol stream is returned.
+      description: |-
+        Retrieve monthly balance history for a single synced crypto symbol stream.<br><br>
+        The path selects one balance stream with a synced crypto account id and `symbol`.<br><br>
+        `start_month`, `end_month`, and current-month entries behave as described in [GET /balance_history](#tag/balance-history/GET/balance_history).
       operationId: getBalanceHistoryForCryptoSynced
       parameters:
         - name: account_id
@@ -7702,23 +8063,27 @@ paths:
             type: string
             minLength: 1
             maxLength: 25
-        - name: start_date
+        - name: start_month
           in: query
-          description: Optional start date for the requested history range in YYYY-MM-DD format. If set, `end_date` is also required. This must be the first day of a month and must not be in the future.
+          description: >-
+            Optional. Same format and constraints as `start_month` on
+            [GET /balance_history](#tag/balance-history/GET/balance_history).
           required: false
           schema:
             type: string
-            format: date
-        - name: end_date
+            pattern: '^\d{4}-(0[1-9]|1[0-2])$'
+        - name: end_month
           in: query
-          description: Optional end date for the requested history range in YYYY-MM-DD format. If set, `start_date` is also required. This must be the first day of a month.
+          description: >-
+            Optional. Same format and constraints as `end_month` on
+            [GET /balance_history](#tag/balance-history/GET/balance_history).
           required: false
           schema:
             type: string
-            format: date
+            pattern: '^\d{4}-(0[1-9]|1[0-2])$'
       responses:
         "200":
-          description: Historical balance entries for the synced crypto symbol stream
+          description: Monthly balance history for the synced crypto symbol stream
           content:
             application/json:
               schema:
@@ -7730,8 +8095,9 @@ paths:
                       crypto_synced_id: 33004
                       symbol: btc
                     balances:
-                      - id: 401
-                        date: "2026-02-01"
+                      - type: historical
+                        id: 401
+                        month: "2026-02"
                         balance: "6231.2800"
                         currency: usd
                         to_base: 6231.28
@@ -7743,16 +8109,16 @@ paths:
               schema:
                 $ref: "#/components/schemas/errorResponseObject"
               examples:
-                missing paired date:
+                missing paired month:
                   value:
                     message: Request Validation Failure
                     errors:
-                      - errMsg: "`start_date` and `end_date` must either both be provided or both be omitted."
-                invalid range:
+                      - errMsg: "`start_month` and `end_month` must either both be provided or both be omitted."
+                invalid month format:
                   value:
-                    message: Request Validation Failure
+                    message: Invalid Request Parameters
                     errors:
-                      - errMsg: "`start_date` must be before or equal to `end_date`."
+                      - errMsg: "Invalid value for parameter: 'start_month'. '2026-06-01' is not a valid month in YYYY-MM format."
         "401":
           $ref: "#/components/responses/unauthorizedToken"
         "404":
@@ -7780,28 +8146,14 @@ paths:
       tags:
         - balance_history
       summary: Upsert balance history for a synced crypto symbol
-      description: >-
-        Upsert one or more historical balance entries for a single synced crypto
-        symbol stream.<br><br>
-
+      description: |-
+        Upsert one or more historical balance entries for a single synced crypto symbol stream.<br><br>
         The path identifies both the synced crypto account and the symbol being updated.<br><br>
-
-        Submit one or more entries in the `balances` array. Each entry must specify
-        a `date` and `balance` value.<br><br>
-
-        Balance history is monthly. Each entry's `date` must be the first day of
-        a month and must be in a past month.<br><br>
-
-        The request body may include an optional `symbol` on each balance entry. If
-        provided, it must match the `symbol` path parameter. Omit `symbol` to use
-        the path value.<br><br>
-
-        `currency` may be provided for any balance entry. If omitted, it defaults
-        to the user's primary currency for synced crypto balances.<br><br>
-
+        Submit one or more entries in the `balances` array. Each entry must specify a `month` (YYYY-MM) and `balance` value. `month` must be a past calendar month. The current month cannot be written through this endpoint.<br><br>
+        The request body may include an optional `symbol` on each balance entry. If provided, it must match the `symbol` path parameter. Omit `symbol` to use the path value.<br><br>
+        `currency` may be provided for any balance entry. If omitted, it defaults to the user's primary currency for synced crypto balances.<br><br>
         `crypto_balance` may be provided for synced crypto balances.<br><br>
-
-        The response contains only the balance entries that were submitted in this request. 
+        The response contains only the `type: historical` balance entries that were submitted in this request.
       operationId: upsertBalanceHistoryForCryptoSynced
       parameters:
         - name: account_id
@@ -7829,44 +8181,49 @@ paths:
               synced crypto bulk upsert:
                 value:
                   balances:
-                    - date: "2026-03-01"
+                    - month: "2026-03"
                       balance: "6400.0000"
                       crypto_balance: "0.100020003000400050"
-                    - date: "2026-04-01"
+                    - month: "2026-04"
                       balance: "6500.0000"
                       crypto_balance: "0.100020003000400050"
       responses:
         "200":
-          description: Returns the modified balance entries only. Other historical
-            entries for the symbol stream are omitted from `balances`.
+          description: >-
+            Returns only the `type: historical` entries modified by this request.
+            Other historical entries for the symbol stream are omitted from
+            `balances`.
           content:
             application/json:
               schema:
                 $ref: "#/components/schemas/balanceHistoryAccountObject"
               examples:
                 synced crypto bulk upsert:
-                  summary: Two upserted rows returned (not full symbol history)
+                  summary: Two upserted entries returned (not full symbol history)
                   value:
                     source:
                       type: crypto_synced
                       crypto_synced_id: 33004
                       symbol: btc
                     balances:
-                      - id: 604
-                        date: "2026-03-01"
+                      - type: historical
+                        id: 604
+                        month: "2026-03"
                         balance: "6400.0000"
                         currency: usd
                         to_base: 6400
                         crypto_balance: "0.100020003000400050"
-                      - id: 605
-                        date: "2026-04-01"
+                      - type: historical
+                        id: 605
+                        month: "2026-04"
                         balance: "6500.0000"
                         currency: usd
                         to_base: 6500
                         crypto_balance: "0.100020003000400050"
         "400":
-          description: Bad Request. The entire request is rejected if any row in
-            `balances` fails validation; no rows are updated.
+          description: >-
+            Bad Request. If any entry in `balances` fails validation, the entire
+            request is rejected and no entries are updated.
           content:
             application/json:
               schema:
@@ -7882,17 +8239,22 @@ paths:
                     message: Invalid Request Body
                     errors:
                       - errMsg: "Invalid value for property 'balances'. Array must contain at least 1 element(s)"
-                invalid date:
+                invalid month format:
+                  value:
+                    message: Invalid Request Body
+                    errors:
+                      - errMsg: "Invalid value for property 'balances.0.month'. '2026-06-01' is not a valid month in YYYY-MM format."
+                current month:
                   value:
                     message: Request Validation Failure
                     errors:
-                      - errMsg: "`date` must be the first day of a month."
+                      - errMsg: "`month` must not be the current month."
                         request_balances_index: 0
-                future date:
+                future month:
                   value:
                     message: Request Validation Failure
                     errors:
-                      - errMsg: "`date` must be in a past month."
+                      - errMsg: "`month` must not be in the future."
                         request_balances_index: 1
                 symbol mismatch:
                   value:
@@ -7900,9 +8262,9 @@ paths:
                     errors:
                       - errMsg: "`symbol` in request body (doge) does not match the path symbol (eth)."
                         request_balances_index: 0
-                invalid row in bulk request:
+                invalid entry in bulk request:
                   value:
-                    message: Request Validation Failure
+                    message: Invalid Request Body
                     errors:
                       - errMsg: "`balance` must be a valid numeric string or number."
                         request_balances_index: 1
@@ -7933,11 +8295,9 @@ paths:
       tags:
         - balance_history
       summary: Delete all balance history for a synced crypto symbol
-      description: >-
+      description: |-
         Delete all historical balance entries for a single synced crypto symbol stream.<br><br>
-
-        The path identifies both the synced crypto account and the symbol whose
-        history should be deleted.
+        The path identifies both the synced crypto account and the symbol whose history should be deleted.
       operationId: deleteBalanceHistoryForCryptoSynced
       parameters:
         - name: account_id
@@ -7979,14 +8339,14 @@ paths:
       tags:
         - balance_history
       summary: Delete a balance history entry
-      description: >-
-        Delete a single monthly balance history entry by its id.
+      description: |-
+        Delete a single stored (`type: historical`) monthly balance history entry by its id. Ephemeral `current` entries cannot be deleted this way.
       operationId: deleteBalanceHistoryEntry
       parameters:
         - name: id
           in: path
           required: true
-          description: Balance history row identifier to delete.
+          description: Historical balance entry identifier to delete.
           schema:
             type: integer
             format: int32
@@ -8000,7 +8360,7 @@ paths:
               schema:
                 $ref: "#/components/schemas/errorResponseObject"
               example:
-                message: Request Validation Failure
+                message: Invalid Path Parameters
                 errors:
                   - errMsg: "Invalid value type for path parameter: 'id'. Expected 'number', received 'string'."
         "401":
@@ -8024,12 +8384,9 @@ paths:
       tags:
         - balance_history
       summary: Update details for a deleted account
-      description: >-
+      description: |-
         Update archived metadata for a deleted balance history source.<br><br>
-
-        Pass the `deleted` source id returned on `source.deleted_account_id`.
-        This endpoint updates the stored deleted-source metadata used for all
-        historical entries associated with that deleted source.
+        Pass the `deleted_account_id` from a `source.type: deleted` entry. The update applies to all historical entries associated with that deleted source.
       operationId: updateBalanceHistoryDetails
       parameters:
         - name: account_id
@@ -9103,19 +9460,19 @@ paths:
           description: Sets the maximum number of transactions to return. If
             more match the filter criteria, the response will include a
             `has_more` attribute set to `true`. See
-            [Pagination](https://lm-v2-api-next-a7fabcab8e9a.herokuapp.com/v2/pagination)
+            [Pagination](https://lunchmoney.dev/v2/pagination)
         - name: offset
           in: query
           schema:
             type: integer
           description: Sets the offset for the records returned. This is
             typically set automatically in the header. See
-            [Pagination](https://lm-v2-api-next-a7fabcab8e9a.herokuapp.com/v2/pagination)
+            [Pagination](https://lunchmoney.dev/v2/pagination)
       responses:
         "200":
           description: Returns an array of transactions. <br><br>The `has_more`
             property is set to `true` if more transactions are available. See
-            [Pagination](https://lm-v2-api-next-a7fabcab8e9a.herokuapp.com/v2/pagination)
+            [Pagination](https://lunchmoney.dev/v2/pagination)
           content:
             application/json:
               schema:
@@ -11339,9 +11696,8 @@ paths:
         - transactions (files)
       summary: Attach a file to a transaction
       operationId: attachFileToTransaction
-      description: >-
-        Attaches a file to a transaction. The file must be less than 10MB in size.<br><br>
-        The file will be attached to the transaction and can be downloaded from the link returned by a `GET /transactions/attachments/{file_id}` request.
+      description: |-
+        Attaches a file to a transaction. The file must be less than 10MB in size.<br><br> The file will be attached to the transaction and can be downloaded from the link returned by a `GET /transactions/attachments/{file_id}` request.
       parameters:
         - name: transaction_id
           in: path
@@ -11424,8 +11780,8 @@ paths:
   /transactions/attachments/{file_id}:
     get:
       summary: Get a url to download a file attachment
-      description: Returns a signed url that can be used to download the file
-        attachment.
+      description: |-
+        Returns a signed url that can be used to download the file attachment.
       operationId: getTransactionAttachmentUrl
       tags:
         - transactions (files)
@@ -12320,4 +12676,3 @@ paths:
 
 security:
   - bearerSecurity: []
-  - cookieAuth: []