Person Schema

A breakdown of the person-related fields we offer

Overview

This page details the Person Data that we provide through our Person APIs, such as Person Enrichment and Person Search.

Identifiers

first_name
DESCRIPTION The person's first name.
DATA TYPE String
FIELD DETAILS

The person's first name.

EXAMPLE
"name": "sean"
full_name
DESCRIPTION The person's full name.
DATA TYPE String
FIELD DETAILS

The first and the last name fields appended with a space.

EXAMPLE
"surname": "thorne"
id
DESCRIPTION A unique persistent identifier for the person.
DATA TYPE String
FIELD DETAILS

The ID is a unique, persistent, and hashed value that represents a specific person.

IDs have a max length of 64 characters, although in practice we expect IDs to be closer to 32 characters in length.

EXAMPLE
"id": "qEnOZ5Oh0poWnQ1luFBfVw_0000"
Contact Information
linkedin
DESCRIPTION The person's linkedin Id
DATA TYPE String (LinkedIn)
FIELD DETAILS

The linkedin field is generated from a unique identifier for a LinkedIn profile.

EXAMPLE
"linkedin": "obert-mufunda-973b5290"
twitter
DESCRIPTION The person's X account profile Id.
DATA TYPE String (twitter)
FIELD DETAILS

The twitter field is generated from a unique identifier for an X profile.

EXAMPLE
"twitter": "obert-mufunda"
personal_emails

DESCRIPTION All personal emails associated with the person.
DATA TYPE Array [String]
FIELD DETAILS

The list of all emails tagged as type = personal.

EXAMPLE
"personal_emails": [ "[email protected]" ]
phone_numbers
DESCRIPTION All phone numbers associated with the person.
DATA TYPE Array [String (Phone)]
FIELD DETAILS

For more detailed metadata on individual phone numbers, see the phones field.

EXAMPLE
"phone_numbers": [ "+15558675309" ]
phones
DESCRIPTION The list of phone numbers associated with this record with additional metadata.
DATA TYPE Array [Object]
FIELD DETAILS

Each phone number object in this list will contain the following information.

FIELD DATA TYPE DESCRIPTION
first_seen String (Date) The date that this number was first associated with this record.
last_seen String (Date) The date that this number was last associated with this record.
num_sources Integer (> 0) The number of sources that have contributed to the association of this profile with this record.
number String (Phone) The phone number.
EXAMPLE
"phones": [ { "number": "+15558675309", "first_seen": "2017-06-02", "last_seen": "2019-07-18", "num_sources": 17 } ]
recommended_personal_email
DESCRIPTION The best available email to reach a person.
DATA TYPE String
FIELD DETAILS

This field is generated by analyzing the all of a person's emails in the personal_emails list to identify the best available email.

Through testing, we’ve found that using the email identified in recommended_personal_email versus selecting a random email address from personal_emails resulted in ~37% higher deliverability.

EXAMPLE
"recommended_personal_email": "[email protected]"
work_email
DESCRIPTION The person's current work email.
DATA TYPE String
FIELD DETAILS

The value for this field must use valid email address formatting.

EXAMPLE
"work_email": "[email protected]"
Current Company

These fields describe the company the person currently works at. These fields will match the corresponding values in our Company Schema and will use the same formatting and parsing logic.

