PitchBook Company Profile Scraper — Funding & Investors

Scrape PitchBook (pitchbook.com) company profiles — description, HQ, funding rounds, investors, acquisitions, competitors, and FAQ-derived valuation/revenue — for market research, deal sourcing, competitive intelligence or M&A lead lists. Pay per company profile returned, no subscription.

What you get

One row per company profile, including:

Field	Description
companyId	PitchBook company id (from the profile URL)
companyName	Company name
profileUrl	The PitchBook profile URL scraped
description	Company description
website, logoUrl	Website URL, logo image URL
foundedYear, employees	Year founded, employee count
status, ownershipStatus, financingStatus	Company/ownership/financing status
primaryIndustry, formerlyKnownAs	Industry classification, former names
hqAddress, hqCity, hqPostalCode, hqCountry	Structured HQ address
latestDealType, financingRoundsCount	Latest deal type, number of financing rounds
currentValuation, currentRevenue	Current valuation / revenue, when PitchBook has made them public for this company (null when gated — see below)
investorsTable, investorsTableGated	Full investor rows when public; investorsTableGated=true when this company's investor table is subscription-only
investorsFromFaq, investorsTotalCount	A partial investor name list + total count, surfaced from the page's FAQ even when the full table is gated
fundingRounds, fundingRoundsGated	Funding-round rows when public
acquisitions, acquisitionsGated	Acquisition deals (company, date, type, industry)
competitorsFromFaq, competitorsTotalCount	Named competitors + total count
acquisitionDate, acquiredBy	If this company was itself acquired
faq	The full public Q&A block PitchBook publishes for this company
scrapedAt	ISO 8601 timestamp

Every gated table is explicitly flagged (investorsTableGated, fundingRoundsGated, acquisitionsGated, competitorsTableGated) so you can always tell "PitchBook doesn't have this" apart from "this data is behind PitchBook's own paywall for this company" — this actor never guesses or fabricates a value for a locked table.

Input

Field	Type	Description
startUrls	array	PitchBook company profile URLs, e.g. https://pitchbook.com/profiles/company/10874-98
maxItems	integer	Max profiles to scrape and charge for (default 50)

Example input

{
  "startUrls": [
    { "url": "https://pitchbook.com/profiles/company/10874-98" }
  ],
  "maxItems": 10
}

Access & reliability

PitchBook profile pages sit behind Cloudflare Enterprise-class bot defence. This actor reaches the site through a built-in managed access layer — no proxy account, key, or login is required on your side. Extraction keys on the page's own structured data (JSON-LD, semantic HTML attributes), not styling classes, so it stays robust across front-end redeploys.

Pricing

Pay per company profile returned (pay-per-result). You are charged only for profiles actually delivered to your dataset — failed or blocked fetches cost nothing.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.