@lunch-money/developer-docs 2.11.2-preview.9 → 2.11.3-preview.1

package/v1/_user.md

@@ -11,8 +11,8 @@ This API (v1) will not progress to a generally available state. For new projects
 | user_id        | number | false    | Unique identifier for user                                                              |
 | user_name      | string | false    | User's name                                                                             |
 | user_email     | string | false    | User's email                                                                            |
-| account_id     | number | false    | Unique identifier for the associated budgeting account                                  |
-| budget_name    | string | false    | Name of the associated budgeting account                                                |
+| account_id     | number | false    | Unique identifier for the associated budget account                                     |
+| budget_name    | string | false    | Name of the associated budget account                                                   |
 | primary_currency|string | false    | Primary currency from user's settings                                                   |
 | api_key_label  | string | true     | User-defined label of the developer API key used. Returns null if nothing has been set. |
 

package/v2/docs/intro-to-v2.md

@@ -10,7 +10,7 @@ All API requests require a Bearer token in the `Authorization` header:
 Authorization: Bearer YOUR_ACCESS_TOKEN
 ```
 
-Use a personal access token for API exploration or work with your own budgeting account. The [Getting started guide](/getting-started) walks through creating one on the <a href="https://my.lunchmoney.app/developers" target="_blank" rel="noopener noreferrer">Lunch Money Developers page</a> and making your first request. Applications built for other Lunch Money users should use an [OAuth access token issued after the user authorizes the application](/oauth).
+Use a personal access token for API exploration or work with your own budget account. The [Getting started guide](/getting-started) walks through creating one on the <a href="https://my.lunchmoney.app/developers" target="_blank" rel="noopener noreferrer">Lunch Money Developers page</a> and making your first request. Applications built for other Lunch Money users should use an [OAuth access token issued after the user authorizes the application](/oauth).
 
 ## Base URL
 

package/v2/docs/migration-guide.md

@@ -317,10 +317,10 @@ GET /v2/plaid_accounts/123
 GET /v2/tags/1
 ```
 
-**Migration Strategy**: 
+**Migration Strategy**:
 - Maintain a local cache of categories, accounts, and tags
-- Update your code to use IDs and fetch related objects separately when needed
-- Consider batching requests or using the bulk endpoints to reduce API calls
+- Fetch `GET /manual_accounts` and `GET /plaid_accounts` once and build an ID-to-account map. To filter transactions by account name, resolve the name to its account type and ID, then use `manual_account_id` or `plaid_account_id` with `GET /transactions`
+- Refresh cached related objects when their metadata changes instead of fetching them once per transaction
 
 #### Removed Properties
 
@@ -415,14 +415,17 @@ See the [Amounts & balances guide](/amounts-and-balances) for the full sign conv
 #### Split and Grouped Transactions
 
 **Split Transactions**:
-- Parents of split transactions (`is_parent: true`) are not returned by default in `GET /transactions`
+- Parents of split transactions (`is_split_parent: true`) are not returned by default in `GET /transactions`
 - Split transactions include `split_parent_id` pointing to the parent
 - Use `GET /transactions/:id` to get parent with full `children` array
 - Use `GET /transactions` with query param `include_split_parents=true` to include parents in list
 
+> [!WARNING] Prevent duplicate split processing
+> A v1 integration may see split children returned by v2 as new transactions because their parent is omitted by default. Before treating a transaction as new or attempting to split it, check `split_parent_id`. A non-null value identifies an existing split child and points to its parent transaction.
+
 **Grouped Transactions**:
 - Transactions that have been grouped are not returned by default
-- Only the group transaction (`is_group: true`) is returned
+- Only the group transaction (`is_group_parent: true`) is returned
 - Use `GET /transactions/:id` to get details of grouped transactions in the transaction group's `children` array.
 
 

package/v2/docs/version-history.md

@@ -5,17 +5,20 @@ The Lunch Money API spec uses a modified version of SEMVER for its versioning me
 - The minor version represents the number of main endpoints the current version of the spec supports.  For example, a version of the API that supports the /me, /categories, and /transactions endpoints would have a minor version of 3.
 - The revision number represents the number of updates since the last endpoint was added.  For example, each time changes are made to one of the existing three APIs as described above, the revision number will be bumped.
 
