Feature Requests

It would be helpful if the PDL Location Data included actual store locations.

Today, PDL only provides standard access to the current release version of the Person, Company, and Job Posting datasets. This Feature Request is to add the ability to access prior release versions (e.g., for backtesting or modeling use cases).

Associate NPI numbers with person data. This enables us to search and locate a high value customer. https://npiregistry.cms.hhs.gov/search

Customers regularly have limited details about the companies they are looking to enrich, and a lot of cases, may only have a Company name. Additionally these company names can sometime be filled in by hand, and may include variations that deviate from the more common name iterations. For example, attempting to enrich the company name "monsanto chemical company", does not result in any matches, however, enriching "monsanto company" does, despite the fact the returned record includes indications of “chemical” in various fields such as the summary, naics codes, and sic codes. Given Company Enrichments that use company_name as the primary matching input attempt to use the various name fields on a company for matching, we wouldn’t expect to see the Monsanto Company matched for "monsanto chemical company". However, if additional context was used for company_name based enrichment, it would be reasonable to return the Monsanto company for "monsanto chemical company". The request is we utilize more than just the various company name fields (i.e. descriptive fields like summary, and industry codes) to help facilitate a higher match rate when matching off of company_name.

Track deadlines associated with job postings (common with internships)

I would like to filter job postings to full-time, part-time, contract, etc.

Add additional coverage to the Person Dataset that includes healthcare workers.

I've been working with teams that handle digital nomad tax accountant services ( https://pearllemonaccountants.com/accountants-for-digital-nomads/ ), and one thing that keeps coming up is the challenge of identifying reliable cross-border employment and location data. It would be really useful if the platform could expose more structured signals around international work history, remote employment patterns, and location changes where appropriate. That kind of enrichment could make compliance and verification workflows much more efficient for businesses operating globally. I know data accuracy and privacy have to come first, so I'm not suggesting anything overly broad. Even incremental improvements to available metadata or optional enrichment fields would help organizations that need to understand distributed workforces without relying on multiple external sources. Having those insights in a consistent format would reduce manual effort and improve confidence in downstream processes. Overall, it's great to see the roadmap continue expanding based on community feedback. A feature like this could benefit not only tax and compliance use cases but also HR, recruiting, and workforce analytics teams that regularly deal with international professionals and remote-first organizations.

When working with large datasets and customer records, I've noticed that teams often focus heavily on APIs and data workflows while overlooking the day-to-day experience of the people behind the screens. Something as simple as coordinating lunch during long planning sessions can become a distraction, which is why having a dependable office catering company ( https://pearllemoncatering.com/ ) has actually made our internal collaboration smoother. It sounds unrelated at first, but removing small operational headaches gives product, engineering, and data teams more uninterrupted time to focus on testing, reviewing feedback, and shipping improvements. One thing I appreciate about platforms like this is how much community feedback influences the roadmap. It's useful to see feature requests grouped, discussed, and updated instead of disappearing into a support inbox. As someone who regularly works alongside developers and product managers, that transparency helps set realistic expectations and encourages more thoughtful suggestions rather than duplicate requests. The voting system also makes it easier to understand what other users are struggling with before creating a new post. I'd also love to see continued attention given to usability alongside new data capabilities. Even small interface improvements can save a surprising amount of time for teams that spend hours reviewing results or validating records. When a platform keeps balancing powerful functionality with practical user experience, it tends to become much easier for both technical and non-technical stakeholders to adopt. Looking forward to seeing how the roadmap develops over the coming months.

supporting API that returns the current dataset version and its release date and/or accepts an optional parameter for dataset_version to see when previous versions were released programmatically