Getting Started
Core Configuration
Components
API Pages
- Playground
- OpenAPI Setup
- Customization
- AsyncAPI
- MDX
- Troubleshooting
Authentication and Personalization
- Authentication
- Partial Authentication
- Personalization
- Auth vs Personalization
- Authentication Setup
- Personalization Setup
- Sending Data
Guides
- Migrations
- Model Context Protocol
- Translations
- Monorepo setup
- React
- Custom Scripts
- SEO
- Hidden pages
- Redirects and Broken Links
- Custom Subdirectory
- Dashboard Access
Integrations
- Analytics
- SDKs
- Support
- Privacy
Version Control and CI/CD
Support
We’re here to help you get the most out of Mintlify
Dashboard widget
Send us a message from your dashboard. Select Support in your dashboard’s sidebar.
Email Us
If you can’t access your dashboard, email us at support@mintlify.com.
Ask AI
Join our community and ask our AI assistant that’s been trained on our documentation.
YouTube
Watch tutorials and guides on our YouTube channel.
Frequently Asked Questions
The GitHub app can be temperamental and resetting the connection is a great way to solve issues.
Uninstall the Mintlify app through GitHub
- In GitHub, go to installations and select Configure next to the Mintlify app. Scroll down and select Uninstall.
- Go to Authorized GitHub Apps and select Revoke next to the Mintlify app.
Reinstall the Mintlify app
- In your Mintlify dashboard, go to Git Settings and install the GitHub app.
- Authorize your account in the My Profile section of your dashboard.
API pages are complicated. As a result, there are a lot of things that can go wrong. Here’s a list of common issues we’ve seen customers run into:
In this scenario, it’s likely that either Mintlify cannot find your OpenAPI document or your OpenAPI document is invalid.
Running mint dev
locally should reveal some of these issues.
To verify your OpenAPI document will pass validation:
- Run
mint openapi-check <openapiFilenameOrUrl>
in your CLI. - Validate your OpenAPI spec with Swagger Editor.
Additionally, Mintlify does not support OpenAPI 2.0. If your document uses OpenAPI 2.0, you may encounter this issue. You can convert your document with Swagger Editor.
This is usually caused by a misspelled 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: "GET /users/{id}/"
---
paths:
"/users/{id}":
get: ...
Notice that the path in the 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:
---
openapi: "v1 GET /users/{id}"
---
If you have a custom domain configured, this could be an issue with your reverse proxy. By
default, requests made via the API Playground start with a 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.
Check to see if you have /api
in the URL. This is a reserved folder in production environments, which produces a 404 error.
We support a specific type of SVG, called JSX, and as such the image will need to be converted.
- Use the SVGR converter to generate JSX compatible SVG code.
- Copy the code inside the
<svg/>
tag.
- Paste the code into your card. Make sure you only copy and paste the code inside the
<svg/>
tag. - You may need to decrease the height and width to make the image fit.
Since account creation is currently limited to GitHub, you’ll need to use a workaround to connect your GitLab repository. Follow these steps to bypass the standard GitHub-only onboarding flow:
Skip the first onboarding step
When you first create your Mintlify account, you’ll see an onboarding flow that asks you to connect a GitHub repository. Skip this initial step.
Enter placeholder repository information
In the second step of the onboarding process, enter the following placeholder information:
- Organization:
mintlify
- Repository:
starter
This will allow you to proceed through the onboarding without connecting an actual GitHub repository.
Complete the onboarding
Click through the remaining onboarding steps to reach your Mintlify dashboard.
Navigate to GitLab settings
Once you’re in the dashboard, navigate to the GitLab settings page and connect your actual GitLab repository using the project ID and access token from the previous section.
We do our best to respond to all requests within 24 hours but delays may occur during busy times.
Was this page helpful?