-## v2.11.2 - TBD
+## v2.11.3 - TBD
 - Add OAuth 2.0 bearer-token authentication to the v2 API, allowing applications to access Lunch Money on behalf of users who authorize them
 - Document and enforce required OAuth scopes for every v2 operation and publish the scope and scope-group catalog mapped to V2 `operationId` values.
   - Added a new `403` `insufficient_scope` response
 - Document the OAuth 2.0 authorization-code flow used to obtain access tokens
 - Add `include_files` query parameter to `GET /transactions/{id}`
 
-## v2.11.1 - TBD
+## v2.11.2 - Nov 7, 2026
+- Allow `balance_as_of` to be `null` in manual account responses
+
+## v2.11.1 - Sep 28, 2026
 - Add `GET /me/account/settings` and `PUT /me/account/settings` for account-level settings
 - Add `GET /me/user/settings` and `PUT /me/user/settings` for user-level display and formatting preferences
-- Add `GET /me/user/account/settings` and `PUT /me/user/account/settings` for settings specific to a user and budgeting account
+- Add `GET /me/user/account/settings` and `PUT /me/user/account/settings` for settings specific to a user and budget account
 - Add `include_pending_in_totals` to `GET /me/account/settings` and `PUT /me/account/settings`
 - Add `default_manual_account_id` to `GET /me/user/account/settings` and `PUT /me/user/account/settings`
 - Document `GET /budgets/settings` response schema publicly; change `budget_period_quantity` to integer

package/v2/images/oauth-authorization-flow.svg

@@ -1,6 +1,6 @@
 <svg xmlns="http://www.w3.org/2000/svg" width="1120" height="960" viewBox="0 0 1120 960" role="img" aria-labelledby="title desc">
   <title id="title">Lunch Money OAuth authorization-code flow</title>
-  <desc id="desc">A sequence diagram with three actors: your application, the Lunch Money user, and Lunch Money. The application redirects the user's browser to Lunch Money. When necessary, Lunch Money presents its sign-in screen and the user signs in directly with Lunch Money. Lunch Money then presents the budgeting-account selector and requested permissions, the user selects an account and approves access, Lunch Money returns an authorization code, and the application exchanges it for tokens. The application calls GET /v2/me, saves the identified connection, and calls the API for that account.</desc>
+  <desc id="desc">A sequence diagram with three actors: your application, the Lunch Money user, and Lunch Money. The application redirects the user's browser to Lunch Money. When necessary, Lunch Money presents its sign-in screen and the user signs in directly with Lunch Money. Lunch Money then presents the budget-account selector and requested scopes, the user selects an account and approves access, Lunch Money returns an authorization code, and the application exchanges it for tokens. The application calls GET /v2/me, saves the identified connection, and calls the API for that account.</desc>
   <defs>
     <marker id="app-arrow" markerWidth="10" markerHeight="10" refX="8" refY="3" orient="auto"><path d="M0,0 L0,6 L9,3 z" fill="#b45309"/></marker>
     <marker id="user-arrow" markerWidth="10" markerHeight="10" refX="8" refY="3" orient="auto"><path d="M0,0 L0,6 L9,3 z" fill="#9a6700"/></marker>
@@ -23,8 +23,8 @@
   <path class="flow user-flow" d="M560 200 H940"/><rect class="step-bg" x="652" y="178" width="196" height="28" rx="6"/><text class="step" x="750" y="197" text-anchor="middle">2. Request authorization</text>
   <path class="flow lm-flow" d="M950 260 H570"/><rect class="step-bg" x="640" y="238" width="240" height="28" rx="6"/><text class="step" x="760" y="257" text-anchor="middle">3. Show sign-in, when needed</text>
   <path class="flow user-flow" d="M560 320 H940"/><rect class="step-bg" x="605" y="298" width="290" height="28" rx="6"/><text class="step" x="750" y="317" text-anchor="middle">4. Sign in directly with Lunch Money</text>