job_company_facebook_url
DESCRIPTION The person's current company's Facebook URL.
DATA TYPE String
EXAMPLE
"job_company_facebook_url": "facebook.com/peopledatalabs"
job_company_founded
DESCRIPTION The person's current company's founding year.
DATA TYPE Integer (> 0)
EXAMPLE
"job_company_founded": 2015
job_company_id
DESCRIPTION The person's current company's PDL ID.
DATA TYPE String
EXAMPLE
"job_company_id": "peopledatalabs"
job_company_industry
DESCRIPTION The person's current company's industry.
DATA TYPE Enum (String)
EXAMPLE
"job_company_industry": "computer software"
job_company_linkedin_id
DESCRIPTION The person's current company's LinkedIn ID.
DATA TYPE String
EXAMPLE
"job_company_linkedin_id": "18170482"
job_company_linkedin_url
DESCRIPTION The person's current company's LinkedIn URL.
DATA TYPE String
EXAMPLE
"job_company_linkedin_url": "linkedin.com/company/peopledatalabs"
job_company_location_address_line_2
DESCRIPTION The person's current company's headquarters' street address line 2.
DATA TYPE String
EXAMPLE
"job_company_location_address_line_2": "suite 1670"
job_company_location_continent
DESCRIPTION The person's current company's headquarters' continent.
DATA TYPE Enum (String)
EXAMPLE
"job_company_location_continent": "north america"
job_company_location_country
DESCRIPTION The person's current company's headquarters' country.
DATA TYPE Enum (String)
EXAMPLE
"job_company_location_country": "united states"
job_company_location_geo
DESCRIPTION The person's current company's headquarters' city-center geographic coordinates.
DATA TYPE String
EXAMPLE
"job_company_location_geo": "37.77,-122.41"
job_company_location_locality
DESCRIPTION The person's current company's headquarters' locality.
DATA TYPE String
EXAMPLE
"job_company_location_locality": "san francisco"
job_company_location_metro
DESCRIPTION The person's current company's headquarters' metro area.
DATA TYPE Enum (String)
EXAMPLE
"job_company_location_metro": "san francisco, california"
job_company_location_name
DESCRIPTION The person's current company's headquarters' location name.
DATA TYPE String
EXAMPLE
"job_company_location_name": "san francisco, california, united states"
job_company_location_postal_code
DESCRIPTION The person's current company's headquarters' postal code.
DATA TYPE String
EXAMPLE
"job_company_location_postal_code": "94105"
job_company_location_region
DESCRIPTION The person's current company's headquarters' region.
DATA TYPE String
EXAMPLE
"job_company_location_region": "california"
job_company_location_street_address
DESCRIPTION The person's current company's headquarters' street address.
DATA TYPE String
EXAMPLE
"job_company_location_street_address": "455 market st"
job_company_name
DESCRIPTION The person's current company's name.
DATA TYPE String
EXAMPLE
"job_company_name": "people data labs"
job_company_size
DESCRIPTION The person's current company's size range.
DATA TYPE Enum (String)
EXAMPLE
"job_company_size": "51-200"
job_company_ticker
DESCRIPTION The person's current company's ticker.
DATA TYPE String
EXAMPLE
"job_company_ticker": "goog"
job_company_twitter_url
DESCRIPTION The person's current company's Twitter URL.
DATA TYPE String
EXAMPLE
"job_company_twitter_url": "twitter.com/peopledatalabs"
job_company_type
DESCRIPTION The person's current company's type.
DATA TYPE Enum (String)
EXAMPLE
"job_company_type": "public"
job_company_website
DESCRIPTION The person's current company's website.
DATA TYPE String
EXAMPLE
"job_company_website": "peopledatalabs.com"
Current Job

These fields describe the person's most recent work experience.

inferred_salary
DESCRIPTION The inferred salary range (USD) for the person's current job.
DATA TYPE Enum (String)
FIELD DETAILS

Must be one of our Canonical Inferred Salary Ranges.

EXAMPLE
"inferred_salary": "70,000-85,000"
job_last_updated
DESCRIPTION The timestamp that a new data source contributed to the record for the person's current job.
DATA TYPE String (Date)
FIELD DETAILS

An update is the time when either new information is added to the record or existing information is validated.

EXAMPLE
"job_last_updated": "2018-11-05"
job_onet_broad_occupation
DESCRIPTION The O*NET Broad Occupation associated with the person’s current job title.
DATA TYPE String
EXAMPLE
"job_onet_broad_occupation": "Chief Executives"
job_onet_code
DESCRIPTION The 8-digit O*NET code for the person’s current job title.
DATA TYPE String
FIELD DETAILS

The 8-digit O*NET code for the person’s current job title, following the 2018 SOC guidelines.

