PitchBook API: Access, Pricing, and What You Get

PitchBook doesn’t sell its API as a standalone product with a price tag. It’s a premium add-on layered on top of a paid platform subscription. Access only comes through a separate contract with PitchBook’s Direct Data team. There’s no public price list for it anywhere, not even on PitchBook’s own site. This guide walks through what it costs, what it actually gives you, and whether your team needs it.

What the PitchBook API Actually Is

PitchBook’s API is a RESTful, JSON-based interface. It lets you pull data programmatically from PitchBook’s private-market database into your own systems — a CRM, a data warehouse, a dashboard, or a custom app. It covers PitchBook’s core entity types: companies, deals, investors, funds, people, limited partners, and service providers. Each entity’s data spans several related endpoints. That means you can request only the fields your integration needs, instead of pulling a full record every time.

It’s easy to confuse the API with two other PitchBook products. Each solves a similar problem differently:

• The Excel Plugin pulls PitchBook data straight into a spreadsheet for manual analysis. No integration work is involved — it’s built for analysts, not developers.
• The Data Feed delivers scheduled bulk exports (.dat, .csv, or Parquet files) to a warehouse like Snowflake, AWS, or Azure. Delivery runs on a daily, weekly, monthly, or quarterly cadence. It suits teams that need PitchBook’s entire dataset, or a large slice of it, sitting in their own infrastructure.
• API access sits in between the two. It offers on-demand, near-real-time queries scoped to a configurable set of entities — the companies and industries you actually track, not PitchBook’s full universe.

If you’re building a live dashboard or enriching CRM records as deals happen, you want the API. If you need PitchBook’s whole dataset for a quant model, you want the Data Feed. For pulling a few numbers into a spreadsheet occasionally, the Excel Plugin covers it.

How to Get API Access (It’s Not Self-Serve)

There’s no developer signup page. There’s no “generate an API key” button in the dashboard. You can’t start testing without a sales conversation first. Access works differently depending on where you’re starting from:

• Existing PitchBook platform customers go to My PitchBook → Plugins & Apps → PitchBook API inside the platform. That routes a request to the Direct Data team.
• New customers contact the Direct Data team directly. API access then gets negotiated alongside a platform subscription.

Either way, credentials only arrive after a contract is signed — an API key or token. A sandbox environment exists for pre-production testing once you’re in the process. It gives developers a space to practice calls before going live, though it isn’t accessible before that point.

Authentication itself is API-key or token-based. PitchBook doesn’t publish the technical specifics anywhere publicly: header placement, token expiry, refresh flow. Those details only surface once you’re a contracted client with documentation access.

PitchBook API Pricing: What Actually Drives the Cost

Here’s the honest answer: nobody outside PitchBook can tell you an exact number, because PitchBook doesn’t publish one, and neither does anyone else who’s reviewed the API. What you can do is build a realistic set of expectations from the pieces that are publicly confirmed.

The Baseline Subscription

Start with the platform itself. A standard PitchBook subscription, before any API access, typically runs $15,000–$30,000 per year for a single named seat. Multi-seat and enterprise deals climb well past $100,000. The exact number depends on user count, data modules, and contract length. We break this down in full in our PitchBook pricing guide, including what pushes the number up or down.

What Independent Sources Say About the API Add-On

API access sits on top of that base. Several independent sources describe it the same way, without ever attaching a figure to it: a “premium add-on” requiring separate negotiation. That negotiation typically pushes you into a higher contract tier. PitchBook’s LP Intelligence module works similarly — it reportedly adds another $5,000–$10,000 per year to a base subscription. Vendr tracks real PitchBook transaction data, and it describes the API and Excel Plugin the same way. Both carry additional fees depending on contract structure, with no public number attached.

What Real Contracts Show

The clearest evidence of contract size doesn’t come from marketing pages or blog estimates. It comes from public procurement records. Government contracting bodies must publish vendor agreement terms, and PitchBook’s own signed order forms have shown up in that data. One authorized-user agreement for 18 seats came to $100,800 after discount, against a $126,000 list price. A separate contract listed an Annual Contract Value of $98,000, cut to $19,600 after a one-time discount. Additional seats on these contracts run roughly $7,000 per year each. None of these documents break out API access as its own line item. But they confirm the seat-based, heavily-negotiated structure that every add-on sits inside.

The Realistic Takeaway

