Linking Mintlify as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
Sync your Mintlify documentation analytics into the PostHog data warehouse, including AI assistant conversations, user feedback, search queries, page views, and visitor metrics. Join docs engagement data with product analytics to understand how documentation drives adoption and activation.
Prerequisites
- An admin API key from Mintlify (starts with
mint_). Create one in Settings → Organization → API keys. - Your project ID, available on the same API keys page.
- A Mintlify Pro or Enterprise plan. Analytics endpoints are only available on paid plans.
Adding a data source
- Go to the sources tab of the data pipeline section in PostHog.
- Click + New source and then click Link next to Mintlify.
- In Mintlify, go to Settings → Organization → API keys and create an admin API key (starts with
mint_). Copy the key and your project ID from the same page. - Back in PostHog, enter the admin API key and project ID, then click Next.
- Select the tables you want to sync, set the sync method and frequency, then click Import.
Available tables
| Table | Description | Sync method |
|---|---|---|
assistant_conversations | Individual user turns with assistant responses, referenced pages, and resolution status | Incremental |
feedback | User feedback from page ratings, code snippets, and agents, including review status | Full refresh |
searches | Search terms with aggregate counts and click statistics | Full refresh |
views | Content view counts for each documentation path, split by human and AI traffic | Full refresh |
visitors | Approximate distinct visitors for each documentation path, split by human and AI traffic | Full refresh |
Incremental tables sync only new or updated records on each run using the timestamp field as a cursor. Full refresh tables reload all data on each sync.
The feedback table uses full refresh because its status can change without a modification timestamp. The searches, views, and visitors tables use full refresh because they contain aggregates rather than individual events.
Rate limiting
Mintlify's analytics endpoints share a limit of 100 requests per organization per hour. The source uses maximum page sizes to minimize API calls. If you have a large documentation site with extensive analytics history, syncs may be throttled.
Configuration
| Option | Type | Required |
|---|---|---|
Admin API key | password | Yes |
Project ID | text | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
assistant_conversations | Individual user turns with assistant responses, referenced pages, and resolution status. | Incremental, Full refresh | timestamp | — |
feedback | User feedback from page ratings, code snippets, and agents, including its current review status. | Full refresh | — | — |
searches | Search terms with aggregate counts and click statistics, ordered by search count in descending order. | Full refresh | — | — |
views | Content view counts for each documentation path, split by human and AI traffic. | Full refresh | — | — |
visitors | Approximate distinct visitors for each documentation path, split by human and AI traffic. | Full refresh | — | — |
Troubleshooting
If a sync fails with an authentication error, check that you're using an admin API key (starts with mint_), not a regular API key, and that it hasn't been regenerated. Create a new admin API key in Mintlify settings and reconnect the source.
If Mintlify returns an access denied error, verify your account has a Pro or Enterprise plan. Analytics endpoints are not available on the free plan.
If you see a project not found error, verify the project ID matches exactly what's shown on the Mintlify API keys page.
For more details on the Mintlify API, see the official API documentation.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.