EXAMPLE
"job_onet_code": "11-1011.00"
job_onet_major_group
DESCRIPTION The O*NET Major Group associated with the person’s current job title.
DATA TYPE String
EXAMPLE
"job_onet_major_group": "Management Occupations"
job_onet_minor_group
DESCRIPTION The O*NET Minor Group associated with the person’s current job title.
DATA TYPE String
EXAMPLE
"job_onet_minor_group": "Top Executives"
job_onet_specific_occupation
DESCRIPTION The O*NET Specific Occupation associated with the person’s current job title.
DATA TYPE String
EXAMPLE
"job_onet_specific_occupation": "Chief Executives"
job_onet_specific_occupation_detail
DESCRIPTION A more detailed job title classification than O*NET Specific Occupation.
DATA TYPE String
FIELD DETAILS

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.

For example, the highest level of granularity in O*NET for C-suite positions is Chief Executives. With this field, we can specify the type of executive role.

EXAMPLE
"job_onet_specific_occupation_detail": "Chief Technology Officer"
job_start_date
DESCRIPTION The date the person started their current job.
DATA TYPE String (Date)
EXAMPLE
"job_start_date": "2015-03"
job_summary
DESCRIPTION User-inputted summary of their current job.
DATA TYPE String
FIELD DETAILS

The summary is lowercased, but otherwise kept as-is from the raw source.

EXAMPLE
"job_summary": "worked on the \"search analytics\" team to understand our users better"
job_title
DESCRIPTION The person's current job title.
DATA TYPE String
FIELD DETAILS

The person's current job title.

EXAMPLE
"job_title": "co-founder and chief executive officer"
job_title_levels
DESCRIPTION The derived level(s) of the person's current job title.
DATA TYPE Array [Enum (String)]
FIELD DETAILS

Each level in the list will be one of our Canonical Job Title Levels.

Note: The cxo level is a catch-all for "Chief __ Officer" roles, so a CEO, CIO, CTO, etc. will all have job_title_levels: ["cxo"].

EXAMPLE
"job_title_levels": ["cxo", "owner"]
job_title_role
DESCRIPTION The derived role of the person's current job title.
DATA TYPE Enum (String)
FIELD DETAILS

The value will be one of our Canonical Job Roles.

EXAMPLE
"job_title_role": "operations"
job_title_sub_role
DESCRIPTION The derived subrole of the person's current job title.
DATA TYPE Enum (String)
FIELD DETAILS

The value will be one of our Canonical Job Sub Roles. Each subrole maps to a role. See https://docs.peopledatalabs.com/docs/title-subroles-to-roles for a complete mapping list.

EXAMPLE
"job_title_sub_role": "logistics"
Demographics
birth_date
DESCRIPTION The day the person was born.
DATA TYPE String (Date)
FIELD DETAILS

If this field exists, birth_year will agree with it.

EXAMPLE
"birth_date": "1990-12-02"
birth_year
DESCRIPTION The year the person was born.
DATA TYPE Integer
FIELD DETAILS

The approximated birth year associated with this person profile. If a profile has a birth_date, the birth_year field will match it.

EXAMPLE
"birth_year": 1990
gender
DESCRIPTION The person's gender.
DATA TYPE Enum (String)
FIELD DETAILS

The value will always be one of our Canonical Genders.

❗️

Upcoming Breaking Change!

Change Expected In: v26 / April 2024

We are renaming the gender field to sex in the Person Schema. The output will remain the same.

EXAMPLE
JSON
"gender": "male"
languages
DESCRIPTION Languages the person knows.
DATA TYPE Array [Object]
FIELD DETAILS

The languages listed are based on user input, we do not verify them.

FIELD DATA TYPE DESCRIPTION
name Enum (String) The language. Must be one of our Canonical Languages.
proficiency Integer (1-5) Self-ranked language proficiency from 1 (limited) to 5 (fluent).
EXAMPLE
"languages": [ { "name": "english", "proficiency": 5 } ]
Education
education
DESCRIPTION The person's education information.
DATA TYPE Array [Object]
FIELD DETAILS

The education objects associated with this person profile, which, when output in CSV format, have indexing based on recency and associativity.

Each education object in the list will include the following data:

