Linking OpenRouter as a source

Alpha release

This source is currently in alpha. The interface and available tables may change.

The OpenRouter connector syncs your LLM gateway data – usage rollups, API keys, credits, organization members, workspaces, and the models and providers catalogs – into the PostHog Data warehouse, so you can analyze your LLM spend and usage alongside your product data.

Prerequisites

You need an OpenRouter account with permission to create an API key.

A management API key is required to sync the activity, api_keys, credits, organization_members, and workspaces tables.
A regular inference key can only sync the public models and providers catalogs.

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 OpenRouter, you'll need:

API key – create a management API key in your OpenRouter settings under Settings → Management Keys. A management key unlocks all tables; an inference key can only access the public catalogs.

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_at timestamp). 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 activity table syncs incrementally by date, fetching daily usage rollups. OpenRouter retains only the last 30 completed UTC days, so both first and incremental syncs are limited to that window.

All other tables (models, providers, api_keys, credits, organization_members, workspaces) sync as full refresh because the OpenRouter API doesn't support time-based filtering for these endpoints.

Configuration

Option	Type	Required
`API key`	password	Yes

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`models`	Catalog of every model available through the OpenRouter gateway, including pricing, context length, architecture, and supported parameters.	Full refresh	—	—
`providers`	Catalog of inference providers that serve models through OpenRouter.	Full refresh	—	—
`activity`	Daily usage rollups; only the last 30 completed UTC days are available	Incremental, Full refresh	date	—
`api_keys`	API keys belonging to the account or organization, with per-key usage and spending limits.	Full refresh	—	—
`credits`	Current credit balance for the account: total credits purchased and total credits used.	Full refresh	—	—
`organization_members`	Members of the OpenRouter organization and their roles.	Full refresh	—	—
`workspaces`	Workspaces within the organization, including their default models and observability settings.	Full refresh	—	—

Troubleshooting

If you see an authentication error, your API key is invalid or has been revoked. Create a new key in your OpenRouter settings, then reconnect.
If you see a permissions error for activity, api_keys, credits, organization_members, or workspaces tables, your key is missing the management scope. Create a management API key under Settings → Management Keys, then reconnect.

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.