Linking Apitally 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.
Contents
This source is currently in alpha. The interface and available tables may change.
The Apitally connector syncs your API monitoring and analytics data — apps, consumers, endpoints, traffic metrics, and request logs — into the PostHog Data warehouse, so you can analyze API performance alongside your product data.
Prerequisites
You need an Apitally account on the Premium plan, which includes API access. If you're on a lower tier, you'll need to upgrade before connecting.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
When linking Apitally, you'll need:
- API key – create a team-scoped API key in your Apitally team settings under API keys.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
The Traffic table supports incremental syncs on the period_end field, and RequestLogs supports incremental syncs on the timestamp field. All other tables (Apps, Consumers, Endpoints) are full refresh only, as the Apitally API doesn't expose a server-side timestamp filter for them.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Apps | Apps and their environments configured in your Apitally team. | Full refresh | — | — |
Consumers | API consumers (identified callers) that have made requests to an app. | Full refresh | — | — |
Endpoints | API endpoints (method + path) detected for an app. | Full refresh | — | — |
Traffic | Hourly API traffic metrics for an app: request counts and payload sizes over time. | Incremental, Full refresh | period_end | — |
RequestLogs | Individual API request log entries for an app, including status code, timing, and consumer. | Incremental, Full refresh | timestamp | — |
Troubleshooting
- If you see a 401 authentication error, your API key is invalid or has been revoked. Generate a new key in your Apitally team settings under API keys, then reconnect.
- If you see a 403 access denied error, your Apitally plan doesn't include API access. Upgrade to the Premium plan to enable it.
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.