FIELD DATA TYPE DESCRIPTION
degrees Array [Enum (String)] The degrees the person earned at the school. All values will be Canonical Education Degrees
end_date String (Date) The date the person left the school. If the person is still at the school, will be null.
gpa Float The GPA the person earned at the school.
majors Array [Enum (String)] All majors earned at the school. All values will be Canonical Education Majors.
minors Array [Enum (String)] All minors earned at the school. All values will be Canonical Education Majors.
raw Array [String] Raw education data that was parsed into the degrees, majors, and minors fields.
school Object The school the person attended.
start_date String (Date) The date the person started at the school.
summary String User-inputted summary of their education.
education.school

To tap into our school matching logic, use our School Cleaner API to retrieve possible school values.

FIELD SUB FIELD DATA TYPE DESCRIPTION
domain   String The primary website domain associated with the school.
facebook_url   String The school's Facebook URL
id   String The NON-PERSISTENT ID for the school in our records.
linkedin_id   String The school's LinkedIn ID
linkedin_url   String The school's LinkedIn URL
location   Object The location of the school. See Common Location Fields for detailed field descriptions.
  continent Enum (String)  
  country Enum (String)  
  locality String  
  name String  
  region String  
name   String The name of the school.
raw   Array [String] Raw school name.
twitter_url   String The school's Twitter URL
type   Enum (String) The school type. Will be one of our Canonical School Types.
website   String The website URL associated with the school, which could include subdomains.
EXAMPLE
"education": [ { "school": { "name": "university of oregon", "type": "post-secondary institution", "id": "64LkgfdwWYkCC2TjbldMDQ_0", "location": { "name": "eugene, oregon, united states", "locality": "eugene", "region": "oregon", "country": "united states", "continent": "north america" }, "linkedin_url": "linkedin.com/school/university-of-oregon", "linkedin_id": "19207", "facebook_url": "facebook.com/universityoforegon", "twitter_url": "twitter.com/uoregon", "website": "uoregon.edu", "domain": "uoregon.edu", "raw": [ "university of oregon" ] }, "end_date": "2014", "start_date": "2010", "gpa": null, "degrees": [], "majors": [ "entrepreneurship" ], "minors": [], "raw": [ "data analytics & entrepreneurship", ", entrepreneurship", "entrepreneurship" ], "summary": "when i was at oregon i volunteered at a local homeless shelter 3 days a week" }, ]
Location

For more information on our standard location fields, see https://docs.peopledatalabs.com/docs/data-types#locations.

countries
DESCRIPTION All countries associated with the person.
DATA TYPE Array [Enum (String)]
EXAMPLE
"countries": [ "united states" ]
location_address_line_2
DESCRIPTION The person's current street address line 2.
DATA TYPE String
EXAMPLE
"location_address_line_2": "apartment 12"
location_continent
DESCRIPTION The continent of the person's current address. One of our Canonical Continents.
DATA TYPE Enum (String)
EXAMPLE
"location_continent": "north america"
location_country
DESCRIPTION The country of the person's current address. One of our Canonical Countries.
DATA TYPE Enum (String)
EXAMPLE
"location_country": "united states"
location_geo
DESCRIPTION The geo code of the city center of the person's current address.
DATA TYPE String
EXAMPLE
"location_geo": "37.87,-122.27"
location_last_updated
DESCRIPTION The timestamp that a new data source contributed to the record for the person's current address.
DATA TYPE String (Date)
FIELD DETAILS

An update is the time when either new information is added to the record or existing information is validated.

EXAMPLE
"location_last_updated": "2018-11-05"
location_locality
DESCRIPTION The locality of the person's current address.
DATA TYPE String
EXAMPLE
"location_locality": "berkeley"
location_metro
DESCRIPTION The metro of the person's current address. One of our Canonical Metros.
DATA TYPE Enum (String)
EXAMPLE
"location_metro": "san francisco, california"
location_name
DESCRIPTION The location of the person's current address.
DATA TYPE String
EXAMPLE
"location_name": "berkeley, california, united states"
location_names
DESCRIPTION All location names associated with the person.
DATA TYPE Array [String]
EXAMPLE
"location_names": [ "berkeley, california, united states", "san francisco, california, united states" ]
location_postal_code
DESCRIPTION The postal code of the person's current address.
DATA TYPE String
EXAMPLE
"location_postal_code": "94704"
location_region
DESCRIPTION The region of the person's current address.
DATA TYPE String
EXAMPLE
"location_region": "california"
location_street_address
DESCRIPTION The person's current street address.
DATA TYPE String
EXAMPLE
"location_street_address": "455 fake st"
regions
DESCRIPTION All regions associated with the person.
DATA TYPE Array [String]
EXAMPLE
"regions": [ "california, united states" ]
street_addresses
DESCRIPTION All street addresses associated with the person.
DATA TYPE Array [Object]
FIELD DETAILS

