We’re here to help you get the most out of Mintlify
GitHub app issues
Uninstall the Mintlify app through GitHub
Reinstall the Mintlify app
API page issues
All of my OpenAPI pages are completely blank
mint dev
locally should reveal some of these issues.To verify your OpenAPI document will pass validation:mint openapi-check <openapiFilenameOrUrl>
in your CLI.One of my OpenAPI pages is completely blank
openapi
field in the page metadata. Make sure that the HTTP method and path match the HTTP method and path in the OpenAPI document exactly.Here’s an example of how things might go wrong:openapi
field has a trailing slash, whereas the path in the OpenAPI
document does not.Another common issue is a misspelled filename. If you are specifying a particular OpenAPI document
in the openapi
field, ensure the filename is correct. For example, if you have two OpenAPI
documents openapi/v1.json
and openapi/v2.json
, your metadata might look like this:Requests from the API Playground don't work
POST
request to the
/api/request
path on the docs site. If your reverse proxy is configured to only allow GET
requests, then all of these requests will fail. To fix this, configure your reverse proxy to
allow POST
requests to the /api/request
path.Alternatively, if your reverse proxy prevents you from accepting POST
requests, you can configure Mintlify to send requests directly to your backend with the api.playground.proxy
setting in the docs.json
. See the configurations for the API playground for more information. This will
likely require you to configure CORS on your server, as these requests will now come directly
from your users’ browsers.Docs page won't load (error 404)
/api
in the URL. This is a reserved folder in production environments, which produces a 404 error.Issues adding SVG to a card
<svg/>
tag.<svg/>
tag.Bypassing the Onboarding Flow for GitLab
Skip the first onboarding step
Enter placeholder repository information
mintlify
starter
Complete the onboarding
Navigate to GitLab settings