Create manual API pages
Document API endpoints manually with MDX files.
You can manually define API endpoints in individual MDX pages. This approach is useful for small APIs or prototyping.
Setup
In your docs.json file, define your base URL and authentication method.
"api": {
"mdx": {
"server": "https://mintlify.com/api",
"auth": {
"method": "key",
"name": "x-api-key"
}
}
}If you want to hide the API playground, set the display field to none. You don't need to include an authentication method if you hide the playground.
"api": {
"playground": {
"display": "none"
}
}Find a full list of API configurations in Settings.
Create an MDX file for each endpoint. Define the title and api in the frontmatter:
---
title: 'Create new user'
api: 'POST https://api.mintlify.com/user'
---Specify path parameters by wrapping them in {}:
https://api.example.com/v1/endpoint/{userId}If you have a server field configured in docs.json, you can use relative paths like /v1/endpoint.
To override the global playground display mode for a specific page, add playground to the frontmatter:
---
title: 'Create new user'
api: 'POST https://api.mintlify.com/user'
playground: 'none'
---Options:
playground: 'interactive'- Display the interactive playground (default)playground: 'simple'- Display a copyable endpoint with no playgroundplayground: 'none'- Hide the playground entirely
Use parameter and response fields to document your endpoint's parameters and return values.
<ParamField path="userId" type="string" required>
Unique identifier for the user
</ParamField>
<ParamField body="email" type="string" required>
User's email address
</ParamField>
<ResponseField name="id" type="string" required>
Unique identifier for the newly created user
</ResponseField>
<ResponseField name="email" type="string" required>
User's email address
</ResponseField>Add your endpoint pages to the navigation by updating the pages field in your docs.json:
"navigation": {
"tabs": [
{
"tab": "API Reference",
"groups": [
{
"group": "Users",
"pages": [
"api-reference/users/create-user",
"api-reference/users/get-user",
"api-reference/users/update-user"
]
},
{
"group": "Orders",
"pages": [
"api-reference/orders/create-order",
"api-reference/orders/list-orders"
]
}
]
}
]
}Each page path corresponds to an MDX file in your docs repository. For example, api-reference/users/create-user.mdx. Learn more about structuring your docs in Navigation.
Using OpenAPI endpoints in navigation
If you have an OpenAPI specification, you can reference endpoints directly in your navigation without creating individual MDX files. Reference specific endpoints by including the OpenAPI file path and the endpoint:
"navigation": {
"pages": [
"introduction",
"/path/to/users-openapi.json POST /users",
"/path/to/orders-openapi.json GET /orders"
]
}You can also set a default OpenAPI spec for a navigation group and reference endpoints by method and path:
{
"group": "API reference",
"openapi": "/path/to/openapi-v1.json",
"pages": [
"overview",
"authentication",
"GET /users",
"POST /users",
{
"group": "Orders",
"openapi": "/path/to/openapi-v2.json",
"pages": [
"GET /orders",
"POST /orders"
]
}
]
}For more details on OpenAPI integration, see OpenAPI setup.
Enable authentication
You can set authentication globally in docs.json or override it on individual pages using the authMethod field in frontmatter. A page-specific method overrides the global setting.
Bearer token
"api": {
"mdx": {
"auth": {
"method": "bearer"
}
}
}---
title: "Your page title"
authMethod: "bearer"
---Basic authentication
"api": {
"mdx": {
"auth": {
"method": "basic"
}
}
}---
title: "Your page title"
authMethod: "basic"
---API key
"api": {
"mdx": {
"auth": {
"method": "key",
"name": "x-api-key"
}
}
}---
title: "Your page title"
authMethod: "key"
---None
To disable authentication on a specific page, set authMethod to none:
---
title: "Your page title"
authMethod: "none"
---