What's Changing?
The legacy Leadfeeder API had its own authentication method and a separate credit system, which made building and maintaining integrations complex. The new unified API simplifies everything:
One API Key: A single API key will now be used for company data, contact data, web visitor data, and IP enrichment operations.
Better Performance: Experience improved reliability and speed.
New Features: Take advantage of new capabilities like bulk requests and access to your custom fields, tags, and lists within the API.
What You Need to Do
Note: The legacy APIs will continue to work as they do today, nothing is changing right now. When a deprecation date is confirmed, we will communicate it well in advance so you have plenty of time to make any necessary changes.
Customers using the legacy Leadfeeder (Web Visitors) API need to migrate to the new Leadfeeder API. Legacy API keys will not be automatically migrated.
Generate a new API key: You will need to create a new API key in your platform settings -> personal -> api keys.
Update your integrations: Your existing integrations must be updated to use the new API endpoints.
Handle the new response structure: You will need to update your integration to work with the new data response format.