April 2022 Release Notes - People Data Labs Documentation

Release Name	Dataset Version	Publish Date
April 2022	`v18.0`	03/29/2022

Person v18.0 was released on 3/29/2022 and Data License deliveries will begin on 4/4/2022. Welcome to our April 2022 release notes! One quarter into the new year and we have a ton of exciting updates to share! Here are some of the key highlights:

The long-awaited field updates: O*NET Title Tags and NAICS/SIC Industry codes are finally here!
Person Retrieve API now supports new workflows for maintaining fresh data!
New Javascript SDK for all our awesome JS devs out there!
Two exciting new integrations: Snowflake and Make (formerly Integromat)
An early preview of some upcoming improvements to our self-serve subscription plans
Over 228 million jobs and 209 million locations have been updated this past quarter and tons of new linkages between emails and contact information!

Excited yet? Read on to learn more, or jump to a specific section using the table of contents below.

📣 Key Announcements

Deprecations

❗️DEPRECATION NOTICE – Rate Limiting and Credit Usage Headers

In the next quarterly release (v19 - July 2022), PDL will be deprecating the current functionality of the header response fields . Instead, the headers will be updated (as shown below) in order to improve the alignment between the values returned by header fields and the values reflected in the API dashboard. The updated schema will be as follows:

{  
  "x-ratelimit-reset": 2022-02-23T20:19:55Z, \# Flask  
  "x-ratelimit-remaining": {  
    'minute': 1200,  
    'day': 12000,  
    'month': 120000  
  } \# Flask  
  "x-ratelimit-limit": {  
    'minute': 1201,  
    'day': 12001,  
    'month': 120001  
  }  
  "x-lifetime-used": 984152,  
  "x-totallimit-remaining": 1342,  
  “x-totallimit-spent”: 1,  
  "x-totallimit-purchased-remaining": 342,  
  "x-totallimit-overages-remaining": 1000,  
}  

Header Field	Description	Example
`x-ratelimit-reset`	The UTC timestamp at which the rate limit will reset	`2022-02-23T20:19:55Z,`
`x-ratelimit-remaining`	A collection of fields describing the number of credits remaining over a subsequent time period based on the rate limit
`x-ratelimit-remaining.minute`	The number of credits available to be used in the next minute	1200
`x-ratelimit-remaining.day`	The number of credits available to be used in the next day	12000
`x-ratelimit-remaining.month`	The number of credits available to be used in the next month	120000
`x-ratelimit-limit`	A collection of fields describing the maximum number of credits that can be used in a given time period
`x-ratelimit-limit.minute`	The maximum number of credits that can be used in a minute	1201
`x-ratelimit-limit.day`	The maximum number of credits that can be used in a day	12001
`x-ratelimit-limit.month`	The maximum number of credits that can be used in a month	120001
`x-lifetime-used`	The total number of credits that have been used over an account’s lifetime	`984152`
`x-totallimit-remaining`	The total number of credits available to consume (purchased + overages)	`1342`
`x-totallimit-spent`	Number of credits billed for this call.	`1`
`x-totallimit-purchased-remaining`	The number of purchased credits remaining	`342`
`x-totallimit-overages-remaining`	The number of overage credits remaining	`1000`

Please reach out to your Customer Success Team if you have any questions or concerns about migrating to the new headers.

Schema Changes

In this release, PDL is officially introducing support for 2 industry-standard codes:

O*NET Occupational Codes
NAICS / SIC Industry Classification Codes

Support for these standards has been heavily requested, and we are very excited to begin the rollout of these fields! The schema additions are below, and check out the Field Updates section below for more details as well as information on how to access these new data fields.

O*NET Occupation Codes (Person Schema)

Field Name	Field Type	Field Description	Example
`job_onet_code`	`String`	The 6-digit O*NET code for a person’s current job title, following the 2018 SOC guidelines.	”11-1011.00”
`job_onet_major_group`	`String`	The O*NET Major Group associated with a person’s current job title.	”Management Occupations”
`job_onet_minor_group`	`String`	The O*NET Minor Group associated with a person’s current job title.	“Top Executives”
`job_onet_broad_occupation`	`String`	The O*NET Broad Occupation category associated with a person’s current job title.	“Chief Executives”
`job_onet_specific_occupation`	`String`	The O*NET Detailed Occupation category associated with a person’s current job title.	“Chief Executives”
`job_onet_title`	`String`	An O*NET Alternative Title associated with a person’s current job title.	“Chief Technology Officer”

NAICS / SIC Industry Classification Codes (Company Schema)

