July 2022 Release Notes (v19.0)
| Release Name | Dataset Version | Publish Date |
|---|---|---|
| July 2022 | v19.0 | 07/05/2022 |
Person v19.0 was released on 7/5/2022.
Welcome to our July 2022 release notes! We’re rolling out some exciting updates with this release.
Here are some of the key highlights:
- Our highly requested Sandbox APIs for Person endpoints are just around the corner!
- Two new APIs to help make better queries: the Job Title and Skill Enrichment APIs!
- We’re expanding our Company data with detailed ticker and inferred revenue fields!
- Python, Ruby, and Go SDKs for our awesome developers are now available!
- We now support rollover credits for our self-serve customers!
- Over 175 million jobs and 156 million locations have been updated this past quarter and huge boosts to our coverage of O*NET codes and company tickers!
Excited yet? Read on to learn more, or jump to a specific section using the table of contents below.
❗️DEPRECATION NOTICE – Rate Limiting and Credit Usage Headers
As of the July 2022 (v19) release, PDL has updated the functionality of the header response fields to improve the alignment between the values returned by header fields and the values reflected in the API dashboard. See the Usage and Rate Limiting page for additional information.
O*NET Field Name Updates (Person Schema)
In this release, we changed the name of the job_onet_title field to job_onet_specific_occupation_detail. There is no change to the content that is provided through this field, but we wanted to provide a clearer name for the field.
| Field Name | Field Type | Field Description | Example |
|---|---|---|---|
job_onet_specific_occupation_detail | String | A more detailed job title for records where the specific occupation within O*NET's standard hierarchy isn't granular enough to accurately describe the job title. (e.g. The highest level of granularity for c-suite positions is Chief Executives.) | "Chief Technology Officer" |
We are adding the inferred_revenue field in our Company Enrichment and Company Search APIs. The inferred revenue field presents an estimated range of annual revenue on over 5 million company profiles, and can be used as a filter in any Company Search queries. The enumerated set of possible values for this field are documented here: Inferred Revenue Ranges.
The inferred_revenue field will be available through our Company Segmentation and Sales Opportunity Sourcing bundles.
| Field Name | Field Type | Field Description | Example |
|---|---|---|---|
inferred_revenue | Enum (String) | Company's estimated annual revenue, in U.S. dollars. See Inferred Revenue Ranges. | 10,000,000-25,000,000 |
Company Stock Exchanges and Sectors (Company Schema)
We are adding 21,000 additional tickers to our company dataset. We are also adding two new fields: mic_exchange and gics_sector. These fields will be available through our base company bundle. Canonicalized values for these fields can be found here: MIC Codes, GICS Sectors.
| Field Name | Field Type | Field Description | Example |
|---|---|---|---|
mic_exchange | Enum (String) | MIC code for the stock exchange the ticker is listed on. See MIC Codes. | xnms |
gics_sector | Enum (String) | GICS standard sector classification for public companies. See GICS Sectors. | technology |
This quarter we released the new Skill Enrichment API, which takes a single skill, runs through our skill cleaner, and returns a match from our skill index with additional information about the skill. The skills reflect the values returned in our Person Data’s skill field.
By using this endpoint with the Person Search API, users can search with less context provided. For example, instead of searching for "Engineers who know spark, mapreduce, or hadoop" a user could effectively search for "Engineers who know spark or similar skills.”
We have provided free credits to our enterprise Person Search API customers. If you’d like access, please reach out to us.
This quarter we also released the new Job Title Enrichment API, which takes a single job title, runs through our job cleaner, and returns a match from our job index with additional information about the job title. The job titles reflect the values returned in our Person Data’s job_title field.
By using this endpoint with the Person Search API, users can search with less context provided. For example, instead of searching for "chief financial officers, interim chief financial officers, or financial consultants" a user could effectively search for "chief financial officers or similar jobs with similar skills.”
We have provided free credits to our enterprise Person Search API customers. If you’d like access, please reach out to us.
We are excited to announce the launch of our suite of Sandbox API endpoints, which will begin rolling out over the upcoming weeks. These endpoints allow users to query PDL APIs for synthetic data without consuming paid credits, and are primarily aimed at testing and evaluation use cases to support users interested in:
- Performing integration testing to ensure compatibility with our endpoints and data structures
- Evaluating PDL endpoints without revealing proprietary or regulated data
The Sandbox API endpoints mirror our production endpoints, meaning that each public API endpoint will have a corresponding sandbox endpoint. For example, the public Person Enrichment API (api.peopledatalabs.com/v5/person/enrich) will have a corresponding Sandbox Person Enrichment API (sandbox.api.peopledatalabs.com/v5/person/enrich). This quarter we are launching sandbox APIs for our Person endpoints (i.e. enrich/bulk, search, retrieve, and identify) with support for Company endpoints coming in future releases.
This has been one of our most upvoted feature requests, so we are very excited to be able to begin rolling this out to our users. For this initial launch, our active enterprise customers will be the first users able to access the Sandbox API endpoints. We hope to gather feedback during this time in order to iterate and improve this service before releasing it to our wider user base. If you would like to request access to the Sandbox APIs, please reach out to your Customer Success team.
Over the past quarter, we released 3 more developer SDKs for working with PDL APIs: in addition, our previously launched JavaScript library, we also added SDKs for:
Each of these SDKs offer language-specific utility functions and methods for working with our API endpoints, allowing users to make API queries with just a single function call. They are all designed to be extremely lightweight and easy to work with. It’s our hope that these libraries will make it easy for developers to build with.
All of these SDKs can be quickly installed using standard package management systems (e.g. pip for python, gem for ruby, get for go). Details are available on the docs pages linked above. In addition, all our libraries have been open-sourced on github, and we encourage all our users to submit issues, feature requests and pull requests. So give them a spin and share your feedback with us!
As of this past quarter, we now support rollover credits for self-serve customers allowing you to rollover credits into the next monthly or annual cycle. Rollover credits are unused plan credits from one cycle that roll into the next as long as you have a paid plan. The amount of credits you can roll over is capped at the amount of your new subscription plan. These changes accompany our subscription plan updates announced in the April 2022 Release Notes.
Note: These changes will not affect our enterprise customers.
For more information on rollover credits and subscription plan details, see our Plans and Billing page.
This quarter, we updated millions of jobs and locations in our Global Resume Dataset. See below for details:
| Dataset | Geography | Field | Records Updated |
|---|---|---|---|
| Resume | Global | experience | 175,098,318 |
| Resume | Global | location | 156,261,127 |
| Resume | United States | experience | 61,050,079 |
| Resume | United States | location | 68,027,716 |
| Linkage | Coverage in v18 | Coverage in v19 | Increase (%) |
|---|---|---|---|
total_records | 700,613,882 | 716,383,643 | 2.25% |
job_company_ticker | 20,325,049 | 44,619,675 | 119.53% |
job_onet_code | 73,052,681 | 158,251,185 | 116.63% |
job_onet_broad_occupation | 73,052,681 | 158,251,185 | 116.63% |
job_onet_major_group | 73,052,681 | 158,251,185 | 116.63% |
job_onet_minor_group | 73,052,681 | 158,251,185 | 116.63% |
job_onet_specific_occupation | 73,052,681 | 158,251,185 | 116.63% |
experience.company.ticker | 42,042,180 | 83,919,037 | 99.61% |
| Linkage | Coverage in v18 | Coverage in v19 | Increase (%) |
|---|---|---|---|
ticker | 2395 | 23287 | 872.32% |
- This quarter, we saw a significant increase in coverage for employment and company data across all datasets, of particular note:
- O*NET field coverage increased by 94 million in API Dataset as we improve the coverage of our tagging algorithm
experience.company.tickercoverage increased by 60 million in API Dataset due to increases in the number of tickers in the company dataset
- We added bulk support to the Person Retrieve API allowing users to retrieve up to 100 person records with a single API request. See the Bulk Person Retrieve API documentation for more information.
- Added typescript support to JavaScript SDK
- Made some updates to the way the Person Identify API pulls down and ranks records when a name + location are inputted to maximize the number of fuzzy results.
- Fixed an issue with records containing just a last initial not getting merged, which should lead to more complete profiles in our Person dataset
- Improved the likelihood logic by decreasing scores for enrichment and identify matches that contained conflicting names
- Added an error for people using percent signs in SQL LIKE queries while making a GET request since this can cause encoding issues. We highly recommend people use POST for the search API for this reason
- Fixed bug in company required params that only allowed AND boolean logic
- Fixed a Person Search API SQL bug where leading and trailing whitespace sometimes caused 0 results.