Each address associated with the person will be added to this list as its own object.

In addition to the Common Location Fields, street_addresses will also include:

FIELD DATA TYPE DESCRIPTION
first_seen String (Date) The date that this entity was first associated with the Person record.
last_seen String (Date) The date that this entity was last associated with the Person record.
num_sources Integer (> 0) The number of sources that have contributed to the association of this entity with the Person record.
EXAMPLE
"street_addresses": [ { "name": "berkeley, california, united states", "locality": "berkeley", "metro": "san francisco, california", "region": "california", "country": "united states", "continent": "north america", "street_address": "455 fake st", "address_line_2": "apartment 12", "postal_code": "94704", "geo": "37.87,-122.27", "first_seen": "2017-06-02", "last_seen": "2019-07-18", "num_sources": 17 } ]
Lower Confidence Data

PDL values high confidence data that is very likely to be associated with a person. The data in these fields have lower confidence than the data used in other fields.

possible_birth_dates
DESCRIPTION Birthdays associated with this person that have a lower level of confidence.
DATA TYPE Array [String (Date)]
FIELD DETAILS

The dates in this field use the same format as the birth_date field.

EXAMPLE
"possible_birth_dates": [ "1991-05-26", "1992-05-26" ]
possible_emails
DESCRIPTION Email addresses associated with this person that have a lower level of confidence.
DATA TYPE Array [Object]
FIELD DETAILS

This field uses the same format as the emails field.

EXAMPLE
"possible_emails": [ { "address": "[email protected]", "type": null, "first_seen": "2021-06-13", "last_seen": "2021-06-13", "num_sources": 2 } ]
possible_location_names
DESCRIPTION Locations associated with this person that have a lower level of confidence.
DATA TYPE Array [String]
FIELD DETAILS

This field uses the same format as the location_names field.

Possible locations are inferred based on phone area codes, university location, and other associations.

EXAMPLE
"possible_location_names": [ "berkeley, california, united states", "san francisco, california, united states" ]
possible_phones
DESCRIPTION Phone numbers associated with this person that have a lower level of confidence.
DATA TYPE Array [Object]
FIELD DETAILS

This field uses the same format as the phones field.

EXAMPLE
"possible_phones": [ { "number": "+15558675309", "first_seen": "2021-06-13", "last_seen": "2021-06-13", "num_sources": 2 } ]
possible_profiles
DESCRIPTION Social profiles associated with this person that have a lower level of confidence.
DATA TYPE Array [Object]
FIELD DETAILS

This field uses the same format as the profiles field.

EXAMPLE
"possible_profiles": [ { "network": "linkedin", "id": "145991517", "url": "linkedin.com/in/seanthorne", "username": "seanthorne", "first_seen": "2021-06-13", "last_seen": "2021-06-13", "num_sources": 2 } ]
possible_street_addresses
DESCRIPTION Addresses associated with this person that have a lower level of confidence.
DATA TYPE Array [Object]
FIELD DETAILS

This field uses the same format as the street_addresses field.

EXAMPLE
"possible_street_addresses": [ { "name": "berkeley, california, united states", "locality": "berkeley", "metro": "san francisco, california", "region": "california", "country": "united states", "continent": "north america", "street_address": "455 fake st", "address_line_2": "apartment 12", "postal_code": "94704", "geo": "37.87,-122.27", "first_seen": "2021-06-13", "last_seen": "2021-06-13", "num_sources": 2 } ]
Social Presence

We currently cover person social profiles on our Canonical Profile Networks. All profiles we've found for a person will be added to the profiles list.

Each social profile URL has one or more standard formats that we parse and turn into a standard PDL format for that social URL. We invalidate profiles that have non-valid person stubs (for example, linkedin.com/company), and we also have a blacklist of usernames that we know are invalid.

