Skip to main content
Welcome to our September 2026 release notes! Back to school season is here, and we’ve got an exciting batch of updates to share for show-and-tell this month: improved salary and compensation data, a new sandbox endpoint for the Job Posting API, improved deduplication, and expanded Job Posting and Technology Data coverage. Check it out:

✨ Release Updates

Inferred Salary Improvements

Person Data GA ✨ Product Update 📐 Schema Change What’s New? We’ve improved how our inferred_salary field is calculated and added three new fields to provide a more precise and transparent view of estimated compensation. Our updated methodology now incorporates compensation signals from real-world job posts, accounting for factors such as role, seniority, company, geography, and recency. Alongside the existing inferred_salary field, we have also added the following fields: New Inferred Salary Fields These fields offer a more granular estimated range and additional context about the strength of each salary estimate.
The canonical values for the inferred_salary field are not changing. We are only improving the methodology used to assign those canonical salary buckets to each record.
Example
Why It Matters These improvements make Inferred Salary data more useful across a wider range of compensation, targeting, and analytics workflows. With these updates, you can expect:
  • More accurate salary estimates across international markets
  • Greater granularity for compensation above $250k
  • Broader coverage
  • More precise estimated salary ranges
  • A confidence indicator to help evaluate each estimate
By incorporating real-world compensation signals from our Job Posting Dataset, our salary estimates now better reflect current market compensation across roles, companies and geographies. Availability The new fields are included in the premium Inferred Salary field bundle, alongside the existing inferred_salary field. Customers who already have access to this bundle will automatically receive the new fields in their upcoming deliveries. If you’re an enterprise customer and would like access to these fields, please reach out to your Customer Success team. Self-serve customers can add the bundle to their subscription through the API Dashboard under Plans & Billing > Subscriptions > Manage. Additional Resources

Job Posting Sandbox API

Job Posting Data GA ✨ Product Update What’s New? This month, we released a new Sandbox endpoint for our Job Posting Search API; you can now test and build with the Job Posting Search API for free using our new Sandbox endpoint. The Sandbox Job Posting Search API mirrors the functionality of the production API, but runs against a sample of real Job Posting data and does not consume credits. This offers a risk-free environment to test queries, build integrations, and prototype workflows before moving to production. Overview Endpoint: https://sandbox.api.peopledatalabs.com/v5/job_posting/search The Sandbox endpoint supports the same input parameters and returns the same JSON response structure as the production Job Posting Search API. The underlying Sandbox dataset contains a sample of 5,000 real Job Posting records and is refreshed monthly, providing enough data to test workflows including filtering, pagination, and aggregations. Why It Matters Previously, testing the Job Posting Search API required access to production credits. With the new Sandbox endpoint, you can:
  • Build and test integrations and workflows without consuming credits
  • Experiment with search queries before using them in production
  • Test filtering, pagination, and aggregation workflows against real Job Posting Data
  • Evaluate Job Posting Data without needing test credits provisioned first
Because the Sandbox uses real Job Posting records, you can also evaluate the structure of the underlying data using representative samples.
Sandbox Dataset LimitationsThe Sandbox endpoint uses a small curated dataset of 5,000 job posts and is only updated monthly.Therefore, the Sandbox API is not reflective of the coverage and freshness of the production Job Posting Search API. Instead, this endpoint is intended to provide a free way to test functionality and workflows using the endpoint.If you would like to evaluate the production Job Posting Search API, please reach out to us.
Availability The Sandbox endpoint for our Job Posting Search API is available across all plans and does not consume API credits. To access the Sandbox API, simply query the endpoint with your PDL API key. If you do not have an API key, you can sign up for a free one through our self-serve portal. Getting Started To immediately start sending test queries, check out this quick copy-and-paste code example: Sandbox Example For more test queries to try out, you can also run any of the code samples in the Job Posting Search API Examples page. Simply replace the production Job Posting Search API endpoint in those examples with the sandbox endpoint: To run any Job Posting Search API example with the Sandbox Endpoint:

🚀 Data Updates

Freshness

The number of resume experiences and locations verified in our datasets (based on the job_last_verified and location_last_updated fields). Monthly (v35.1 → v35.2) 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 the job_last_changed field). Monthly (v35.1 → v35.2) Job changes detected over the past month.

🌐 Coverage

Monthly Highlights (v35.1 → v35.2)

Resume Dataset

Full Dataset

Company Dataset

Job Posting Dataset

Technology Data

Commentary

  • Person Data
  • Company Data
  • Job Posting Data
    • Job Posting Dataset coverage continued to expand with 6% more unique companies and 12% more active postings this month
  • Technology Data
    • Total technology mentions increased by 6%, while the number of unique Company<>Technology linkages increased by 3.7%
    • We also observed Technology Data across 4.6% more companies this month

🛠 Improvements and Bug Fixes

Improvements

  • Person Record Deduplication
    • We reduced the number of duplicate LinkedIn profiles by 65% by filtering sparse records that duplicate more complete profiles. This removed approximately 40M records from the full dataset (see commentary above).
    • These improvements primarily target the full Person Dataset, and do not impact our resume or other datasets.
    • Customers using the full Person Dataset may see a decrease in the total number of records. Customers using the person changelog will see a temporary spike in the number of records marked as deleted this month.
  • GitHub URL Validation
    • The github_url field on person records now only contains URLs that return a 200 status. URLs returning a 404 are retained in the profiles array, but will no longer appear as the top-level github_url.
  • Improved Company Location Coverage
    • We expanded our company location sourcing to increase our coverage of locations across records in our Company Dataset.Company Location Coverage