-  <path class="flow lm-flow" d="M950 380 H570"/><rect class="step-bg" x="545" y="358" width="430" height="28" rx="6"/><text class="step" x="760" y="377" text-anchor="middle">5. Present budgeting-account selector and permissions</text>
-  <path class="flow user-flow" d="M560 440 H940"/><rect class="step-bg" x="585" y="418" width="330" height="28" rx="6"/><text class="step" x="750" y="437" text-anchor="middle">6. Select budgeting account and approve</text>
+  <path class="flow lm-flow" d="M950 380 H570"/><rect class="step-bg" x="545" y="358" width="430" height="28" rx="6"/><text class="step" x="760" y="377" text-anchor="middle">5. Present budget-account selector and scopes</text>
+  <path class="flow user-flow" d="M560 440 H940"/><rect class="step-bg" x="585" y="418" width="330" height="28" rx="6"/><text class="step" x="750" y="437" text-anchor="middle">6. Select budget account and approve</text>
   <path class="flow lm-flow" d="M950 500 H180"/><rect class="step-bg" x="385" y="478" width="360" height="28" rx="6"/><text class="step" x="565" y="497" text-anchor="middle">7. Redirect to callback with authorization code</text>
   <path class="flow app-flow" d="M170 580 H940"/><rect class="step-bg" x="335" y="558" width="460" height="28" rx="6"/><text class="step" x="565" y="577" text-anchor="middle">8. Exchange code with PKCE (+ client secret for confidential client)</text>
   <path class="flow lm-flow" d="M950 640 H180"/><rect class="step-bg" x="385" y="618" width="360" height="28" rx="6"/><text class="step" x="565" y="637" text-anchor="middle">9. Return access token + optional refresh token</text>

package/v2/spec/lunch-money-api-v2.yaml

@@ -4,9 +4,9 @@ info:
   description: >-
     ### Introduction
 
-    Welcome to the Lunch Money v2 API reference. This is the **v2.11.2** spec.
+    Welcome to the Lunch Money v2 API reference. This is the **v2.11.3** spec.
 
