Company Timeline Data

---

A company's full history — funding rounds, acquisitions, and executive moves — plus firmographics and the investors on its cap table. Paste your target accounts and get back one clean row per record — a company row plus one row per event — each deduplicated across the outlets that reported it and resolved to a single canonical company, not a raw scrape. You pay per result: the company is one record and each event (funding round, acquisition, executive move) is one more, so a company with no events costs one record and a rich history costs a few. Unresolved companies cost nothing.

Use it for company timeline, company history, funding history, company intelligence, account research, company profile data — account research, CRM enrichment, competitive monitoring, and deal sourcing.

What you get

Flat rows you can sort, filter, and export straight to a sheet. Every row carries recordType, companyName, and companyDomain, so rows join back to their company. Two kinds of rows:

• Company row (recordType: company) — firmographics (domain, LinkedIn, HQ, industry, employee count, founded year) plus the deduplicated investors on its cap table.
• Event rows (recordType: funding | acquisition | exec_move) — one per event, with its date and details.

Filter to recordType = company for a firmographic table, or to an event type for a deal feed. Results export to JSON, CSV, or Excel, or stream straight to your database via the Apify API.

Common use cases

• Account research — pull the full story on every target account before a call.
• CRM enrichment — append funding, M&A, and leadership history to your accounts.
• Competitive monitoring — track how rivals raise, acquire, and hire over time.
• Deal sourcing — for investors and corp-dev teams sizing up a company fast.

Input

Input	Description
companies	One company per line: a domain, company name, LinkedIn URL, or Datahyena id. Billed per record (company + each event).
include	Event kinds to include (funding, acquisitions, exec_moves). Leave empty for all. Fewer kinds means fewer events, so a lower cost.

Example output

[
  {
    "recordType": "company",
    "companyName": "Legora",
    "companyDomain": "legora.com",
    "date": null,
    "hqCountry": {
      "code": "SE",
      "name": "Sweden"
    },
    "industryGroup": "Professional Services",
    "investors": [
      {
        "name": "General Catalyst"
      },
      {
        "name": "Y Combinator"
      }
    ]
  },
  {
    "recordType": "funding",
    "companyName": "Legora",
    "companyDomain": "legora.com",
    "date": "2026-04-15",
    "round": "series-b",
    "amountUsd": 50000000,
    "announcedAt": "2026-04-15"
  },
  {
    "recordType": "exec_move",
    "companyName": "Legora",
    "companyDomain": "legora.com",
    "date": "2026-02-01",
    "role": "VP of Engineering",
    "moveType": "appointment",
    "announcedAt": "2026-02-01"
  }
]

FAQ

What does this actor return?

For each company you list: one company row (firmographics + investors) and one row per event (funding round, acquisition, executive move), deduped and matched to a single canonical company. Every row carries companyName and companyDomain so you can join events back to their company.

How do I identify a company?

Any of a domain (stripe.com), a company name, a LinkedIn URL, or a Datahyena company id. We resolve each to one canonical company.

What if a company isn't found?

It is skipped and you are not charged for it. You only pay for companies we resolve and return.

How is this priced?

Pay per result, one result per row — the same model as our other actors. The company row is one result and each event row is one more, so a company with only firmographics is a single result and a company with a long funding, M&A, and leadership history costs a few. Narrow the include list to pull fewer event kinds and pay less.

How fresh is the data?

New events land within hours of being reported and are added to the company's timeline.

Can I get this over an API instead?

Yes. Datahyena is API-first: REST, webhooks, or MCP (Claude, Cursor, Codex). This actor is the Apify-native way to run it.

Use it in your own stack

For ongoing use it is cheaper and more flexible to go direct: REST, webhooks, and MCP, with subscription pricing and 50 free credits to start.

datahyena.com · Docs · MCP

---