Crunchbase Pro

Crunchbase Pro API provides comprehensive access to detailed company, startup, and investment data, offering advanced business intelligence capabilities for market research, competitive analysis, and investment decision-making through extensive datasets and powerful search functionality.

Power end-to-end data operations for your Crunchbase Pro API with Nexla. Our bi-directional Crunchbase Pro connector is purpose-built for Crunchbase Pro, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Crunchbase Pro or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Crunchbase Pro workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Crunchbase Pro credential, you need to obtain an API user key from your Crunchbase account. The API user key is required to authenticate with the Crunchbase Pro API v4.

To obtain your API user key, you need to have a Crunchbase Pro account with API access enabled. Once you have access to your account, you can generate an API user key from your account settings. The API user key is used to authenticate all API requests to the Crunchbase Pro API v4 using the X-cb-user-key header. For detailed information about API key setup and authentication, refer to the Crunchbase API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API User Key	Yes	Yes	The Crunchbase API uses token-based authentication. Check out the Crunchbase API documentation URL for details on obtaining this key.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Crunchbase Pro

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Crunchbase Pro API user key in the API User Key field. This is the API user key you obtained from your Crunchbase Pro account settings. The API user key is sent in the X-cb-user-key header to authenticate all API requests to the Crunchbase Pro API v4.

   Keep your API user key secure and do not share it publicly. The API user key provides access to your Crunchbase Pro account and should be treated as a sensitive credential. The Crunchbase Pro API uses token-based authentication, and the API user key is included in the X-cb-user-key header for all API requests.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Crunchbase Pro connector tile, then select the credential that will be used to connect to the Crunchbase Pro instance, and click Next; or, create a new Crunchbase Pro credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Crunchbase Pro endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

Fetch Organization by UUID or Permalink

This endpoint fetches organizations by their UUID or permalinks. Use this endpoint when you need to retrieve detailed organization information using a specific organization identifier.

• Enter the UUID or permalink of the organization you wish to fetch data for in the Organization UUID or Permalink field. For example: crunchbase or a full UUID. The default value is crunchbase if not specified.

• The endpoint uses GET requests to https://api.crunchbase.com/api/v4/entities/organizations/{'{org_id}'} where {org_id} is the UUID or permalink you provide. The endpoint URL is automatically constructed based on the Crunchbase Pro API base URL and the organization identifier.
• The endpoint does not use pagination and returns the complete organization details in a single request.
• The endpoint will return detailed information for the specified organization. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure.

Organization identifiers can be either UUIDs or permalinks (e.g., crunchbase). The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about fetching organizations by UUID or permalink, see the Crunchbase API documentation.

Fetch Organization by ID in Lookup

This endpoint fetches organizations by their UUID or permalinks stored in a Nexla Lookup. Use this endpoint when you need to retrieve detailed organization information for multiple organizations whose identifiers are stored in a lookup.

• Select the Nexla Lookup that contains UUIDs or permalinks to iterate over from the Lookup for fetching UUIDs dropdown menu. The lookup should contain organization UUIDs or permalinks in one of its columns.

• Enter the column name that contains the UUIDs or permalinks in the UUID column name in Lookup field. This should match the exact column name in your selected lookup that contains the organization identifier values.

• The endpoint uses GET requests to https://api.crunchbase.com/api/v4/entities/organizations/{'{org_id}'} where {org_id} is iterated from the selected lookup column. The endpoint URL is automatically constructed for each organization identifier in the lookup.
• The endpoint does not use pagination and returns the complete organization details in a single request for each organization identifier.
• The endpoint will return detailed information for each organization in the lookup. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure for each organization.

This endpoint iterates through all organization identifiers (UUIDs or permalinks) in the selected lookup column, making a separate API call for each identifier. The lookup must contain organization UUIDs or permalinks in the specified column. The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about fetching organizations by UUID or permalink, see the Crunchbase API documentation.

Fetch Organizations by Domain Name

This endpoint searches for organizations by domain name equality match. This endpoint fetches organizations whose website URL entry is equal to the user input. Use this endpoint when you need to retrieve organizations based on their domain name.

• Enter the domain name of the organization you wish to fetch data for in the Organization Domain Name field. For example: crunchbase.com. The default value is crunchbase.com if not specified.

• The endpoint uses POST requests to https://api.crunchbase.com/api/v4/searches/organizations with a JSON body containing the search query. The request body includes a query with a domain equality match filter. The endpoint URL is automatically constructed based on the Crunchbase Pro API base URL.
• The endpoint uses token-based pagination, automatically fetching additional pages as needed using the after_id query parameter. When a response includes organization UUIDs, Nexla automatically uses the last UUID as the after_id parameter in the subsequent request to fetch the next page of results.
• The endpoint will return all organizations matching the domain name. The response data is extracted from the entities array in the API response ($.entities[*]), with each organization record processed individually.

Domain names should be entered without the protocol (https://) prefix. For example, use crunchbase.com instead of https://crunchbase.com. This endpoint uses POST requests with a JSON body containing the search query. The endpoint supports pagination through the after_id token mechanism. When a response includes organization UUIDs, Nexla automatically uses the last UUID from the entities array as the after_id parameter in the subsequent request to fetch the next page of results. The endpoint uses token-based pagination (iteration.type: paging.next.token) through the after_id mechanism. The response data path is $.entities[*], which extracts all items from the entities array in the API response. The search query limits results to 2000 organizations per request. For detailed information about searching organizations by domain name, see the Crunchbase API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Crunchbase Pro data sources can also be manually configured to ingest data from any valid Crunchbase Pro API v4 endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Crunchbase Pro API endpoints typically follow the pattern https://api.crunchbase.com/api/v4/{endpoint_path} and require API user key authentication in the X-cb-user-key header, which is handled automatically by your credential configuration. The JSON path to data varies by endpoint — for example, $.entities[*] extracts all items from an entities array, $[*] extracts all items from a root-level array, and $ extracts the entire root-level object. For detailed information about available endpoints, see the Crunchbase API documentation.

Once all of the relevant settings have been configured, click the Save button to save and create the new Crunchbase Pro data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.