PitchBook Integration

Overview

The PitchBook integration connects DMTR to PitchBook data for position enrichment, intent capture, and entity mapping. Users can surface DMTR registry and transferability data within PitchBook deal and company views. The integration supports data enrichment (PitchBook identifiers and metadata), intent capture (capturing transfer intents from PitchBook workflows), and entity mapping (resolving PitchBook entities to DMTR participants). PitchBook integration requires a PitchBook subscription and DMTR API access.

Capabilities

Capabilities include data enrichment (pulling PitchBook deal, company, and fund data into DMTR positions), intent capture (recording transfer or liquidity intents from PitchBook research workflows), and entity mapping (resolving PitchBook company and fund IDs to DMTR registry participants). Use capabilities according to your PitchBook product and DMTR subscription tier. Intent capture requires user authentication for audit trails.

Prerequisites

Prerequisites include a PitchBook subscription with API access, DMTR API credentials with research platform scopes, and network connectivity. For intent capture, the DMTR extension or API integration must be configured. Verify PitchBook API entitlements for the data types you need. Contact your PitchBook and DMTR representatives for access. Sandbox environments are available for development.

Permissions and scopes

Permissions and scopes required include positions:read, registry:read, research:enrich, and intent:write for intent capture. Use API keys for server-to-server or OAuth for user-delegated flows. Request scopes via the DMTR dashboard. Scope approval may take 1–2 business days. Intent capture scopes require additional compliance review for audit requirements.

Setup

Setup involves provisioning PitchBook API credentials, configuring the DMTR integration in the dashboard, and mapping PitchBook identifiers to DMTR entity types. Follow the setup wizard for step-by-step configuration. Configure intent capture endpoints if using that capability. Test in sandbox before production. Setup typically takes 1–2 hours for experienced integrators.

Supported workflows

Supported workflows include position lookup from PitchBook deal pages, intent capture when users express transfer or liquidity interest, and bulk enrichment of positions with PitchBook data. Workflows integrate with the DMTR extension for interactive use and with the API for batch operations. Unsupported workflows include real-time streaming of PitchBook data; use batch sync instead.

Data model mapping

Data model mapping defines how PitchBook entities (company ID, deal ID, fund ID) map to DMTR Position and Participant objects. PitchBook company and deal identifiers map to DMTR position identifiers; fund and investor data map to participants. Handle identifier resolution and disambiguation. Refer to the mapping reference for field-level details. Some mappings may require custom configuration.

Security

Security requirements include storing credentials in a secrets manager, using TLS for all API calls, and restricting credential access. Do not log or expose PitchBook data in client-side code. Comply with PitchBook data use terms and DMTR security policies. Rotate credentials according to the secrets rotation schedule. Intent capture data is subject to audit; ensure proper access controls.

Limitations

Limitations include PitchBook API rate limits, data latency (some data is delayed), and unsupported PitchBook products. The integration does not support real-time streaming. Some identifier types require manual mapping. Intent capture has additional compliance requirements. Contact support for workarounds or feature requests.

Troubleshooting

Troubleshooting steps include verifying credentials and scopes, checking PitchBook API status, and reviewing DMTR API logs. Common issues: identifier resolution failures, rate limit errors, and intent capture validation errors. Use the DMTR support portal for escalation. Include request IDs and timestamps in support tickets.

Reference

Reference documentation includes the PitchBook API documentation, DMTR API reference, and the integration mapping specification. Links are available in the integrations dashboard. Keep documentation updated as APIs evolve.