Skip to main content

Captain Data

Captain Data is an AI-powered data extraction and automation platform that enables sales, marketing, and go-to-market teams to collect, enrich, and orchestrate B2B data at scale. The platform provides access to 500M+ professional profiles and 50M+ companies through a simple RESTful API, with integrations spanning LinkedIn, Google, and 100+ additional data sources. Captain Data's workflow engine allows users to chain automated data extraction and enrichment actions—without code—to build qualified prospect lists, track buyer intent signals, and sync enriched contact and company data into CRMs and other downstream tools. Its API allows developers to programmatically launch workflows, retrieve job results, and manage integrations, making it well-suited for product teams building data-driven features and GTM teams scaling outbound operations.

Captain Data icon

Power end-to-end data operations for your Captain Data API with Nexla. Our bi-directional Captain Data connector is purpose-built for Captain Data, 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 Captain Data or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Captain Data 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​

To connect Nexla to Captain Data, you will need a Captain Data API key and your project's unique identifier (Project UID). Captain Data uses API key authentication, with the key passed in the Authorization request header alongside your Project UID in a separate x-project-id header.

Obtain a Captain Data API Key and Project UID​

Captain Data API keys are generated directly from your Captain Data workspace settings. Each API key is tied to the user account that created it within a given workspace.

  1. Sign in to your Captain Data workspace at app.captaindata.com.

  2. Navigate to Settings > Developers (or go directly to https://app.captaindata.com/settings/developers) to access your API credentials.

  3. In the API Keys section, click Generate API Key or Create New Key to create a new API key for use with Nexla.

  4. Enter a descriptive label for the key (for example, "Nexla Integration") so you can identify its purpose later.

  5. Copy the generated API key immediately and store it in a secure location. For security reasons, Captain Data may not display the full key value again after the initial creation.

  6. On the same Developers settings page, locate your Project UID (also referred to as the Project ID). This is the unique identifier for your Captain Data project workspace and is required alongside the API key for all authenticated API requests.

Important

Treat your Captain Data API key as a sensitive credential. Do not share it in emails, code repositories, or other insecure locations. If a key is ever compromised, revoke it immediately from your Captain Data settings and generate a replacement key.

API keys in Captain Data are tied to your individual user account within a workspace. If other team members need API access, they must generate their own API keys from their own accounts. For additional guidance, see the Captain Data API documentation.

Authenticate​

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.

  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 Captain Data API key in the API Key field. This key authenticates Nexla with the Captain Data API and is sent as the value of the Authorization: x-api-key header with each API request. The key should be kept confidential and only shared with authorized systems such as Nexla.

  4. Enter your Captain Data Project UID in the Project ID field. The Project UID is the unique identifier for your Captain Data workspace project and is required alongside the API key to scope API requests to the correct project. You can find this value on the Settings > Developers page of your Captain Data workspace.

    The Project UID is different from your account username or workspace name. It is a unique alphanumeric identifier assigned by Captain Data to your project. Ensure you copy the exact value shown on the Developers settings page.

  5. 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 and can be selected for use with a new data source or destination.

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 Captain Data connector tile, then select the credential that will be used to connect to the Captain Data instance, and click Next; or, create a new Captain Data 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 Captain Data 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.

Get Workspace

Retrieves the current workspace information and details. Use this endpoint to fetch metadata about your Captain Data workspace, including configuration and usage details.

This endpoint returns workspace-level metadata and is useful for validating credential configuration before setting up other Captain Data endpoints.

List Workflows

Returns a list of all workflows in the workspace. Use this endpoint to retrieve available Captain Data workflow definitions, including their configuration and status.

Workflow records include workflow name, UID, and configuration. Workflow UIDs returned here can be used to scope job queries to specific workflows.

List Jobs

Returns a list of all jobs across workflows. Use this endpoint to retrieve the full job history for your Captain Data workspace, including both completed and failed runs.

Job records include status, start time, end time, and result counts. Use this endpoint to monitor execution history across all workflows in your workspace.

List Successful Jobs

Returns a list of successfully completed jobs across workflows. Use this endpoint when you only need to process results from jobs that completed without errors.

Job UIDs from this endpoint can be used with the Get Job Results endpoint to retrieve the actual data extracted by each successful job run.

Get Job Results

Retrieves the results data for a specific job. Use this endpoint to extract the B2B data (profiles, companies, or other records) produced by a completed Captain Data workflow job.

  • Issues a GET request to https://api.captaindata.co/v3/jobs/{job_uid}/results.
  • Response data is located at $.results[*]; use this path in the Path to Data field to extract individual result records.
  • Configure the following parameter: Job ID — the unique identifier (UID) of the job whose results you want to retrieve.

Job UIDs can be found in the Captain Data UI under workflow run history, or retrieved programmatically using the List Jobs or List Successful Jobs endpoints. Use lookup-based macros to dynamically pass job UIDs from another Nexla source.

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​

Captain Data data sources can also be manually configured to ingest data from any valid Captain Data API endpoint, including endpoints not covered by the pre-built templates, chained API calls used to fetch job results across multiple workflows, or sources that require 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.

The Captain Data API base URL is https://api.captaindata.co/v3. Common endpoint URLs include https://api.captaindata.co/v3/jobs/{'{job_uid}'}/results (retrieve the results of a specific workflow job), https://api.captaindata.co/v3/workflows (list all workflows), and https://api.captaindata.co/v3/workspace (retrieve workspace information). Captain Data responses nest data records inside a data array alongside pagination metadata, so the job results endpoint requires a path to data of $.data[*] to extract individual records; a pagination object with total, page, and per_page values is available alongside data if you need to capture this as metadata.

You do not need to add the Authorization or x-project-id headers manually — these are added automatically based on the values configured in your Captain Data credential.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Captain Data 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.

Use as a destination​

Click the + icon on the Nexset that will be sent to the Captain Data destination, and select the Send to Destination option from the menu. Select the Captain Data connector from the list of available destination connectors, then select the credential that will be used to connect to the Captain Data organization, and click Next; or, create a new Captain Data credential for use in this flow.

Manual configuration​

Captain Data destinations can be manually configured to send data to any valid Captain Data API endpoint. Common use cases include launching Captain Data workflows with input data, pushing enriched prospect lists into Captain Data collections, or triggering automated outreach sequences. 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, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Captain Data API endpoints generally accept JSON-formatted request bodies. The Captain Data API base URL is https://api.captaindata.co/v3; common destination endpoints include https://api.captaindata.co/v3/workflows/{'{workflow_uid}'}/launch (launch a workflow run with input data) and https://api.captaindata.co/v3/collections (create or update records in a collection). You do not need to add the Authorization or x-project-id headers manually — these are added automatically based on the values configured in your Captain Data credential.

If batching records together—for example, when launching a workflow with multiple inputs—use the Property Inside JSON Object grouping algorithm with a property name such as inputs to match the Captain Data API's expected request structure. You can also enable the response webhook option to process the API response as a new Nexla webhook data source, which is useful for capturing return data such as the job_uid returned when a workflow is launched; the captured job UID can then be used to retrieve job results via a separate Captain Data source.

Save & activate​

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to the configured Captain Data endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Captain Data API until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.