Update from code changes: document x-mint playground expand setting

api-playground/openapi-setup.mdx

@@ -1,11 +1,21 @@
 ---
 title: "OpenAPI setup"
 description: "Generate interactive API documentation from OpenAPI specification files with automatic endpoint pages, request builders, and navigation."
-keywords: ["OpenAPI", "API specification", "Swagger"]
+keywords:
+  - "OpenAPI"
+  - "API specification"
+  - "Swagger"
 ---
 
 OpenAPI is a specification for describing APIs. Mintlify supports OpenAPI 3.0 and 3.1 documents to generate interactive API documentation and keep it up to date.
 
+![Favicon](/favicon.ico "Favicon")
+
+|  |  |  |
+| --- | --- | --- |
+|  |  |  |
+|  |  |  |
+
 ## Add an OpenAPI specification file
 
 To document your endpoints with OpenAPI, you need one or more valid OpenAPI specifications in either JSON or YAML format that follow the [OpenAPI specification 3.0 or 3.1](https://swagger.io/specification/).
@@ -15,30 +25,32 @@
 Reference any number of OpenAPI specifications in the navigation element of your `docs.json` to create pages for your API endpoints. Each specification file generates its own set of endpoints.
 
 <CodeGroup>
-  ```json Single specification
-  "navigation": {
-    "tabs": [
-      {
-        "tab": "API Reference",
-        "openapi": "openapi.json"
-      }
-    ]
-  }
-  ```
 
-  ```json Multiple specifications
-  "navigation": {
-    "tabs": [
-      {
-        "tab": "API Reference",
-        "openapi": [
-          "openapi/v1.json",
-          "openapi/v2.json"
-        ]
-      }
-    ]
-  }
-  ```
+```json Single specification
+"navigation": {
+  "tabs": [
+    {
+      "tab": "API Reference",
+      "openapi": "openapi.json"
+    }
+  ]
+}
+```
+
+```json Multiple specifications
+"navigation": {
+  "tabs": [
+    {
+      "tab": "API Reference",
+      "openapi": [
+        "openapi/v1.json",
+        "openapi/v2.json"
+      ]
+    }
+  ]
+}
+```
+
 </CodeGroup>
 
 <Note>
@@ -120,37 +132,35 @@
 
 <Steps>
   <Step title="Define your authentication method.">
-  Add a `securitySchemes` field to define how users authenticate.
+    Add a `securitySchemes` field to define how users authenticate.
 
-  This example shows a configuration for bearer authentication.
+    This example shows a configuration for bearer authentication.
 
-  ```json
-  {
-    "components": {
-      "securitySchemes": {
-        "bearerAuth": {
-          "type": "http",
-          "scheme": "bearer"
+    ```json
+    {
+      "components": {
+        "securitySchemes": {
+          "bearerAuth": {
+            "type": "http",
+            "scheme": "bearer"
+          }
         }
       }
     }
-  }
-  ```
-
+    ```
   </Step>
   <Step title="Apply authentication to your endpoints.">
-  Add a `security` field to require authentication.
+    Add a `security` field to require authentication.
 
-```json
-{
-  "security": [
+    ```json
     {
-      "bearerAuth": []
+      "security": [
+        {
+          "bearerAuth": []
+        }
+      ]
     }
-  ]
-}
-```
-
+    ```
   </Step>
 </Steps>
 
@@ -168,7 +178,7 @@
 
 Use the `x-default` extension on a security scheme to pre-fill the authentication field in the API playground. This is useful for providing placeholder values or test credentials that help users get started quickly.
 