Say you’re already paying for a platform subscription and now negotiating API access on top. Expect it to move you into your next contract tier, rather than show up as a small line item. Negotiate it the way you’d negotiate seat count or data modules — there’s no published rate card to check yourself against.

What You Get: Rate Limits, SDKs, and Documentation

This is the part that catches developers off guard. It’s worth setting expectations before you sign anything:

• No public rate limits. Call-volume caps and burst limits aren’t published anywhere. Constraints get set per contract with the Direct Data team, so you can’t plan integration capacity until after the deal is signed.
• No official SDKs. The API works with any standard HTTP client, but no maintained client library exists in any language. Your team owns the full integration layer: authentication, request handling, pagination, retries, error handling.
• Documentation stays private. The API guide and endpoint reference sit behind platform authentication, visible only to contracted clients. There’s no public OpenAPI spec and no interactive explorer.
• No webhooks. Real-time updates mean polling the API yourself. There’s no event-driven or push-notification pattern. Scheduled delivery is what the Data Feed handles, not the API.
• A sandbox does exist. Once you’re in the process, PitchBook provides a test environment for practicing call structure before going live. The Direct Data team supports onboarding during this phase.

None of this makes the underlying data less valuable. PitchBook’s dataset spans millions of companies, investments, and investor profiles, updated multiple times a day. It just means the developer experience is closer to an enterprise data-licensing deal than a typical modern API integration.

API vs. Data Feed vs. Excel Plugin: Which One Do You Actually Need

Your situation	Best fit
You need to check a few data points occasionally, no engineering resources	Excel Plugin
You’re building a live dashboard, CRM enrichment flow, or app that needs specific, current data on demand	API
You need PitchBook’s full dataset (or a large slice of it) sitting in your own warehouse for modeling or analytics	Data Feed
You need both live lookups and scheduled bulk delivery	API + Data Feed, negotiated together — PitchBook positions them as complementary, not competing

A common mistake teams make is assuming the API is the “upgrade” from the Excel Plugin. It isn’t — they solve different problems for different users. The API is for engineering teams building something that consumes PitchBook data automatically; the Excel Plugin is for analysts who just want the numbers in a spreadsheet faster.

Who Actually Needs API Access (And Who Doesn’t)

API access tends to make financial sense for:

• Corporate development teams pulling deal and financing data continuously into an internal CRM or deal-tracking system
• Larger PE or VC firms with dedicated data engineering resources who are already building on top of other data sources and want PitchBook data in the same pipeline
• Firms running quantitative or model-driven sourcing that needs fresh data flowing in automatically, rather than pulled manually

It tends not to make sense for:

• Solo investors, small funds, or search-fund operators who just need to look things up as deals come in — a standard subscription (or a cheaper PitchBook alternative) covers this without the extra contract layer
• Teams without in-house engineering resources to own an unsupported, SDK-less integration
• Anyone who mainly needs occasional exports rather than continuous, automated data flow — the Excel Plugin is both cheaper and simpler for this

If you’re not sure which camp you fall into, the honest test is: are you already building or maintaining a data pipeline today that this would plug into? If the answer is no, the API adds contract complexity and cost without a corresponding workflow to justify it.

What the API Doesn’t Cover — And Where a Data Room Comes In

It’s worth being explicit about a limitation that’s easy to miss: PitchBook’s API — and PitchBook generally — is a sourcing tool. It tells you who’s raised money, who invested, at what valuation, and who the people behind a deal are. That’s enormously useful for finding and evaluating targets. It has nothing to do with what happens once a deal moves into diligence.

Once you’re past sourcing and into an active transaction — sharing financials, contracts, cap tables, and other sensitive documents with a counterparty, tracking who viewed what, and running a structured Q&A process — that’s a different tool entirely: a virtual data room. No amount of PitchBook API access replaces it, because they’re built for opposite problems: PitchBook helps you find the deal; a data room helps you close it securely. We cover this handoff — and what a due diligence VDR should actually include — in our guide to virtual data rooms for due diligence.

If your team is automating deal sourcing through the API and also budgeting for the diligence stage that follows, our M&A Deal Readiness Calculator is worth running alongside this — it accounts for both sides of that budget, not just the data subscription.

Frequently Asked Questions

---

This article draws on PitchBook’s own product pages, publicly available government procurement records for PitchBook contracts, and third-party pricing research from Vendr and other sources. Pricing figures for API access specifically are estimates based on how comparable add-ons are priced, since PitchBook does not publish API pricing publicly.