Skip to main content
Every company profile returned by /api/v1/companies/ includes a company_datasets array — chart-ready time series data you can plot directly. Each dataset is a named series of {x, y} points covering revenue, valuation, fundraising, and share price history. This guide walks through a real response (Kraken) to show how the data is structured and how to turn it into charts.

When to use company_datasets

company_datasets is the sweet spot when you want to build your own charts without having to aggregate raw metric rows yourself. The data comes pre-aggregated and sorted chronologically.

Fetch company datasets

Request Kraken’s company profile:
The company_datasets array lives inside the company object alongside financials, documents, and other fields:
A single company can have multiple datasets spanning different data types.

Dataset object reference

Each object in company_datasets has these fields:

Data points

Each entry in the data array has this shape:
y values are always raw numbers. Revenue of 1.66Bisreturnedas1658800000,not1658.8or"1.66B is returned as `1658800000`, not `1658.8` or `"1.66B”`. Format values for display in your UI.
Date conventions for revenue data points follow the same rules described in the Revenue concepts page: December 31 dates are full-year figures, any other month-end date is year-to-date.

Dataset types

Here are the dataset types you’ll find in company_datasets, illustrated with Kraken’s data:

Revenue

Annual or year-to-date revenue figures in USD.

Revenue Growth Rate

Year-over-year revenue growth as a decimal. A value of 1.38 means 138% growth, -0.28 means a 28% decline.
Growth rates are decimals, not percentages. Multiply by 100 for display: (y * 100).toFixed(1) + "%".

Valuation

Company valuation at each funding event. The meta object identifies the specific round.

Amount Raised

Total capital raised per year, aggregated across all rounds in that year. The meta object includes the aggregation method and number of events.

Price per Share

Share price at each funding round. The meta object links back to the specific event.

Issue Price

Similar to Price per Share but sourced from filings. May contain the same values with different provenance.

Filtering datasets by type

To find a specific dataset, filter the array by data_type:
Not every company will have every dataset type. Always check that the dataset exists before accessing its data.

Example: revenue chart

This React component fetches a company and renders a revenue bar chart using Recharts.
This renders a bar chart showing Kraken’s annual revenue from 2022 through 2025, with values formatted as billions.

Example: valuation timeline

Valuation datasets include meta with the funding round name, which you can use as data point labels.
For Kraken, this plots two points: Growth 2019 (4B)andSeriesC2025(4B) and Series C 2025 (15B), each labeled with the round name from meta.

Example: fundraising history table

For fundraising data, a table is often more useful than a chart since the Amount Raised dataset is aggregated annually while Price per Share is per-round.
For Kraken, the share price table shows the progression from 0.03atSeed(2013)to0.03 at Seed (2013) to 61.47 at the Growth round (2025) — a ~2,000x increase.

Tips

  • Values are raw numbers. Revenue of $2.2B is returned as 2204000000. Always format for display.
  • Growth rates are decimals. A y of 1.38 on a Revenue Growth Rate dataset means 138% growth. Multiply by 100 for percentage display.
  • Not every company has every dataset type. Always check that find() returns a result before accessing .data.
  • Date conventions matter. December 31 dates are full-year figures; other month-end dates are year-to-date. See the Revenue concepts page for details.
  • meta varies by dataset type. Valuation and Price per Share datasets include funding round details (name, event_subtype, event_id). Amount Raised includes aggregation info (year, event_count). Revenue datasets typically have no meta.
  • Use /events/ for richer funding data. If you need investor names, round details, or secondary transactions beyond what meta provides, query the /api/v1/events/ endpoint.
  • Use /metrics/ for citations. Datasets don’t include citation sources. If you need to show where a revenue figure came from, use /api/v1/metrics/ which returns full citation chains.