API settings
Configure OpenAPI and AsyncAPI specs, the interactive API playground, SDK code examples, and authentication settings in your docs.json file.
Use the api field in docs.json to configure what API specifications generate API pages, the interactive API playground for testing endpoints, and how to generate and display code examples.
Settings
api
Type: object
Define all API-related settings under the api key.
api.openapistring or array or objectOpenAPI specification files for generating API reference pages. Accepts a single path or URL, an array of paths and URLs, or an object specifying a source and directory.
Show Hide api.openapi object
sourcestringURL or path to your OpenAPI specification file. Minimum length: 1.
directorystringDirectory to search for OpenAPI files. Do not include a leading slash.
"openapi": "openapi.json"api.asyncapistring or array or objectAsyncAPI specification files for generating event-driven API reference pages. Accepts a single path or URL, an array of paths and URLs, or an object specifying a source and directory.
Show Hide api.asyncapi object
sourcestringURL or path to your AsyncAPI specification file. Minimum length: 1.
directorystringDirectory to search for AsyncAPI files. Do not include a leading slash.
"asyncapi": "asyncapi.json"api.playgroundobjectInteractive API playground settings.
Show Hide api.playground
display"interactive" | "simple" | "none" | "auth"The display mode for the playground. Defaults to interactive.
interactive— Full interactive playground with request buildersimple— Simplified view without the request buildernone— Hide the playground entirelyauth— Show the playground only to authenticated users
proxybooleanWhether to route API requests through a proxy server. Defaults to true.
credentialsbooleanWhether to include cookies and authentication headers for cross-origin requests when proxy is false. Defaults to false. Has no effect when proxy is true.
api.paramsobjectDisplay settings for API parameters.
Show Hide api.params
expanded"all" | "closed"Whether to expand all parameters by default. Defaults to closed.
postarray of stringOpenAPI spec field keys to surface as post pills next to every parameter name in API reference pages and the playground. For each key you list, Mintlify reads the value from the schema and renders it as a pill:
- String values render as the verbatim string.
truerenders the key name as the pill label.false,null, and empty strings render nothing.- Number values render the stringified number.
- Arrays of strings or numbers render one pill per element.
- Objects and other values are skipped.
Use this to expose custom OpenAPI fields—such as x-internal, nullable, or vendor extensions—as visual annotations on each parameter without per-property configuration.
api.url"full"Display mode for the base URL in the endpoint header. Set to full to always show the complete base URL on every endpoint page. By default, the base URL is only shown when there are multiple base URLs to select from.
api.examplesobjectSettings for autogenerated API code examples.
Show Hide api.examples
languagesarray of stringLanguages for autogenerated code snippets. See supported languages for the full list of available languages and aliases.
defaults"required" | "all"Whether to include optional parameters in generated examples. Defaults to all.
prefillbooleanWhether to prefill the playground with example values from your OpenAPI specification. Defaults to false.
autogeneratebooleanWhether to generate code samples for endpoints from your API specification. Defaults to true. When set to false, only manually written code samples (from x-codeSamples in OpenAPI or <RequestExample> components in MDX) appear in the playground.
api.mdxobjectSettings for API pages built from MDX files rather than OpenAPI specs.
Show Hide api.mdx
authobjectAuthentication configuration for MDX-based API requests.
Show Hide auth
method"bearer" | "basic" | "key" | "cobo"Authentication method for API requests.
namestringAuthentication parameter name for API requests.
serverstring or arrayBase URL prepended to relative paths in page-level api frontmatter fields. Not used when the frontmatter contains a full URL.
Example
{
"api": {
"openapi": ["openapi/v1.json", "openapi/v2.json"],
"playground": {
"display": "interactive"
},
"params": {
"expanded": "all",
"post": ["nullable", "x-internal"]
},
"url": "full",
"examples": {
"languages": ["curl", "python", "javascript", "go"],
"defaults": "required",
"prefill": true,
"autogenerate": true
}
}
}