Linking Crunchbase as a source
The Crunchbase connector syncs company, funding, and investment data from Crunchbase into PostHog, including organizations, people, funding rounds, acquisitions, investments, IPOs, and funds.
The Crunchbase Search API requires a paid Enterprise or Applications license from Crunchbase. A Basic-plan API key returns a 403 error and is rejected at connection time. Check the Crunchbase pricing page for details on eligible plans.
This source is currently in alpha. If you encounter issues, reach out to our support team.
Requirements
Before you begin, you need:
- A Crunchbase account with an Enterprise or Applications license
- A Crunchbase API user key (found in your Crunchbase account integrations)
Adding a data source
- Go to the Data pipeline page and the Sources tab in PostHog.
- Click + New source and select Crunchbase.
- Enter your Crunchbase User key.
- Optional: Add a prefix to your table names.
- Click Next.
The data warehouse then starts syncing your Crunchbase data. You can see details and progress in the data pipeline sources tab.
Available tables
| Table | Description |
|---|---|
organizations | Company data including description, website, founding date, categories, location, total funding, employee count, and operating status |
people | Individual profiles with first and last names |
funding_rounds | Funding round details including announcement date, investment type, money raised, funded organization, and investor count |
acquisitions | Acquisition events with announcement date, acquirer, acquiree, and price |
investments | Individual investment records with announcement date, investor, funding round, and amount invested |
ipos | IPO events including public date, stock symbol, money raised, and valuation |
funds | Investment fund details with announcement date, money raised, and fund name |
All tables use uuid as the primary key.
Sync behavior
All Crunchbase tables support incremental syncing on the updated_at field. During incremental syncs, PostHog queries Crunchbase for records where updated_at is greater than or equal to the last synced value, so only new and modified records are fetched.
Data is partitioned by the created_at field using monthly partitions.
Configuration
| Option | Type | Required |
|---|---|---|
User key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
organizations | A company or organization profile in Crunchbase. | Incremental, Full refresh | updated_at | — |
people | A person profile in Crunchbase, such as a founder, executive, or investor. | Incremental, Full refresh | updated_at | — |
funding_rounds | A funding round raised by an organization in Crunchbase. | Incremental, Full refresh | updated_at | — |
acquisitions | An acquisition of one organization by another in Crunchbase. | Incremental, Full refresh | updated_at | — |
investments | An investment made by an investor into a funding round in Crunchbase. | Incremental, Full refresh | updated_at | — |
ipos | An initial public offering (IPO) by an organization in Crunchbase. | Incremental, Full refresh | updated_at | — |
funds | A fund raised by an investment firm in Crunchbase. | Incremental, Full refresh | updated_at | — |
Troubleshooting
403 Forbidden error at connection time
The Crunchbase Search API requires an Enterprise or Applications license. If you're using a Basic-plan API key, Crunchbase returns a 403 error and PostHog rejects the key at connection time. Upgrade your Crunchbase plan to a tier that includes Search API access.
401 Unauthorized error
Your API user key is invalid or has been revoked. Generate a new key from your Crunchbase account integrations and update the source configuration in PostHog.