Leadfeeder
Leadfeeder (now part of Dealfront) is a B2B lead generation and website intelligence platform that identifies the companies visiting your website and turns that activity into actionable sales intelligence. Its public REST API exposes accounts, leads, visits, companies, contacts, custom feeds, and enrichment jobs so you can integrate this intent data into your own analytics and sales workflows.

Power end-to-end data operations for your Leadfeeder API with Nexla. Our bi-directional Leadfeeder connector is purpose-built for Leadfeeder, 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 Leadfeeder or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Leadfeeder workflows fast, secure, and fully governed.
Features
Type: API
- 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 Leadfeeder credential, you need a Leadfeeder API key and the base URL for the Leadfeeder API. Leadfeeder authenticates every request with an API key sent in the X-Api-Key header, and the API is served from https://api.leadfeeder.com.
To obtain your Leadfeeder API key, follow these steps:
-
Sign in to the Leadfeeder platform with an account that has permission to manage API access.
-
Open Settings (the gear icon), then navigate to Personal > API Keys.
-
Click Create a new API key, enter a descriptive name for the token (for example, "Nexla Integration"), and confirm to generate the key.
-
Copy the generated API key immediately and store it securely. For security reasons, Leadfeeder displays the full token only once, so it cannot be retrieved again after you leave the page.
If you do not see the API Keys section, your user may not have the required permissions. Ask your Leadfeeder account administrator to grant API access. The API key is sensitive information and should be treated as a secret. For more detail, see the Leadfeeder API documentation and How to Create and Use Your Leadfeeder API Keys.
Authenticate
Credentials required
| Field | Required | Secret | Description |
|---|---|---|---|
| API Key Value | Yes | Yes | An encoded string value used as a secret token to authenticate API requests |
| Base URL | Yes | No | The base URL for the Leadfeeder API. |
Create a credential in Nexla
-
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Resource descriptions are recommended but are not required. Use them to identify the Leadfeeder account or access level represented by this credential.
-
Enter your Leadfeeder API key in the API Key Value field. This is the token you generated under Settings > Personal > API Keys in Prerequisites. Nexla sends this value in the
X-Api-Keyheader on every request and keeps it confidential. -
Enter the Leadfeeder API endpoint in the Base URL field. The standard value is
https://api.leadfeeder.com. -
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 Leadfeeder connector tile, then select the credential that will be used to connect to Leadfeeder, and click Next; or, create a new Leadfeeder 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 Leadfeeder 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.
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
Leadfeeder data sources can also be manually configured to ingest data from any valid Leadfeeder API 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.
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 Leadfeeder 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 Leadfeeder destination, and select the Send to Destination option from the menu. Select the Leadfeeder connector from the list of available destination connectors, then select the credential that will be used to connect to Leadfeeder, and click Next; or, create a new Leadfeeder credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Leadfeeder endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Manual configuration
Leadfeeder destinations can also be manually configured to send data to any valid Leadfeeder API endpoint. 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.
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 send the data to the configured Leadfeeder endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Leadfeeder endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.