-```json {6}
+```json highlight={6}
 {
   "components": {
     "securitySchemes": {
@@ -183,7 +193,7 @@
 }
 ```
 
 The `x-default` extension supports `apiKey` and `http` bearer security scheme types. The value appears as the default input in the playground's authentication fields. Prefill for security schemes is unconditional and does not require any additional configuration.
 
 Use `x-default` on other schema properties in your OpenAPI specification to set a default value in the API playground without affecting the `default` field in the schema definition. Unlike security schemes, prefill for non-security-scheme properties only takes effect when you set [`api.examples.prefill`](/organize/settings-api) to `true` in your [`docs.json`](/api-playground/overview#example-configuration).
 
@@ -200,7 +210,7 @@
 When enabled, clicking the option downloads your OpenAPI spec directly. Deployments with multiple specs receive them bundled as `api-specs.zip`. On deployments behind `auth` or `userAuth`, only authenticated readers can download the spec.
 
 <Warning>
   The downloaded OpenAPI spec is unfiltered and does not respect [authentication groups](/deploy/authentication-setup). Any authenticated reader who can open the contextual menu receives the full spec, including endpoints and schemas that would otherwise be hidden from their group. Do not enable `download-spec` on an authenticated site if your OpenAPI spec contains endpoints or fields you consider sensitive.
 </Warning>
 
 ## Customize your endpoint pages
@@ -211,7 +221,7 @@
 
 Override the default metadata for generated API pages by adding `x-mint: metadata` to any operation. You can use any metadata field that would be valid in MDX frontmatter except for `openapi`.
 
-```json {7-14}
+```json highlight={7-14}
 {
   "paths": {
     "/users": {
@@ -239,7 +249,7 @@
 
 You can also control playground display per endpoint using the `playground` and `groups` metadata fields:
 
-```json {7-11}
+```json highlight={7-11}
 {
   "paths": {
     "/admin/users": {
@@ -264,7 +274,7 @@
 
 Add content before the auto-generated API documentation using `x-mint: content`. The `x-mint: content` extension supports all Mintlify MDX components and formatting.
 
-```json {6-8}
+```json highlight={6-8}
 {
   "paths": {
     "/users": {
@@ -317,7 +327,7 @@
 
 Both fields accept an array of strings. Each string becomes its own pill.
 
-```json {7-10}
+```json highlight={7-10}
 {
   "components": {
     "schemas": {
@@ -351,13 +361,36 @@
 
 With this configuration, a property like `{ "type": "string", "nullable": true, "x-internal": "admin" }` renders `nullable` and `admin` pills next to its name. Post pills appear in this order: built-in pills (`read-only`, `write-only`), then `api.params.post` config-driven pills, then per-property `x-mint.post` pills.
 
+### Collapse nested playground fields
+
+Start nested object fields collapsed in the API playground by adding `x-mint: playground` with `expand: false` to an operation. This keeps the playground compact for endpoints with large or deeply nested request bodies.
+
+```json highlight={6-10}
+{
+  "paths": {
+    "/users": {
+      "post": {
+        "summary": "Create user",
+        "x-mint": {
+          "playground": {
+            "expand": false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+The top-level request sections, such as Authorization, Path, Query, and Body, always stay expanded. The setting only collapses object fields nested within those sections. Users can expand any collapsed field manually. When `expand` is omitted, all fields start expanded.
+
 ### Group display names
 
 Set a custom display name for a tag's navigation group using the `x-group` extension on a tag object. By default, Mintlify uses the tag `name` as both the navigation group label and the URL path segment. The `x-group` extension overrides the group label while keeping the tag name for the URL.
 
 This is useful when you want a human-readable group name that differs from the tag used in your API paths.
 
-```json {4-9}
+```json highlight={4-9}
 {
   "tags": [
     {
@@ -409,7 +442,7 @@
 
 Generate dedicated API sections by adding an `openapi` field to a navigation element and no other pages. All endpoints in the specification appear in the generated section.
 
-```json {5}
+```json highlight={5}
 "navigation": {
   "tabs": [
     {
@@ -515,7 +548,7 @@
 
 Reference specific endpoints without setting a default OpenAPI specification by including the file path. You can reference endpoints from multiple OpenAPI specifications in the same documentation section.
 
-```json {5-6}
+```json highlight={5-6}
 "navigation": {
   "pages": [
     "introduction",

es/api-playground/openapi-setup.mdx

@@ -378,6 +378,31 @@ Para mostrar campos arbitrarios de la especificación OpenAPI como píldoras en
 
 Con esta configuración, una propiedad como `{ "type": "string", "nullable": true, "x-internal": "admin" }` renderiza las píldoras `nullable` y `admin` junto a su nombre. Las píldoras post aparecen en este orden: píldoras integradas (`read-only`, `write-only`), luego las píldoras impulsadas por la configuración `api.params.post` y, por último, las píldoras `x-mint.post` por propiedad.
 
+<div id="collapse-nested-playground-fields">
+  ### Contraer campos anidados del playground
+</div>
+
+Inicia los campos de objetos anidados contraídos en el playground de API agregando `x-mint: playground` con `expand: false` a una operación. Esto mantiene el playground compacto para endpoints con cuerpos de solicitud grandes o muy anidados.
+
+```json {6-10}
+{
+  "paths": {
+    "/users": {
+      "post": {
+        "summary": "Create user",
+        "x-mint": {
+          "playground": {
+            "expand": false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+Las secciones de solicitud de nivel superior, como Authorization, Path, Query y Body, siempre permanecen expandidas. La configuración solo contrae los campos de objetos anidados dentro de esas secciones. Los usuarios pueden expandir manualmente cualquier campo contraído. Cuando se omite `expand`, todos los campos inician expandidos.
+
 <div id="group-display-names">
   ### Nombres de visualización de grupo
 </div>

fr/api-playground/openapi-setup.mdx

@@ -378,6 +378,31 @@ Pour faire apparaître des champs arbitraires de la spécification OpenAPI sous
 
 Avec cette configuration, une propriété telle que `{ "type": "string", "nullable": true, "x-internal": "admin" }` affiche les pastilles `nullable` et `admin` à côté de son nom. Les pastilles post apparaissent dans cet ordre : pastilles intégrées (`read-only`, `write-only`), puis pastilles définies par la configuration `api.params.post`, puis pastilles `x-mint.post` propres à la propriété.
 
+<div id="collapse-nested-playground-fields">
+  ### Réduire les champs imbriqués du playground
+</div>
+
+Affichez les champs d'objets imbriqués réduits par défaut dans le playground d'API en ajoutant `x-mint: playground` avec `expand: false` à une opération. Cela garde le playground compact pour les endpoints avec des corps de requête volumineux ou profondément imbriqués.
+
+```json {6-10}
+{
+  "paths": {
+    "/users": {
+      "post": {
+        "summary": "Create user",
+        "x-mint": {
+          "playground": {
+            "expand": false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+Les sections de requête de premier niveau, comme Authorization, Path, Query et Body, restent toujours développées. Le paramètre réduit uniquement les champs d'objets imbriqués dans ces sections. Les utilisateurs peuvent développer manuellement tout champ réduit. Lorsque `expand` est omis, tous les champs sont développés par défaut.
+
 <div id="group-display-names">
   ### Noms d'affichage des groupes
 </div>

zh/api-playground/openapi-setup.mdx

@@ -378,6 +378,31 @@ API playground 会使用这些服务器 URL 来确定请求的发送目标。如
 
 通过此配置，类似 `{ "type": "string", "nullable": true, "x-internal": "admin" }` 的属性会在其名称旁渲染 `nullable` 和 `admin` 标签。post 标签按以下顺序显示：内置标签（`read-only`、`write-only`）、由 `api.params.post` 配置驱动的标签，然后是逐属性配置的 `x-mint.post` 标签。
 
+<div id="collapse-nested-playground-fields">
+  ### 折叠 playground 中的嵌套字段
+</div>
+
+在操作上添加 `x-mint: playground` 并设置 `expand: false`，使 API playground 中的嵌套对象字段默认折叠。这可以让请求体较大或嵌套较深的端点在 playground 中保持简洁。
+
+```json {6-10}
+{
+  "paths": {
+    "/users": {
+      "post": {
+        "summary": "Create user",
+        "x-mint": {
+          "playground": {
+            "expand": false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+顶层请求区块（如 Authorization、Path、Query 和 Body）始终保持展开。该设置仅折叠这些区块内嵌套的对象字段。用户可以手动展开任何已折叠的字段。省略 `expand` 时，所有字段默认展开。
+
 <div id="group-display-names">
   ### 分组显示名称
 </div>