PitchBook limited partner profile API

Endpoint facts

Method

GET

API path

/pitchbook/limited-partner

Auth

apiKey

Credits

3 credits/request

Platform

PitchBook

Response schema

#/definitions/pitchbook.limitedPartnerResponseDoc

Overview

Returns the free/teaser content of a PitchBook limited partner (institutional investor, e.g. pension fund, endowment, or insurance company) profile page: overview, description, contact, and a preview of fund commitments. PitchBook gates most numeric figures and full lists behind a paid subscription; those come through as empty cells rather than being fabricated. Some limited partner profiles have no FAQ section (thinner profiles) -- this is normal, not a sign of a blocked or broken response. Pass exactly one of `id` or `url`. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

3 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- Passing neither or both of `id`/`url` returns an invalid-parameter error. - A `url` that isn't an absolute `https://pitchbook.com/profiles/limited-partner/<id>` URL returns an invalid-parameter error. - A response missing the profile name is treated as an upstream error (parser drift or a blocked/challenge page), never a `200` with empty data. - Some limited partner profiles have no FAQ section at all — PitchBook only generates one for profiles with enough content. `faqs` being empty on an otherwise complete response is normal, not a sign of a blocked or broken request. Example response: ```json { "code": 200, "msg": "OK", "data": { "kind": "limited-partner", "id": "864326-44", "name": "TKP Pension", "description": "TKP Pension is a corporate pension based in Groningen, Netherlands. Established in 1988, the fund manages pensions, offers asset management services, and advises pension funds on legal, tax, actuarial, and investment matters.", "overview": { "Type": "Corporate Pension", "Year Founded": "1988", "Professionals": "2" }, "contact": { "Institution Type": "Corporate Pension", "Title": "Chief Financial and Risk Officer", "Website": "http://www.tkppensioen.nl", "Corporate Office": "Europaweg 27, 9723 AS Groningen, Netherlands" }, "tables": [], "faqs": [ {"question": "When was TKP Pension founded?", "answer": "TKP Pension was founded in 1988."} ], "source_url": "https://pitchbook.com/profiles/limited-partner/864326-44", "fetched_at": "2026-07-20T20:37:00Z" } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related