From fa2865df89db001e8513d3a9047e60156630159b Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Wed, 25 Feb 2026 01:59:48 +0000 Subject: [PATCH 1/4] Add tip about downloading OpenAPI specs Generated-By: mintlify-agent --- create/files.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/create/files.mdx b/create/files.mdx index 25d6e7999..af7fce54d 100644 --- a/create/files.mdx +++ b/create/files.mdx @@ -8,6 +8,10 @@ Mintlify automatically serves static assets from your documentation repository a You can make any supported file type available to your users, including OpenAPI specifications, images, videos, and more. + + OpenAPI specification files in your repository are automatically accessible at their file path. For example, if you have `openapi.json` at the root of your repo, users can download your API spec at `https://docs.your-project.com/openapi.json`. + + Files must be less than 20 MB for images and 100 MB for other file types. From 7b164d6647b69cb7bd6c3c94876fb1dc2badcaa9 Mon Sep 17 00:00:00 2001 From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Date: Tue, 24 Feb 2026 18:05:26 -0800 Subject: [PATCH 2/4] Move OpenAPI download tip to openapi-setup.mdx --- api-playground/openapi-setup.mdx | 4 ++++ create/files.mdx | 4 ---- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/api-playground/openapi-setup.mdx b/api-playground/openapi-setup.mdx index 37edd2e83..2962fa5ea 100644 --- a/api-playground/openapi-setup.mdx +++ b/api-playground/openapi-setup.mdx @@ -14,6 +14,10 @@ Add OpenAPI specifications to your documentation repository or host them online 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. + + OpenAPI specification files stored in your documentation repository are automatically served at their file path. For example, `openapi.json` at the root of your repo is available for download at `https://docs.your-project.com/openapi.json`. + + ```json Single specification "navigation": { diff --git a/create/files.mdx b/create/files.mdx index af7fce54d..25d6e7999 100644 --- a/create/files.mdx +++ b/create/files.mdx @@ -8,10 +8,6 @@ Mintlify automatically serves static assets from your documentation repository a You can make any supported file type available to your users, including OpenAPI specifications, images, videos, and more. - - OpenAPI specification files in your repository are automatically accessible at their file path. For example, if you have `openapi.json` at the root of your repo, users can download your API spec at `https://docs.your-project.com/openapi.json`. - - Files must be less than 20 MB for images and 100 MB for other file types. From e906e4bba8436a681946fcd2cd483918aa8d2e2d Mon Sep 17 00:00:00 2001 From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Date: Tue, 24 Feb 2026 18:09:36 -0800 Subject: [PATCH 3/4] Replace tip callout with prose --- api-playground/openapi-setup.mdx | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/api-playground/openapi-setup.mdx b/api-playground/openapi-setup.mdx index 2962fa5ea..c9b43f74f 100644 --- a/api-playground/openapi-setup.mdx +++ b/api-playground/openapi-setup.mdx @@ -10,14 +10,10 @@ OpenAPI is a specification for describing APIs. Mintlify supports OpenAPI 3.0 an 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/). -Add OpenAPI specifications to your documentation repository or host them online where you can access the specifications by URL. +Add OpenAPI specifications to your documentation repository or host them online where you can access the specifications by URL. Specifications stored in your repository are [served as downloadable files](/create/files) at their file path on your docs domain. For example, `https://your-domain/docs/openapi.json`. 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. - - OpenAPI specification files stored in your documentation repository are automatically served at their file path. For example, `openapi.json` at the root of your repo is available for download at `https://docs.your-project.com/openapi.json`. - - ```json Single specification "navigation": { From 33196e4951b655223e01b996fbf54921ce868c79 Mon Sep 17 00:00:00 2001 From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Date: Tue, 24 Feb 2026 18:12:27 -0800 Subject: [PATCH 4/4] Apply suggestion from @ethanpalm --- api-playground/openapi-setup.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/api-playground/openapi-setup.mdx b/api-playground/openapi-setup.mdx index c9b43f74f..91cd2cce9 100644 --- a/api-playground/openapi-setup.mdx +++ b/api-playground/openapi-setup.mdx @@ -10,7 +10,7 @@ OpenAPI is a specification for describing APIs. Mintlify supports OpenAPI 3.0 an 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/). -Add OpenAPI specifications to your documentation repository or host them online where you can access the specifications by URL. Specifications stored in your repository are [served as downloadable files](/create/files) at their file path on your docs domain. For example, `https://your-domain/docs/openapi.json`. +Add OpenAPI specifications to your documentation repository or host them online where you can access the specifications by URL. Specifications stored in your repository are [served as downloadable files](/create/files) at their path on your docs domain. For example, `https://your-domain/docs/openapi.json`. 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.