Changelog
Follow up on the latest improvements and updates.
RSS
API:
- ⚠️ Breaking: Theemployee_countfilter on POST /v1/icps and PATCH /v1/icps/{id} no longer accepts the values1-2,3-10,11-50,51-200, and201-500; integrations using these values must migrate to the new ranges.
- ⚠️ Breaking: Thesource_urlfield in POST /v1/companies/signals responses is now nullable; clients should handlenullfor signals that have no associated source URL.
- ⚠️ Breaking: Theaccount_companyvalue has been removed from theincludequery parameter on GET /v1/accounts; requests that pass this value will receive an error.
- ✨ New: Theemployee_countfilter on POST /v1/icps and PATCH /v1/icps/{id} now accepts three consolidated range values:1-10,11-100, and101-500.
- ✨ New: Added optionalsort[field]andsort[direction]query parameters to GET /v1/web-visits/companies, allowing results to be sorted by a chosen field and direction.
- ✨ New: Added POST /v1/connect-crm-record-jobs and GET /v1/connect-crm-record-jobs/{job_id} to asynchronously connect a Leadfeeder company to a CRM record and check the job status.
- ✨ New: Added POST /v1/disconnect-crm-record-jobs and GET /v1/disconnect-crm-record-jobs/{job_id} to asynchronously disconnect a Leadfeeder company from a CRM record and check the job status.
- ✨ New: Added POST /v1/enrich-crm-record-jobs and GET /v1/enrich-crm-record-jobs/{job_id} to asynchronously enrich a CRM record with Leadfeeder data and check the job status.
- ✨ New: Added POST /v1/create-crm-contact-jobs and GET /v1/create-crm-contact-jobs/{job_id} to asynchronously create a contact in your CRM and check the job status.
- ✨ New: Added POST /v1/create-crm-lead-jobs and GET /v1/create-crm-lead-jobs/{job_id} to asynchronously create a lead in your CRM and check the job status.
- ✨ New: Added POST /v1/create-crm-organization-jobs and GET /v1/create-crm-organization-jobs/{job_id} to asynchronously create an organization in your CRM and check the job status.
- ✨ New: Added PATCH /v1/crm-connections/{id} to update an existing CRM connection.
- ✨ New: Added GET /v1/crm-contacts/{id} to retrieve a single CRM contact by ID.
- ✨ New: Added GET /v1/crm-leads/{id} to retrieve a single CRM lead by ID.
- ✨ New: Added GET /v1/crm-organizations/{id} to retrieve a single CRM organization by ID.
- ✨ New: Added GET /v1/crm-users to list users available in your connected CRM.
- ✨ New: The POST /v1/companies/signals endpoint now supports two new signal categories —employee_count_changesandrevenue_changes— which can be passed ascategoriesfilter values and will appear in thecategoryfield of returned signals.
- ✨ New: Added POST /v1/subscriptions/purchase-links endpoint for creating purchase links.
- ✨ New: Added GET /v1/subscriptions/purchase-options endpoint for retrieving available purchase options.
- ✨ New: The GET /v1/accounts response now includes arelationships.subscriptionsfield on each account item.
- ✨ New: Added an optionalfilters/company_idsparameter to POST /v1/web-visits, allowing you to filter web visit results to a specific set of companies.
- ⚡ Improved: The POST /v1/companies/enrichment-jobs and GET /v1/companies/enrichment-jobs/{job_id} responses now include an optionaladvanced_searchfield underdata.attributes.configuration.
- ⚡ Improved: Added an optionalapp_urlfield to responses for buyer personas, campaigns, companies, contacts, ICPs, lists, web visits, custom feeds, and goals — including when these resources appear as embedded relationships — providing a direct link to each resource's page in the Leadfeeder app.
MCP:
- ✨ New: Theget_purchase_optionstool is now available, allowing AI assistants to retrieve available purchase options.
- ✨ New: Thecreate_purchase_linktool is now available, allowing AI assistants to generate a purchase link.
- ✨ New: Thesearch_web_visitstool now accepts acompany_idsfilter, letting you retrieve web visits for up to 1,000 companies in a single call instead of querying one company at a time.
The
next_reset_on
deprecation is now liveAs announced earlier, the deprecation of
next_reset_on
on the /accounts
endpoint took effect on November 17, 2026
.What changed
- next_reset_onis still present in the response, but it is marked as deprecated and returns no value.
- It will be removed from the response in a future release. We'll announce the removal date in advance.
What to do
If your integration still reads
next_reset_on
, switch to renews_at
from the relevant credit pool:- recurring.renews_at: credits included in your subscription. This is the same valuenext_reset_onused to return.
- one_off.renews_at: extra credits you purchased.
If you don't use
next_reset_on
, no action is needed.Questions? Contact support@leadfeeder.com