-    The API is available at `https://api.lunchmoney.dev/v2`. Use a personal access token from the [Lunch Money Developers page](https://my.lunchmoney.app/developers) for API exploration or work with your own budgeting account. Applications built for other Lunch Money users should use an [OAuth access token issued after the user authorizes the application](https://lunchmoney.dev/oauth).
+    The API is available at `https://api.lunchmoney.dev/v2`. Use a personal access token from the [Lunch Money Developers page](https://my.lunchmoney.app/developers) for API exploration or work with your own budget account. Applications built for other Lunch Money users should use an [OAuth access token issued after the user authorizes the application](https://lunchmoney.dev/oauth).
 
 
     **Try it from these docs**
@@ -43,7 +43,7 @@ info:
   license:
     name: Apache 2.0
     url: http://www.apache.org/licenses/LICENSE-2.0.html
-  version: 2.11.2
+  version: 2.11.3
 
 servers:
   - url: https://api.lunchmoney.dev/v2
@@ -53,7 +53,7 @@ servers:
 
 tags:
   - name: me
-    description: View details and settings for the current user and account.<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.
+    description: View details and settings for the current user and account.<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 budget account.
   - name: categories
     description: Work with categories
     externalDocs:
@@ -145,12 +145,12 @@ components:
         account_id:
           type: integer
           format: int64
-          description: Unique ID for the current budgeting account
+          description: Unique ID for the current budget account
         budget_name:
           type: string
-          description: Name of the current budgeting account.<p> Also available as `display_name` on [/me/account/settings](#tag/me/GET/me/account/settings), which is the preferred endpoint for reading and updating account settings.
+          description: Name of the current budget account.<p> Also available as `display_name` on [/me/account/settings](#tag/me/GET/me/account/settings), which is the preferred endpoint for reading and updating account settings.
         primary_currency:
-          description: Primary currency for the current budgeting account.<p> Also available on [/me/account/settings](#tag/me/GET/me/account/settings), which is the preferred endpoint for reading and updating account settings.
+          description: Primary currency for the current budget account.<p> Also available on [/me/account/settings](#tag/me/GET/me/account/settings), which is the preferred endpoint for reading and updating account settings.
           allOf:
             - $ref: "#/components/schemas/currencyEnum"
         api_key_label:
@@ -400,7 +400,7 @@ components:
         children:
           type: array
           nullable: false
-          description: List of categories to include in the new category group. This field should only be set if `is_group` is also set to true.<br> You may provide existing category objects, existing category IDs, or names for new categories to add to the group. Categories or IDs must already exist and cannot be category groups. Categories that already belong to another group will be moved. If strings are provided, they will be used as names for new categories added to the group. The request will fail if any provided name already exists.<br> You may mix category objects, IDs, and new category names in the same request.
+          description: Categories to include in the new category group. Set only when `is_group` is `true`.<br> You may provide existing category objects, existing category IDs, or names for new categories. IDs and objects must refer to existing categories and cannot refer to category groups. Existing categories are added to the new group; categories that already belong to another group are moved. Each string is used as the name of a new category, and the request fails if that name already exists.<br> You may mix category objects, IDs, and new category names in the same request. Adding or moving an existing category updates it, so OAuth clients that include at least one existing category ID or object in `children` must have both `categories:create` and `categories:update`; without both scopes, the request returns a `403` `insufficient_scope` error. If every child is specified by name, `categories:create` alone is sufficient.
           items:
             oneOf:
               - type: integer
@@ -476,7 +476,7 @@ components:
         children:
           type: array
           nullable: false
-          description: List of existing category objects, existing category IDs, or names of new categories to add to the category group. This attribute should only be set when modifying an existing category group.<br> Categories or IDs must already exist and must not already belong to a category group. Categories that already belong to another category group will be moved. If strings are specified, they will be used as names for new categories added to the group. The request will fail if any provided name matches an existing category name.<br> You may mix full category objects, IDs, and new category names in the same request. OAuth clients that include one or more strings in `children` must have both `categories:update` and `categories:create`; otherwise the request returns a `403` `insufficient_scope` error.
+          description: List of existing category objects, existing category IDs, or names of new categories to add to the category group. This attribute should only be set when modifying an existing category group.<br> Categories or IDs must already exist and cannot refer to category groups. Categories that already belong to another category group will be moved. If strings are specified, they will be used as names for new categories added to the group. The request will fail if any provided name matches an existing category name.<br> You may mix full category objects, IDs, and new category names in the same request. OAuth clients that include one or more strings in `children` must have both `categories:update` and `categories:create`; otherwise the request returns a `403` `insufficient_scope` error.
           x-updatable: true
           items:
             oneOf:
@@ -1029,7 +1029,9 @@ components:
         balance_as_of:
           type: string
           format: date-time
-          description: Date balance was last updated in ISO 8601 extended format, can be in date or date-time format
+          nullable: true
+          description: Date/time the balance was last updated in ISO 8601
+            extended format. `null` when no balance date is available.
         status:
           type: string
           description: The status of the account
@@ -1108,7 +1110,7 @@ components:
         display_name:
           type: string
           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.
+          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 budget account.
           example: Savings
         type:
           description: The type of manual account
@@ -3157,7 +3159,7 @@ components:
       type: object
       title: budget settings object
       additionalProperties: false
-      description: Budget period and display settings for the current budgeting account.
+      description: Budget period and display settings for the current budget account.
       properties:
         budget_period_granularity:
           type: string
@@ -3434,7 +3436,7 @@ components:
       type: object
       title: account settings object
       additionalProperties: false
-      description: Account-level settings for the budgeting account associated with the authorized API token.
+      description: Account-level settings for the budget account associated with the authorized API token.
       properties:
         primary_currency:
           description: Primary currency for the account.
@@ -3448,7 +3450,7 @@ components:
         display_name:
           type: string
           nullable: true
-          description: Display name of the budgeting account in the Lunch Money app.
+          description: Display name of the budget account in the Lunch Money app.
         locale:
           allOf:
             - $ref: "#/components/schemas/localeEnum"
@@ -3496,7 +3498,7 @@ components:
         display_name:
           type: string
           nullable: true
-          description: If set, updates the display name of the budgeting account.
+          description: If set, updates the display name of the budget account.
           x-updatable: true
         locale:
           allOf:
@@ -3521,7 +3523,7 @@ components:
       type: object
       title: user account settings object
       additionalProperties: false
-      description: Settings specific to the authorized user within the current budgeting account.
+      description: Settings specific to the authorized user within the current budget account.
       properties:
         auto_review_transaction_on_update:
           type: boolean
@@ -3534,7 +3536,7 @@ components:
         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.
+          description: Manual account selected by default when the user creates a manual transaction in the current budget account. Must identify a manual account returned by [GET /manual_accounts](#tag/manual_accounts/GET/manual_accounts) for the current budget account. Set to `null` to clear the selection.
       required:
         - auto_review_transaction_on_update
         - auto_review_transaction_on_creation
@@ -3545,7 +3547,7 @@ components:
       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.
+      description: Request body for updating settings specific to the authorized user within the current budget account. Include at least one property to update.
       properties:
         auto_review_transaction_on_update:
           type: boolean
@@ -3558,7 +3560,7 @@ components:
         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.
+          description: If set, updates the manual account selected by default when the user creates a manual transaction in the current budget account. Must identify a manual account returned by [GET /manual_accounts](#tag/manual_accounts/GET/manual_accounts) for the current budget account. Set to `null` to clear the selection.
           x-updatable: true
 
     userSettingsObject:
@@ -4444,7 +4446,7 @@ paths:
         - me
       summary: Get current user
       description: >-
-        Get details about the user associated with the supplied authorization 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.
+        Get details about the user associated with the supplied authorization 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 budget account. Properties such as `primary_currency` and `budget_name` remain on this response for backwards compatibility.
       operationId: getMe
       security:
         - bearerSecurity: []
@@ -4478,7 +4480,7 @@ paths:
         - me
       summary: Get account settings
       description: >-
-        Returns settings for the current budgeting account. These settings apply regardless of which user is accessing the account.
+        Returns settings for the current budget account. These settings apply regardless of which user is accessing the account.
       operationId: getAccountSettings
       security:
         - bearerSecurity: []
@@ -4486,7 +4488,7 @@ paths:
             - me:read
       responses:
         "200":
-          description: Account settings for the current budgeting account
+          description: Account settings for the current budget account
           content:
             application/json:
               schema:
@@ -4513,7 +4515,7 @@ paths:
         - me
       summary: Update account settings
       description: >-
-        Updates account-level settings for the budgeting account 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.
+        Updates account-level settings for the budget account 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
       security:
         - bearerSecurity: []
@@ -4558,7 +4560,7 @@ paths:
         - me
       summary: Get user settings
       description: >-
-        Returns display and formatting preferences for the authorized user. These settings apply across every budgeting account the user owns or collaborates on.
+        Returns display and formatting preferences for the authorized user. These settings apply across every budget account the user owns or collaborates on.
       operationId: getUserSettings
       security:
         - bearerSecurity: []
@@ -4639,7 +4641,7 @@ paths:
         - 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.
+        Returns settings specific to the authorized user within the current budget account. These settings do not affect other users or the authorized user's settings in other budget accounts.
       operationId: getUserAccountSettings
       security:
         - bearerSecurity: []
@@ -4647,7 +4649,7 @@ paths:
             - me:read
       responses:
         "200":
-          description: Settings for the authorized user in the current budgeting account
+          description: Settings for the authorized user in the current budget account
           content:
             application/json:
               schema:
@@ -4667,7 +4669,7 @@ paths:
         - 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.
+        Updates settings specific to the authorized user within the current budget 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
       security:
         - bearerSecurity: []
@@ -5456,12 +5458,15 @@ paths:
       tags:
         - categories
       summary: Create a new category or category group
-      description: Creates a new category with the given name.<br> If the `is_group` attribute is set to true, a category group is created. In this case, the `children` attribute may be set to an array of category IDs to add to the newly created category group.
+      description: Creates a new category with the given name.<br> If `is_group` is `true`, creates a category group; use `children` to add categories to it. OAuth clients that set `children` may also need `categories:update`; see the `children` property for the exact requirement.
       operationId: createCategory
       security:
         - bearerSecurity: []
         - oauth2Security:
             - categories:create
+        - oauth2Security:
+            - categories:create
+            - categories:update
       requestBody:
         required: true
         content:
@@ -5554,6 +5559,8 @@ paths:
                   - errMsg: Cannot specify a 'group_id' in request body if 'is_group' is also true
         "401":
           $ref: "#/components/responses/unauthorizedToken"
+        "403":
+          $ref: "#/components/responses/insufficientScope"
         "429":
           $ref: "#/components/responses/rateLimited"
         "500":
@@ -8785,15 +8792,21 @@ paths:
             minimum: 1
             maximum: 2000
             default: 1000
-          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://lunchmoney.dev/v2/pagination)
+          description: Sets the maximum number of transactions to return.
+            Defaults to `1000`. When more transactions match, `has_more` is
+            `true`. See [Pagination](https://lunchmoney.dev/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://lunchmoney.dev/v2/pagination)
+          description: Sets the number of matching transactions to skip before
+            returning results. Increase this query parameter for each page. See
+            [Pagination](https://lunchmoney.dev/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://lunchmoney.dev/v2/pagination)
+          description: Returns an array of transactions. <br><br>The `has_more`
+            property is set to `true` if more transactions are available. See
+            [Pagination](https://lunchmoney.dev/pagination)
           content:
             application/json:
               schema:
@@ -11867,7 +11880,7 @@ paths:
             - budgets:read
       responses:
         "200":
-          description: Budget period settings for the current budget
+          description: Budget period settings for the current budget account
           content:
             application/json:
               schema: