> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking OpenRouter as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/openrouter

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

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.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The OpenRouter connector syncs your LLM gateway data – usage rollups, API keys, credits, organization members, workspaces, end users, batches, 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, workspaces, and end\_users tables.
-   A **regular inference key** is required to sync the batches table. Management keys cannot access batch data.
-   A regular inference key can also sync the public models and providers catalogs.

> To sync all tables, connect two separate OpenRouter sources: one with a management key and one with a regular inference key.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  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](https://openrouter.ai/settings/keys) under **Settings → Management Keys**. A management key unlocks most tables (activity, api\_keys, credits, organization\_members, workspaces, end\_users). To sync the batches table, connect a second source with a regular inference key.

## 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](https://posthog.com/docs/data-pipelines/sources.md#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`, `end_users`, `batches`) sync as full refresh because the OpenRouter API doesn't support time-based filtering for these endpoints.

The `batches` table is off by default and requires a regular API key (not a management key). A batch's status, request counts, and usage keep changing after creation, so only full refresh is supported.

## 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 | — | — |
| `end_users` | End-user tracking IDs registered under the OpenRouter organization, including deactivated registrations. | Full refresh | — | — |
| `batches` | Batch jobs in the API key's workspace; needs a regular API key, not a management key | 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](https://openrouter.ai/settings/keys), then reconnect.
-   If you see a permissions error for activity, api\_keys, credits, organization\_members, workspaces, or end\_users tables, your key is missing the management scope. Create a management API key under **Settings → Management Keys**, then reconnect.
-   If you see a permissions error for the batches table, note that this endpoint requires a regular inference key. Management keys cannot access batch data. Connect a second OpenRouter source with a regular inference key to sync batches.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.