The Leadfeeder MCP Server now supports Google Gemini Enterprise. You can connect it as a custom MCP server and work with your Leadfeeder data from Gemini in plain language.
What’s new
Google Gemini is now a supported client for the Leadfeeder MCP Server (https://mcp.leadfeeder.com/mcp), alongside Claude, Claude Code, ChatGPT, Microsoft 365 Copilot, Perplexity, Codex and Cursor.
Gemini connects through OAuth 2.0 with an OAuth application you create in Leadfeeder under Companies → Applications. You need the OAuth Applications right under Company Access Rights.
The scopes you select for the application control what Gemini can access. Use the same scopes in the Gemini MCP configuration.
Get started: follow the step-by-step guide in Connect your AI tool.
We are improving the /accounts endpoint in the Leadfeeder API so you get a clearer view of your credits. As part of this, the
next_reset_on
field is being deprecated on November 17, 2026.What’s new
The /accounts response now shows your credits in two separate pools.
- recurring: the credits included in your subscription
- one_off: any extra credits you purchased on top
Each pool has its own
renews_at
date. You can see exactly when each type of credit refreshes, instead of relying on a single date for everything.What’s changing
- Until November 17, 2026: nothing changes. next_reset_on keeps working as it does today. The new renews_atdates are already available in each credit pool.
- From November 17, 2026: next_reset_onstays in the response, but it is marked as deprecated and no longer returns a value. It will be removed fully at a later date.
What you need to do
If your integration reads
next_reset_on
, switch to renews_at
from the relevant credit pool before November 17. Otherwise, your integration will receive an empty value from that date. recurring.renews_at holds the same value next_reset_on returns today.If your integration does not use next_reset_on, there is nothing you need to do.
For questions, reach out to our support team at support@leadfeeder.com
- 🆕 [New]:Added a Goals endpoints for creating, retrieving, updating, and deleting web visit goals. It coversGET,POSTandDELETEon/v1/web-visits/goals, andGETandPATCHon/v1/web-visits/goals/{id}.
- 🆕 [New]Thelocationsfilter in[POST /v1/companies/search](https://docs.leadfeeder.com/api/public/search-companies-4008955e0)now accepts additional input formats, giving more flexibility in how location criteria are specified.
- ⚡ [Improved]Added an optionallabelfield to the geo filter in advanced search criteria on the batch job endpoints (POST /v1/companies/enrichment-jobs,POST /v1/lists/batch-add-to-list-jobs,POST /v1/lists/batch-remove-from-list-jobs,POST /v1/tags/batch-add-tags-jobs,POST /v1/tags/batch-remove-tags-jobs). The field is also returned in the job creation and status responses.
- 🆕 [New][MCP]Added the web visit goal toolscreate_web_visits_goal,get_web_visits_goal,get_web_visits_goals,update_web_visits_goal, anddelete_web_visits_goal, so AI assistants can create, list, retrieve, update, and remove goals on your behalf.
- ⚡ [Improved][MCP]Theget_web_visits_custom_feedstool accepts a newfilter_has_connected_listparameter to return only feeds that have a connected list.
- ⚡ [Improved][MCP]Theget_web_visits_custom_feedsandget_web_visits_custom_feedtools accept"connected_list"as a value forinclude, so connected list data comes back with the feed.- ⚡ - -⚡[Improved][MCP]Thecreate_batch_add_tags_job,create_batch_add_to_list_job,create_batch_remove_from_list_job,create_batch_remove_tags_job, andcreate_company_enrichment_jobtools accept an optionallabelfield on geo filters in advanced search, to attach a readable place name to the center point.
Newimproved
Leadfeeder API - 2026-09-23
- 🆕 [New]The GET /v1/companies/ips response now includes a meta object on each IP entry, providing additional metadata alongside the existing IP data.
- 🆕 [New]ICP objects returned by the ICP endpoints (GET /v1/icps, POST /v1/icps, GET /v1/icps/{id}, PATCH /v1/icps/{id}) now include arelationshipsfield in the response.
- 🆕 [New]Custom feeds now expose aconnected_listrelationship in responses from GET /v1/web-visits/custom-feeds, POST /v1/web-visits/custom-feeds, GET /v1/web-visits/custom-feeds/{custom_feed_id}, and PATCH /v1/web-visits/custom-feeds/{custom_feed_id}.
- 🆕 [New]Addedconnected_listas a supported value for the include query parameter on GET /v1/web-visits/custom-feeds and GET /v1/web-visits/custom-feeds/{custom_feed_id}, allowing you to sideload connected list data in a single request.
- 🆕 [New]Added a filter[has_connected_list] query parameter to GET /v1/web-visits/custom-feeds, enabling you to filter custom feeds by whether they have a connected list.
- 🆕 [New]Campaign responses from GET /v1/campaigns, GET /v1/campaigns/{id}, and PATCH /v1/campaigns/{id} now include a connected_list relationship on the associated custom feed when one is present.
- ⚡[Improved]Thejob_adscategory is available again in the signals endpoint. It now runs on our new signals system, and you don't need to change anything: requests that filter on job_ads work as they did before the pause.
- ⚡[Improved]The max_ip_addresses parameter on GET /v1/companies/ips is now capped at a maximum value of 500.
Newimproved
Leadfeeder API - 2026-09-16
- 🆕 [New]Added the GET /v1/industries endpoint for retrieving industry reference data.
- 🆕 [New]Added GET /v1/settings/cookie-consent endpoint to retrieve your account's cookie consent settings.
- 🆕 [New]Added PATCH /v1/settings/cookie-consent endpoint to update your account's cookie consent settings.
- 🆕 [New]Added GET /v1/settings/data-processing endpoint to retrieve your data processing settings.
- 🆕 [New]Added PATCH /v1/settings/data-processing endpoint to update your data processing settings.
- ⚡[Improved]The GET /v1/web-visits/tracker response now includes four new fields:data_processed,last_event_received_at,status, andvisiting_companies.
- 🆕 [New] [MCP]Theget_industriestool is now available, letting AI assistants retrieve the list of supported industries.
- 🆕 [New] [MCP]Theget_cookie_consent_settings,get_data_processing_settings,update_cookie_consent_settingsandupdate_data_processing_settingstools are now available, allowing AI assistants to retrieve and manage those account settings.
- 🆕[New]Added POST /v1/icps and POST /v1/buyer-personas to create ICPs and buyer personas; PATCH and DELETE to update and delete them.
- 🆕[New]Added GET /v1/countries and GET /v1/geo-suggestions for reference data and location suggestions.
- 🆕[New]Added POST /v1/icps/companies to retrieve companies matching your ICP, and POST /v1/lists/companies and POST /v1/lists/contacts to browse your saved lists.
- 🆕[New]Added bulk tagging: POST /v1/tags/batch-add-tags-jobs and POST /v1/tags/batch-remove-tags-jobs, with GET .../{job_id} to check job status.
All above operations are supported on the MCP Server - Tools
🆕 [New]
Added OAuth 2.0 authentication
alongside API keys. Register an OAuth application in Settings > Company > Developer Access > Applications, and each user authorises it with their own Leadfeeder account. Find more details here Newimproved
Leadfeeder API - 2026-08-18
- 🆕[New]Added an app_url field to company schema - CompanyV1. This is an example of the returned valuehttps://app.leadfeeder.com/h/company/129011.
- ⚡[Improved]Theunknown_departmentvalue has been removed from the departments filter parameter and from departments response fields across the contacts search, contacts list, single contact, and list batch-add/remove-job endpoints — sending or expecting this value will no longer be accepted or returned.
- ⚡[Improved]Theunknown_hierarchyvalue has been removed from thehierarchy_levelsfilter parameter and from the hierarchy_level response field across the contacts search , contacts list , single contac, and list batch-add/remove-job endpoints — sending or expecting this value will no longer be accepted or returned.
- ⚡[Improved] [MCP]Theunknown_departmentvalue has been removed from the departments filter enum insearch_contacts,create_batch_add_to_list_job, andcreate_batch_remove_from_list_job; any saved prompt or automation passing that value will now be rejected.
- ⚡[Improved] [MCP]Theunknown_hierarchyvalue has been removed from the hierarchy levels filter enum insearch_contacts,create_batch_add_to_list_job, andcreate_batch_remove_from_list_job; any saved prompt or automation passing that value will now be rejected.
Load More
→