We do not validate if a URL is valid (that is, whether you can access it) because doing this at scale is considered a Direct Denial of Service (DDoS) attack and/or a form of crawling. This is highly discouraged! We try to mitigate invalid URLs as much as possible by using Entity Resolution (Merging) to link URLs together and then tagging the primary URL at the top level for key networks.

facebook_friends
DESCRIPTION The number of Facebook friends the person has.
DATA TYPE Integer (>= 0)
EXAMPLE
"facebook_friends": 3912
facebook_id
DESCRIPTION The person's Facebook profile ID based on source agreement.
DATA TYPE String
EXAMPLE
"facebook_id": "1089351304"
facebook_url
DESCRIPTION The person's Facebook profile URL based on source agreement.
DATA TYPE String
EXAMPLE
"facebook_url": "facebook.com/deseanthorne"
facebook_username
DESCRIPTION The person's Facebook profile username based on source agreement.
DATA TYPE String
EXAMPLE
"facebook_username": "deseanthorne"
github_url
DESCRIPTION The person's GitHub profile URL based on source agreement.
DATA TYPE String
EXAMPLE
"github_url": "github.com/deseanathan_thornolotheu"
github_username
DESCRIPTION The person's GitHub profile username based on source agreement.
DATA TYPE String
EXAMPLE
"github_username": "deseanathan_thornolotheu"
linkedin_connections
DESCRIPTION The number of LinkedIn connections the person has.
DATA TYPE Integer (>= 0)
FIELD DETAILS

Typically between 0-500.

EXAMPLE
"linkedin_connections": 432
linkedin_id
DESCRIPTION The person's LinkedIn profile ID based on source agreement.
DATA TYPE String
EXAMPLE
"linkedin_id": "145991517"
linkedin_url
DESCRIPTION The person's LinkedIn profile URL based on source agreement.
DATA TYPE String
EXAMPLE
"linkedin_url": "linkedin.com/in/seanthorne"
linkedin_username
DESCRIPTION The person's LinkedIn profile username based on source agreement.
DATA TYPE String
EXAMPLE
"linkedin_username": "seanthorne"
profiles
DESCRIPTION Social profiles associated with the person.
DATA TYPE Array [Object]
FIELD DETAILS

Each profile associated with the person will be added to this list as its own object.

FIELD DATA TYPE DESCRIPTION
id String The profile ID (format varies based on social network).
first_seen String (Date) The date that this entity was first associated with the Person record.
last_seen String (Date) The date that this entity was last associated with the Person record.
network Enum (String) The social network the profile is on. Must be one of our Canonical Profile Networks.
num_sources Integer (> 0) The number of sources that have contributed to the association of this entity with the Person record.
url String The profile URL.
username String The profile username.
EXAMPLE
"profiles": [ { "network": "linkedin", "id": "145991517", "url": "linkedin.com/in/seanthorne", "username": "seanthorne", "first_seen": "2017-06-02", "last_seen": "2019-07-18", "num_sources": 17 } ]
twitter_url
DESCRIPTION The person's Twitter profile URL based on source agreement.
DATA TYPE String
EXAMPLE
"twitter_url": "twitter.com/seanthorne5"
twitter_username
DESCRIPTION The person's Twitter profile username based on source agreement.
DATA TYPE String
EXAMPLE
"twitter_username": "seanthorne5"
Work History
certifications
DESCRIPTION Any certifications the person has.
DATA TYPE Array [Object]
FIELD DETAILS

The certifications listed are based on user input, we do not verify them.

FIELD DATA TYPE DESCRIPTION
end_date String (Date) The expiration date of the certification.
name String Certification name
organization String The organization awarding the certification.
start_date String (Date) The date the certification was awarded.
EXAMPLE
"certifications": [ { "name": "machine learning certification", "organization": "coursera", "start_date": "2022-03", "end_date": "2023-04" } ]
experience
DESCRIPTION The person's work experience.
DATA TYPE Array [Object]
FIELD DETAILS

The order of work experience in the list is determined by recency and associativity. The experience object that is tagged as experience.is_primary = True is copied over to the flattened job_ fields (see Current Job and Current Company).

Each work experience object contains the following fields:

