Highlights
Run enrichments and sources from your own applications through the API
Work that previously needed a Datablist collection can now run inside your own application or automation workflow. The new Enrichments API works on records you already have, while the Sources API generates new lists from the settings you choose. You can submit work, follow its progress, and retrieve the results as JSON without creating a Datablist collection.
For example, send company names to Company Name to Domain API and write the returned websites back to your CRM. Or use Instagram Followers/Following Scraper through the Sources API to build a list from an Instagram profile. Both use your existing Datablist credits.
Get a Personal API Key and use it directly for your requests; Datablist handles token renewal. In the documentation, Try it lets you send a request and inspect its response before writing a script. Browse the available APIs or start with the API reference.
Improvements
Target Auto-Run enrichments with AND/OR condition groups
Auto-Run conditions used to be limited to a flat set of rules. For enrichments triggered by New items or Input changes, you can now combine AND/OR conditions and nest groups, so one rule can express the rows you want to process.
For example, run Company Enrichment only when a lead’s country is France or Germany and its website is not empty. Put the two country conditions in a Match any group inside a Match all group with the website condition. Only qualifying rows run; scheduled enrichments keep their existing condition limits.
Clone collections with their saved filters
Cloning a collection used to leave its saved filters behind, so a new campaign list needed the same conditions rebuilt by hand. The clone dialog now offers Clone saved filters, enabled by default when the source has saved filters. It also works when you copy selected rows into a new collection.
For a prospect list with saved filters such as Country is France and Email is empty, keep the option enabled to carry those filters into the copy. If a filter needs an enrichment-status column you have chosen not to copy, the dialog names the missing column before you continue. You can include the matching enrichment configuration or leave that filter out.
Clear collection filters in a click
Removing an active filter from the filtering dialog used to mean editing its conditions one by one. Clear filter now removes the active conditions and returns you to the full collection in one click.
Credit usage history separates app and API consumption
Credit usage history was built around collections, which made enrichment activity started through the API hard to review. The history now has separate App usage and API usage sections, so you can see where credits were consumed without looking for a collection that does not exist.
If you enrich a lead collection in Datablist and run a separate email-finding script, open credit usage to review each activity in its own section. Both show the enrichment or source, time and credit cost, while app rows also link to their collection. Load older usage extends the shared history; the summary totals still include both kinds of consumption.
LinkedIn People Profile Scraper adds a Skills output
LinkedIn People Profile Scraper can now return the skills listed on a profile. These names were previously omitted from the enrichment result even when the profile lookup contained them. Select the Skills output and map it to a text column alongside the person’s name, role and company.
A profile listing Python and SQL can produce Python, SQL in that column, ready for filtering or review when you build a recruiting list. The field stays empty when skills are unavailable, including in older cached profiles.
LinkedIn Company Page Scraper charges the same rate for numerical URLs
A numerical LinkedIn company URL could previously cost 75 credits when the lookup needed a fallback, compared with the standard 25-credit rate. LinkedIn Company Page Scraper now uses the same standard price for named and numerical company URLs. You can use either format directly.
For a list of 500 company pages, the standard estimate is 12,500 credits whether the URLs end in company names or numerical IDs such as linkedin.com/company/1234567890. There is no need to convert numerical URLs to named ones to avoid the former surcharge.
LinkedIn Search Scraper stops charging for unrequested email lookups
LinkedIn Search Scraper can return work emails already available with the imported profiles. Those addresses could previously trigger an email-finding fee even when no separate email search had been requested. The import now keeps the address without adding that unrequested lookup charge.
Map Known Work Email when importing a LinkedIn people search if you want to keep addresses returned with those profiles. A value in that column no longer adds an email-finding fee on its own; the normal price for your selected profile-scraping mode still applies.