Linking Finnhub as a source
This source is currently in alpha. The interface and available tables may change.
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
The Finnhub connector pulls market and company financial data into the PostHog Data warehouse, so you can analyze financial metrics alongside your product data.
Prerequisites
You need a Finnhub account so you can create an API key. A free key works, though the free tier is rate limited to 60 requests per minute and some endpoints require a paid plan.
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 Finnhub, you'll need:
- API key – create a free API key in your Finnhub dashboard.
- Symbols – optional, comma-separated. Per-company tables (company profile, quote, company news, basic financials, recommendation trends, and earnings surprises) are synced for each ticker you list here, for example
AAPL, MSFT, GOOGL. Market-wide tables sync without any symbols. - Exchange – optional. Used for the stock symbols table, for example
US.
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.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Symbols (comma-separated) | text | No |
Indices (comma-separated) | text | No |
Exchange (for the stock symbols table) | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
stock_symbols | All tradable symbols for the configured exchange (default US). Full refresh. | Full refresh | — | — |
market_news | Latest general market news. Full refresh. | Full refresh | — | — |
ipo_calendar | Recent and upcoming IPOs over a rolling window. Full refresh. | Full refresh | — | — |
earnings_calendar | Recent and upcoming company earnings over a rolling window. Full refresh. | Full refresh | — | — |
economic_calendar | Recent and upcoming macroeconomic releases over a rolling window. Full refresh. | Full refresh | — | — |
country | Reference list of supported countries and their metadata. Full refresh. | Full refresh | — | — |
company_profile | Company profile for each configured symbol. Full refresh. | Full refresh | — | — |
quote | Latest real-time quote snapshot for each configured symbol. Full refresh. | Full refresh | — | — |
company_news | Company-specific news per configured symbol. Supports incremental sync on the published datetime. | Incremental, Full refresh | datetime | — |
basic_financials | Basic financial metrics (valuation, margins, growth) per configured symbol. Full refresh. | Full refresh | — | — |
recommendation_trends | Analyst recommendation trends per configured symbol. Full refresh. | Full refresh | — | — |
earnings_surprises | Historical EPS estimate vs actual surprises per configured symbol. Full refresh. | Full refresh | — | — |
financials_reported | As-reported income statement, balance sheet and cash flow per annual filing, for each configured symbol. Supports incremental sync on the period end date. | Incremental, Full refresh | endDate | — |
stock_candles | Daily OHLCV candles for each configured symbol. Supports incremental sync on the candle timestamp. | Incremental, Full refresh | t | — |
sec_filings | Index of a company's SEC filings, for each configured symbol. Supports incremental sync on the filed date. | Incremental, Full refresh | filedDate | — |
insider_transactions | Insider buy and sell transactions reported on Form 3/4/5, for each configured symbol. Supports incremental sync on the transaction date. | Incremental, Full refresh | transactionDate | — |
dividends | Dividend payouts with ex-date, amount, record and pay dates, for each configured symbol. Supports incremental sync on the ex-dividend date. | Incremental, Full refresh | date | — |
peers | Comparable companies for each configured symbol, one row per peer. Full refresh. | Full refresh | — | — |
index_constituents | Member symbols of each configured index, with company name and index weight where the plan provides them. Full refresh. | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, your API key may be invalid or revoked. Create a new key in your Finnhub dashboard, then reconnect.
- If a table fails with a forbidden error, your plan may not include access to that data. Upgrade your plan or deselect the affected tables, 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.