Skip to main content
The REST API requires a Pro or Enterprise plan.
The Mintlify REST (Representational State Transfer) API enables you to programmatically interact with your documentation, trigger updates, embed AI-powered chat experiences, and export analytics data.

Endpoints

Common use cases

Authentication

Generate API keys on the API keys page in your dashboard. Each API key belongs to an organization—you can use keys across multiple deployments within the same organization. You can create up to 10 API keys per hour per organization. Mintlify uses two types of API keys, each scoped to a different set of endpoints:

Admin API key

Use the admin API key for deployment, triggering the agent, and analytics endpoints. Admin API keys begin with the mint_ prefix. The admin API key is a server-side secret. Do not expose it in client-side code.

Assistant API key

Do not directly embed the assistant API key in client-side code. Any visitor who extracts the key can call the assistant message endpoint on your behalf, consuming credits and potentially triggering overage charges.For production deployments, proxy requests that use an assistant API key through your own backend and store the key as a server-side environment variable. Routing requests through a proxy also lets you add rate limiting, authentication, and bot protection to prevent abuse.
Use the assistant API key to authenticate requests to the assistant, search, and page content endpoints. Assistant API keys begin with the mint_dsc_ prefix.
Search documentation and page content requests do not consume credits. Assistant message requests use credits and can incur overages.