Field Name	Field Type	Field Description	Example
`naics`	`Object`	An object containing the NAICS industry information associated with a company
`naics.naics_code`	`String`	The NAICS code associated with a company’s industry classification	“111110”
`naics.sector`	`String`	The NAICS sector associated with a company’s industry classification	“agriculture, forestry, fishing and hunting”
`naics.sub_sector`	`String`	The NAICS subsector associated with a company’s industry classification	“crop production”
`naics.industry_group`	`String`	The NAICS industry group associated with a company’s industry classification	“oilseed and grain farming”
`naics.naics_industry`	`String`	The NAICS industry associated with a company’s industry classification	“soybean farming”
`naics.national_industry`	`String`	The NAICS national industry associated with a company’s industry classification	“soybean farming”
`sic`	`Object`	An object containing the SIC industry information associated with a company
`sic.sic_code`	`String`	The SIC industry code associated with a company’s industry classification	“5731”
`sic.major_group`	`String`	The SIC major group associated with a company’s industry classification	“agricultural production - crops”
`sic.industry_group`	`String`	The SIC industry group associated with a company’s industry classification	“cash grains”
`sic.industry_sector`	`String`	The SIC industry sector associated with a company’s industry classification	“soybeans”

✨ New Products and Features

Field Updates

The v18 (April 2022) quarterly release, we are officially introducing support for 2 heavily requested industry-standard codes to our data:

O*NET Occupation Codes (supporting the O*NET v26.0 standard) have been added to our Person Schema as a new premium field bundle.
NAICS/SIC Industry Classification Codes have been added to our Company Schema as Base Company Fields.

O*NET Job Title Codes

Six new ONET-related fields have been added to our Person Schema to support the industry standard for job role tagging. In this initial rollout, we have tagged a subset of the primary job objects across our resume records (meaning no ONET coverage for historical job titles just yet). In the coming data releases, we will be launching improvements to this field to build increasing coverage across every O*NET code. The O*NET additions broaden the set of title classifications we have for our employment data (expanding on our current job_role and job_sub_role fields) and to better support customers building on top of census data. The O*NET fields are available as a premium field bundle that can be added to any person data package to provide additional information on the existing primary job title. See the updated schema here. To learn more about our new O*NET fields or to request access please reach out to your Customer Success team.

NAICS/SICS

To support more granular industry classification for companies in our Company Data, we have introduced NAICS and SIC code. These fields will provide additional segmentation power and value to the PDL company data. Additionally, fields have been added to our Base Company Fields, meaning that they are freely available by default to any customer. The Company Search API can also be leveraged to access NAICS and SIC codes, so users can filter and target companies in their search queries. You can view the schema for these fields here. We encourage all our users to assess these new fields and share any feedback regarding quality and usefulness, you may have with your client team. This is just the beginning and we will continue to iterate and improve on these fields moving forward.

Person Retrieve API Credit Usage Updates

The Person Retrieve API has been updated such that credits will now only be consumed when the API returns a record that has an update since the last time you called it. As a refresher, the Person Retrieve API is billed against your existing pool of person enrichment credits and allows you to pull down a record using a PDL ID as input.
With this update, the Person Retrieve API can now be leveraged to refresh a record using the persistent PDL ID since the last time a user retrieved it via any API endpoint. PDL is currently updating ~100 million records with each monthly API rebuild, so this is a great way for customers to keep specific batches of profiles as fresh as possible.

JavaScript SDK

This past quarter, we released our first developer SDK! The peopledatalabs-js package is a streamlined PDL client to support our API users working with JavaScript. This library supports all of our current API endpoints and allows you to make API requests with just a single function call. We also wrote it using plain vanilla JS, meaning you can use this client for both code that runs in the browser as well as backend server code. This package can be downloaded and installed from the npm package repository or directly cloned from its public github repository. We made this library open source and we encourage anyone to submit issues, feature requests and pull requests. In the future, more SDKs will be released so please share any feedback you have with us!

Integrations

This past quarter, we officially launched 2 new integrations as well:

Snowflake
Make (formerly Integromat)

Snowflake Integration

PDL is now live in the Snowflake Data Marketplace! Customers can request to subscribe to our Person Dataset and openly access our free company dataset via Snowflake. This integration allows us to deliver data directly to Data License customers, and requires minimal additional setup for customers already using Snowflake for other purposes. If you are interested in our snowflake integration, you can request access by searching for PDL in the Snowflake Data Marketplace or by speaking to your Customer Success team. We hope to build more integrations like these in the future, so please share any feedback you have with us as you test it out!