FIELD DATA TYPE DESCRIPTION
company Object The company where the person worked.
end_date String (Date) The date the person left the company. If the person is still working for the company, will be null.
first_seen String (Date) The date that this entity was first associated with the Person record.
last_seen String (Date) The date that this entity was last associated with the Person record.
is_primary Boolean Whether this is the person's current job or not. If true, this experience will be used to populate the job_ fields.
location_names Array [String] Locations where the person has worked while with this company (if different from the company HQ).
num_sources Integer (> 0) The number of sources that have contributed to the association of this entity with the Person record.
start_date String (Date) The date the person started at the company.
summary String User-inputted summary of their work experience.
title Object The person's job title while at the company.
experience.company

The fields in experience.company map to the corresponding fields in our Company Schema. The same parsing and formatting logic apply.

FIELD SUB FIELD DATA TYPE DESCRIPTION
facebook_url   String The company's Facebook URL
founded   Integer (> 0) The founding year of the company.
id   String The company's PDL ID
industry   Enum (String) The self-identified industry of the company. Must be one of the Canonical Industries.
linkedin_id   String The company's LinkedIn ID
linkedin_url   String The company's LinkedIn URL
location   Object The location of the company's headquarters. See Common Location Fields for detailed field descriptions.
  address_line_2 String  
  continent Enum (String)  
  country Enum (String)  
  geo String  
  locality String  
  metro Enum (String)  
  name String  
  postal_code String  
  region String  
  street_address String  
name   String The company name, cleaned and standardized.
raw   Array [String] Raw company name.
size   Enum (String) The self-reported company size range. Must be one of our Canonical Company Sizes.
ticker   String The company ticker. This field will only have a value if the company's type is public.
twitter_url   String The company's Twitter URL
type   Enum (String) The company type. Must be one of our Canonical Company Types.
website   String The company's primary website, cleaned and standardized.
experience.title

See the corresponding Current Job fields for more details on the information included and formatting of these fields.

FIELD DATA TYPE DESCRIPTION
levels Array [Enum (String)] Canonical Job Title Levels.
name String The cleaned job title.
raw Array [String] Raw job title input.
role Enum (String) One of the Canonical Job Roles.
sub_role Enum (String) One of the Canonical Job Sub Roles.
EXAMPLE
"experience": [ { "company": { "name": "people data labs", "size": "11-50", "id": "peopledatalabs", "founded": 2015, "industry": "computer software", "location": { "name": "san francisco, california, united states", "locality": "san francisco", "region": "california", "metro": "san francisco, california", "country": "united states", "continent": "north america", "street_address": "455 market street", "address_line_2": "suite 1670", "postal_code": "94105", "geo": "37.77,-122.41" }, "linkedin_url": "linkedin.com/company/peopledatalabs", "linkedin_id": "18170482", "facebook_url": "facebook.com/peopledatalabs", "twitter_url": "twitter.com/peopledatalabs", "website": "peopledatalabs.com", "ticker": null, "type": "private", "raw": [ "people data labs" ], }, "location_names": ["san francisco, california, united states"], "end_date": null, "start_date": "2015-03", "title": { "name": "chief executive officer and co-founder", "raw": [ "co-founder & ceo", "co-founder & ceo", "co-founder and chief executive officer" ], "role": "operations", "sub_role": "logistics", "levels": [ "cxo", "owner" ], }, "is_primary": true, "summary": "worked on the \"search analytics\" team to understand our users better", "first_seen": "2018-10-11", "last_seen": "2022-11-15", "num_sources": 17 }, ]
industry
DESCRIPTION The most relevant industry for this person based on their work history.
DATA TYPE Enum (String)
FIELD DETAILS

A person's industry is determined based on their tagged personal industries and the industries of the companies that they have worked for.

The value will be one of our Canonical Industries.

EXAMPLE
"industry": "computer software"
inferred_years_experience
DESCRIPTION The person's inferred years of total work experience.
DATA TYPE Integer (0 - 100)
FIELD DETAILS

The value will be between 0 and 100.

EXAMPLE
"inferred_years_experience": 7
interests
DESCRIPTION The person's self-reported interests.
DATA TYPE Array [String]
FIELD DETAILS

