Skip to main content

Data Source

Follow the instructions below to create a new data flow that ingests data from a Crunchbase Pro source in Nexla.
cb_pro_api.png

Crunchbase Pro

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the Crunchbase Pro connector tile from the list of available connectors. 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.

  3. In Nexla, Crunchbase Pro data sources can be created using pre-built endpoint templates, which expedite source setup for common Crunchbase Pro endpoints. Each template is designed specifically for the corresponding Crunchbase Pro endpoint, making source configuration easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    Crunchbase Pro sources can also be configured manually, allowing you to ingest data from Crunchbase Pro endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Crunchbase Pro endpoints. Each template is designed specifically for the corresponding Crunchbase Pro endpoint, making data source setup easy and efficient.

Endpoint Settings​

  • 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.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

Crunchbase Pro data sources can be manually configured to ingest data from any valid Crunchbase Pro API v4 endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Crunchbase Pro sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom authentication headers or request parameters.

API Method​

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Crunchbase Pro API from the Method pulldown menu. The most common methods are:

    • GET: For retrieving data from the API
    • POST: For sending data to the API or triggering actions (e.g., search endpoints)
    • PUT: For updating existing data
    • PATCH: For partial updates to existing data
    • DELETE: For removing data

API Endpoint URL​

  1. Enter the URL of the Crunchbase Pro API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Crunchbase Pro API endpoints typically follow the pattern https://api.crunchbase.com/api/v4/{'{endpoint_path}'}.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The endpoint requires API user key authentication in the X-cb-user-key header, which is handled automatically by your credential configuration. For detailed information about Crunchbase Pro API endpoints and available APIs, see the Crunchbase API documentation.

Path to Data​

  1. Enter the JSON path that identifies the location of the relevant data within the API response in the Path to Data field. JSON paths use dot notation to navigate through nested JSON structures.

    • For example, if your API response has the structure {"entities": [...]}, you would enter $.entities[*] to extract all items from the entities array.
    • Use $[*] to extract all items from a root-level array.
    • Use $ to extract the entire root-level object.

JSON paths are case-sensitive and must match the exact structure of your API response. Crunchbase Pro API responses may use different structures like entities arrays or root-level objects depending on the endpoint. Use the Test button to verify that your JSON path correctly extracts the desired data from the API response.

Save the Data Source​

  1. Once all configuration steps have been completed, click the Save button to save your data source configuration.

  2. The data source will now be available in your data flow and will begin ingesting data according to the configured schedule and endpoint settings.