Make Integration

A new integration with Make (formerly Integromat) is now live! Make is a workflow automation tool that allows you to connect various apps together and seamlessly pass data between them. It is a no-code solution that allows you to build complex logic and pipelines for coordinating your apps and services together. Person and Company data can now be added directly into your automated workflows. Sign up for access to our integration here, and as always, please share any feedback you have with us!

Upcoming Subscription Plan Updates

In the next few weeks, we will be rolling out several updates to our subscription plans for self-serve customers. As a preview, these changes will include:

Standardized pricing tiers across our products
An updated freemium tier with a renewing monthly allotment of free credits
The option to purchase annual subscriptions
Streamlined processes for upgrading and downgrading subscriptions

We are excited about these improvements for our self-serve customers, so stay tuned for an official announcement via email soon!

🚀 Data Updates

Freshness

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`	228,256,002
Resume	Global	`location`	209,846,161
Resume	United States	`experience`	76,269,414
Resume	United States	`location`	84,521,983

Coverage

Resume Dataset

Linkage	Coverage in v17	Coverage in v18	Increase (%)
`total_records`	684,434,661	700,613,882	2.36%
`birth_year`	8,478,127	10,254,962	20.96%
`job_company_ticker`	18,109,504	20,325,049	12.23%
`street_addresses`	25,582,324	28,318,775	10.70%
`job_company_website`	202,077,270	221,853,296	9.79%

API Dataset

Linkage	Coverage in v17	Coverage in v18	Increase (%)
`total_records`	3,026,851,628	3,110,029,187	2.75%
`personal_emails`	586,232,294	661,722,011	12.88%
`street_addresses`	679,766,613	763,341,777	12.29%
`job_company_ticker`	20,278,340	22,696,445	11.92%

Email Dataset

Linkage	Coverage in v17	Coverage in v18	Increase (%)
`total_records`	687,784,131	774,399,256	12.59%
`street_addresses`	248,611,221	348,804,217	40.30%
`personal_emails`	479,704,633	565,117,411	17.81%
`mobile_phone`	28,569,823	33,367,435	16.79%
`birth_date`	66,094,400	76,527,251	15.78%
`gender`	534,231,011	606,542,899	13.54%
`full_name`	687,784,131	774,399,256	12.59%

Commentary

Strong improvements to linkages in our Email slice, in particular:
- Email <> street_addresses linkages increased by 40.3%
- Email <> mobile_phone linkages increased by 16.8%
- Email <> full_name linkages increased by 12.6%
11.9% increase in job_company_tickers across our entire dataset
Significant bump in street_address coverage across the board including a 17.1% increase in street_address <> job_title linkages and 9.1% increase in street_address <> linkedin_url linkages
The Person Dataset saw a 7.1% increase in coverage for birth_year

🛠 Improvements and Bug Fixes

Improvements

Support for POST requests was added to our Person and Company Search APIs, allowing users to send large queries within their API requests. See examples requests here: person search example, company search example
The limit for the number of ‘terms’ in input queries increased from 100 elements to 1,000 for all Person and Company Search APIs.
job_title matching was added to the Identify API, and is now supported as an input parameter.
The criteria for cleaning emails was relaxed in our dataset for increased coverage of temporary email domains to support fraud use cases.
The error response codes for the Bulk Enrichment API were improved for individual errors within a bulk enrichment request. The API will now always return a status code 200, with 400 errors nested appropriately within the response object

Bug Fixes

Within the Company Search API, a bug that was preventing insights fields from being searchable
The Bulk Enrichment API no longer drops invalid input parameters and instead returns 400 status codes nested within the response object.
The Identify API will return an error code 400 when there are no inputs provided.
Error 400 codes are returned in the School and Company cleaners when invalid input parameters are sent.

​📣 Key Announcements

​Deprecations

​❗️DEPRECATION NOTICE – Rate Limiting and Credit Usage Headers

​Schema Changes

​O*NET Occupation Codes (Person Schema)

​NAICS / SIC Industry Classification Codes (Company Schema)

​✨ New Products and Features

​Field Updates

​O*NET Job Title Codes

​NAICS/SICS

​Person Retrieve API Credit Usage Updates

​JavaScript SDK

​Integrations

​Snowflake Integration

​Make Integration

​Upcoming Subscription Plan Updates

​🚀 Data Updates

​Freshness

​Coverage

​Commentary

​🛠 Improvements and Bug Fixes

​Improvements

​Bug Fixes