Welcome to our November 2025 release notes!
Check out the updates below to stay up to date!
Here’s what’s new:
- 📊 Freshness Updates: This past quarter, we verified 278M+ jobs and tracked 723K+ job changes across our global dataset
- Improved Company Facebook / Meta Profile Resolution: We split Facebook & Meta into two distinct company profiles
- Email Deliverability Improvements: Continued work to lower bounce rates and improve match rates for our top-level emails
Breaking Changes (Going Live This Month)
Final Sunset: Query Builder & API Explorer Tools
Deprecation Date: November 2025 (v32.1) Impacted Product: API Dashboard Tools Being Removed- Query Builder Tool
- API Explorer Tool
- Lets you build requests and view live data directly in your dashboard
- Replaces the functionality of the API Explorer Tool without having to leave the API Dashboard
- November 30, 2025 - Legacy tools fully removed
- July–November 2025 - Legacy tools and API Playground both available
- July 2025 - API Playground available in your API Dashboard
- Recreate any workflows you currently run in the Query Builder by writing SQL or Elasticsearch queries in the new API Playground
- Continue using the API Playground now to prepare for the upcoming deprecations
New Products and Features
Email Deliverability Improvements (Person)
Email Deliverability GuideFor an in-depth guide on these changes and how to take advantage of these improvements, please see this customer guide prepared by our Solutions Engineering Team:Email Deliverability Improvements
recommended_personal_email and work_email).
Non-deliverable emails have been removed from these two top-level fields. Removed emails will still remain in the emails array, and we will begin backfilling our top-level fields with new validated emails.
What’s Next
These improvements will continue over the coming months with the goal of significantly enhancing deliverability and maintaining ongoing validation.
Have feedback or ideas? Share them on our roadmap board! We’d love your input, especially on proposed additions like email validation status metadata to the Person Schema.
Improved Facebook / Meta Profile Resolution (Company)
What’s New This release splits Facebook and Meta into separate company profiles and work experience. Previously, we had logic to combine these together as a single entity, and this change standardizes the logic to be consistent with that used for other corporate entity relationships (e.g., Google and Alphabet). Meta Example RecordJSON
JSON
Data Updates
Freshness
Monthly (v32.0 → v32.1) Freshness updates over the past month.Job Changes
The number of person records where the primary job experience changed in our Person Dataset (based on thejob_last_changed field).
Monthly (v31.2 → v32.0)
Freshness updates over the past month.
Coverage
Monthly (v32.0 → v32.1) Resume Dataset
API Dataset
Email Dataset
Mobile Phone Dataset
Company Dataset
Job Posting Dataset
Commentary
- Person
- We began receiving Linkedin ID from one of our sources, contributing to the increase in fill rates for
profiles.idandlinkedin_id.
- We began receiving Linkedin ID from one of our sources, contributing to the increase in fill rates for
Improvements and Bug Fixes
Improvements
- Reduce Count of “Escape Characters” in Company Names
- We’ve identified and removed ~16k (>90%) escape characters from company names. Due to some nuances in how we build our company data, there are still some that remain, but we suspect that active projects this quarter may be able to remove these entirely.
Bug Fixes
- Fix Location Selection Logic
- We fixed an issue in our location selection logic that was causing a previous location to be selected for some records.
- LIMIT in SQL queries
- If a LIMIT clause was used in a Person or Company Search SQL query it was unintentionally overriding the
sizeparameter in some circumstances. It now throws a 400 error as expected.
- If a LIMIT clause was used in a Person or Company Search SQL query it was unintentionally overriding the