Each interest is cleaned (lowercased, stripped of whitespace, etc.). We don't have a canonical list of interests but we remove profanity and do some basic cleaning.

EXAMPLE
"interests": [ "data" ]
job_history
DESCRIPTION Additional professional positions that may have been removed or changed on resumes.
DATA TYPE Array [Object]
FIELD DETAILS

Any additional job history information PDL has that is not included in the experience field.

Usually these are positions that have been removed or changed on resumes.

FIELD DATA TYPE DESCRIPTION
company_id String PDL Company ID
company_name String Company Name
first_seen String (Date) The date that this experience was first associated with this record.
last_seen String (Date) The date that this experience was last associated with this record.
num_sources Integer (> 0) The number of sources that have contributed to the association of this profile with this record.
title String Job Title at this company.
EXAMPLE
"job_history": [ { "company_id": "auntie-annes", "company_name": "auntie annes", "title": "food service supervisor", "first_seen": "2016-05-17", "last_seen": "2020-05-30", "num_sources": 12 } ]
skills
DESCRIPTION The person's self-reported skills.
DATA TYPE Array [String]
FIELD DETAILS

Each skill is cleaned (lowercased, stripped of whitespace, etc.). We do not always strip punctuation because it can be relevant for some skills (ex: "c++" vs "c").

We do not do any canonicalization, so "java" and "java 8.0" are considered separate skills. For this reason, we encourage our customers to use fuzzy text matching with the skills field.

The Skill Enrichment API can help find similar skills.

EXAMPLE
"skills": [ "entrepreneurship" ]
summary
DESCRIPTION User-inputted personal summary.
DATA TYPE String
FIELD DETAILS

The self-written summary tied to the person profile (often a LinkedIn summary).

The summary is lowercased, but otherwise kept as-is from the raw source.

EXAMPLE
"summary": "growth-hacker and digital nomad"
PDL Record Information & Metadata
dataset_version
DESCRIPTION The major or minor release number.
DATA TYPE String
FIELD DETAILS

This field currently exists in Person Enrichment API responses only.

Note: This number corresponds to the data release number, not the API release number.

EXAMPLE
"dataset_version": "19.2"
first_seen
DESCRIPTION The date when this record was first created in our data.
DATA TYPE String (Date)
EXAMPLE
"first_seen": "2017-06-02"
num_records
DESCRIPTION The number of unique raw records contributing to this specific PDL profile.
DATA TYPE Integer (> 0)
EXAMPLE
"num_records": 420
num_sources
DESCRIPTION The number of unique sources contributing to this specific PDL profile.
DATA TYPE Integer (> 0)
EXAMPLE
"num_sources": 72
operation_id
DESCRIPTION An identifier for an operation in a Data License delivery, used for troubleshooting.
DATA TYPE String
FIELD DETAILS

This field exists only in Data License deliveries, and allows PDL employees to identify the timestamp and operations performed on the internal data in order to return a record in a delivery.

EXAMPLE
"operation_id": "acee3bde2e1a2cb7e75c57b80d5b7bc2d5de5b02e7ea51f91304c28df77251dc"
version_status

❗️

DEPRECATION NOTICE

This object has been deprecated in API responses.

DESCRIPTION Metadata about the version of the dataset used to retrieve this record.
DATA TYPE Object
FIELD DETAILS

This object tracks the pervious and current dataset version, and any other persistent IDs that were merged into this record using improved entity resolution and the status of the record.

FIELD DATA TYPE DESCRIPTION
contains Array [String] The list of IDs that have been merged into this record since the last release.
current_version String The current data version.
previous_version String The previous data version.
status Enum (String) The changes made to this record between the previous release and the current one. One of our Canonical Version Statuses.
EXAMPLE
JSON
"version_status": { "contains": [ "qEnOZ5Oh0poWnQ1luFBfVw_0000" ], "current_version": "15", "previous_version": "14", "status": "updated" }

Cookie Notice

We and third parties such as our customers, partners, and service providers use cookies and similar technologies (\"cookies\") to provide and secure our Services, to understand and improve their performance, and to serve relevant information. For more information, see our Cookie Policy.

Accept Cookies

Back to top