# Linking Finage as a source - Docs

![](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`

[Learn more](/wizard.md)

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

**Alpha release**

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

The Finage connector pulls US stock market data, such as quotes, trades, and historical OHLCV bars, into the PostHog Data warehouse, so you can analyze it alongside your product data.

## Prerequisites

You need a Finage account with a paid plan that includes access to the **US stocks** endpoints so you can create an API 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 Finage, you'll need:

-   **API key** – find your key in the [Finage dashboard](https://finage.co.uk/dashboard) after subscribing to a plan. The key needs access to the US stocks endpoints.
-   **Symbols** – a comma-separated list of US stock symbols to sync, for example `AAPL,MSFT,TSLA`.
-   **Backfill start date** – optional. The earliest date (`YYYY-MM-DD`) to pull historical aggregate bars from. Defaults to the connector's built-in start date.

## 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](/docs/cdp/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

This source is full refresh only.

## Configuration

| Option | Description |
| --- | --- |
| API keyType: passwordRequired: True |
| SymbolsType: textRequired: True | Comma-separated list of US stock symbols to sync, e.g. AAPL,MSFT,TSLA. |
| Backfill start dateType: textRequired: False | Earliest date (YYYY-MM-DD) to pull historical aggregate bars from. Defaults to 2020-01-01. |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| last_quote | Latest bid/ask quote per symbol. Point-in-time snapshot, full refresh. | Full refresh | — | symbol |
| last_trade | Latest trade (price and size) per symbol. Point-in-time snapshot, full refresh. | Full refresh | — | symbol |
| aggregates | Historical daily OHLCV bars per symbol from the backfill start date. Full refresh. | Full refresh | — | symbol, t |

## Troubleshooting

-   If you see an authentication error, your Finage API key may be invalid or revoked. Generate a new key in your Finage dashboard, then reconnect.
-   If you see a permission error, your Finage plan does not include access to this data. Upgrade your Finage subscription or remove the affected tables, then reconnect.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](/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.

### Community questions

Ask a question

### Was this page useful?

HelpfulCould be better