Add "x-hidden" docs

api-playground/openapi/advanced-features.mdx

@@ -7,7 +7,7 @@
 
 ## `oneOf`, `anyOf`, `allOf`
 
 For complex datatypes, OpenAPI provides the `oneOf`, `anyOf`, and `allOf` keywords, allowing you to combine schemas in certain ways. You can read more about these keywords in the [Swagger documentation](https://swagger.io/docs/specification/data-models/oneof-anyof-allof-not/), but essentially:
 
 - `oneOf` functions like an "exclusive-or" operator
 - `anyOf` functions like an "or" operator
@@ -54,7 +54,7 @@
 
 ### Providing options with `oneOf` and `anyOf`
 
 When you use `oneOf` or `anyOf`, Mintlify displays the options in a tabbed container. To give your options helpful names, make sure to give each subschema a `title` field. For example, here's how you might display two different types of delivery addresses:
 
 ```yaml
 delivery_address:
@@ -135,3 +135,43 @@
             const planter = require('planter');
             planter.list({ potted: true });
 ```
+
+## `x-hidden`
+
+If your pages are [autogenerated](/openapi/setup) from an OpenAPI document, but there are some paths that you don't want to create pages for, you can hide them by adding the property `x-hidden`.
+
+You can add the `x-hidden` tag under endpoint or webhook paths below the method.
+
+Here's are examples of how that would look in an OpenAPI schema document for an endpoint or a webhook path:
+
+```json {14}
+"paths": {
+  "/plants": {
+    "get": {
+      "description": "Returns all plants from the store",
+      "parameters": { ... },
+      "responses": { ... },
+    }
+  }
+  "/secret_plants": {
+    "get": {
+      "description": "Returns all secret plants from the store (do not publish this endpoint!)",
+      "parameters": { ... },
+      "responses": { ... },
+      "x-hidden": true
+    }
+  }
+},
+```
+
+```json {5}
+"webhooks": {
+  "/secret_pants_hook": {
+    "post": {
+      "description": "Secret webhook for information about a new plant added to the store",
+      "x-hidden": true
+    }
+  }
+}
+```
+

api-playground/openapi/setup.mdx

@@ -61,6 +61,8 @@
 
 There are some scenarios in which the default behavior isn't sufficient. If you need more customizability, you can create an MDX page for your OpenAPI operation, and modify it just like any other MDX page.
 
+<Tip>If you have some endpoints in your OpenAPI schema that you don't want pages generated for automatically, you can add the [x-hidden](/optnapi/advanced-features#x-hidden) property</Tip>
+
 ## Create MDX files for API pages
 
 If you want to customize the page metadata, add additional content, omit certain OpenAPI operations, or reorder OpenAPI pages in your navigation, you'll need an MDX page for each operation. Here is [an example MDX OpenAPI page](https://github.com/mindsdb/mindsdb/blob/main/docs/rest/databases/create-databases.mdx) from [MindsDB](https://docs.mindsdb.com/rest/databases/create-databases).&#x20;
@@ -106,12 +108,12 @@
   and the correct method will be generated.
 </Note>
 
 ### Autogenerate files
 
 For large OpenAPI documents, creating one MDX page for each OpenAPI operation can be a lot of work. To make it easier, we created a local OpenAPI page scraper.
 
 Our Mintlify [scraper](https://www.npmjs.com/package/@mintlify/scraping)
 autogenerates MDX files for your OpenAPI endpoints.
 
 Each generated page will correspond to an OpenAPI operation under the "paths" section of the OpenAPI schema.
 If your OpenAPI document is version 3.1+, the scraper will also generate pages for webhooks under the "webhooks" section of the OpenAPI schema.
@@ -136,7 +138,7 @@
 reorder and add the files to your navigation manually.
 
 <Note>
   If your OpenAPI document is invalid, the files will not autogenerate.
 </Note>