How does the JSON and Object and description table of person identify API created by People Data Labs work?

In this article, I will provide a detailed clarification of the object table and JSON output of the People Data Labs person identify API. As a programmer, you are likely familiar with the concept of object tables and JSON, but understanding the specific output of the People Data Labs API is critical to extracting meaningful information from the data. By providing a clear understanding of the object table and JSON output, you can gain a deeper insight into the API's data structure and effectively utilize it for your programming needs.

Object and Description table

ObjectsDescription
statusThe API response code
matchesA list of up to 20 profiles matching the input criteria from the API request. The API only returns profiles with a match_score greater than 5 (out of 100.)
matches.match_scoreAn integer between 1-99 drawn from a probability-like distribution representing the matching strength between a profile and the input criteria. In other words, the probability that this record is the record you are looking for based on your query.
matches.dataThe field attributes associated with this profile. For a list of fields, see the Person Schema.
matches.matched_onA list of data fields that the API matched for this profile. The API only returns this if you set the include_if_matched input parameter to true.
  1. status: This object represents the API response code, which can be used to determine whether the API call was successful or not. The value of this object will be a numeric code indicating the status of the response, such as 200 for a successful response, 400 for a bad request, or 500 for a server error.

  2. matches: This object represents a list of up to 20 profiles that match the input criteria from the API request. The API only returns profiles with a match_score greater than 5 (out of 100). Each profile in the list is represented by a separate object with its own set of attributes.

  3. matches.match_score: This object represents an integer between 1-99 drawn from a probability-like distribution that represents the matching strength between a profile and the input criteria. In other words, this object represents the probability that a given profile is the record you are looking for based on your query.

  4. matches.data: This object represents the field attributes associated with a given profile. Each field attribute is represented by a separate object within this object. For a complete list of available fields, you can refer to the Person Schema.

  5. matches.matched_on: This object represents a list of data fields that the API matched for a given profile. The API only returns this object if you set the include_if_matched input parameter to true. This object can be used to determine which fields in a profile matched your query, which can be helpful for data validation or troubleshooting purposes.

The information provided in the table is extremely useful for any programmer or developer who is working with the People Data Labs person identify API. By understanding the various objects and their detailed descriptions, programmers can effectively extract and utilize the data provided by the API. For example, knowing the structure and meaning of the matches object can help developers extract relevant profiles from the API response and use the associated matches.data object to access the relevant profile information. Additionally, understanding the meaning of the matches.match_score object can help developers determine the strength of the match between a given profile and their query, which can help improve the accuracy of data retrieval and analysis. Overall, having a clear understanding of the various objects and their meanings can significantly enhance the utility and effectiveness of the People Data Labs person identify API.

JSON REST Output

The below JSON output represents a profile of a person with several data attributes. The data includes information such as the person's full name, gender, birth year, contact information (including mobile phone, work email, and personal email), and social media profiles (including LinkedIn, Facebook, and Twitter). Additionally, it includes details about the person's job, such as job title, company, industry, location, and job summary. Other data attributes include the person's location, inferred salary, inferred years of experience, summary, phone numbers, and emails. The JSON output also includes a unique identifier for the profile and a matching score, which represents the probability that the profile is the record the user is looking for based on their query. Overall, this JSON output contains a wealth of information about a person that can be leveraged by developers for various purposes, such as building products, predictive modeling, and analysis.

{
"status": 200,
"matches": [
{
"data": {
"id": "qEnOZ5Oh0poWnQ1luFBfVw_0000",
"full_name": "sean thorne",
"first_name": "sean",
"middle_initial": "f",
"middle_name": "fong",
"last_name": "thorne",
"gender": "male",
"birth_year": 1990,
"birth_date": null,
"linkedin_url": "linkedin.com/in/seanthorne",
"linkedin_username
": "seanthorne",
"linkedin_id": "145991517",
"facebook_url": "facebook.com/deseanthorne",
"facebook_username
": "deseanthorne",
"facebook_id": "1089351304",
"twitter_url": "twitter.com/seanthorne5",
"twitter_username
": "seanthorne5",
"github_url": null,
"github_username": null,
"work_email": "sean@peopledatalabs.com",
"personal_emails": [],
"mobile_phone": "+14155688415",
"industry": "computer software",
"job_title": "co-founder and chief executive officer",
"job_title_role": null,
"job_title_sub_role": null,
"job_title_levels": [
"owner",
"cxo"
],
"job_company_id": "peopledatalabs",
"job_company_name": "people data labs",
"job_company_website": "peopledatalabs.com",
"job_company_size": "11-50",
"job_company_founded": 2015,
"job_company_industry": "computer software",
"job_company_linkedin_url": "linkedin.com/company/peopledatalabs",
"job_company_linkedin_id
": "18170482",
"job_company_facebook_url": "facebook.com/peopledatalabs",
"job_company_twitter_url
": null,
"job_company_type": "private",
"job_company_ticker": null,
"job_company_location_name": "san francisco, california, united states",
"job_company_location_locality": "san francisco",
"job_company_location_metro": "san francisco, california",
"job_company_location_region": "california",
"job_company_location_geo": "37.77,-122.41",
"job_company_location_street_address": "455 market street",
"job_company_location_address_line_2": "suite 1670",
"job_company_location_postal_code": "94105",
"job_company_location_country": "united states",
"job_company_location_continent": "north america",
"job_last_updated": "2021-12-15",
"job_start_date": "2015-03",
"job_summary": "People Data Labs builds people data. Leverage our dataset of 1.5 billion unique person profiles as your data foundation to build products, enrich person profiles, power predictive modeling/AI, analysis, and more. We build and maintain our data from our powerful Data Union. We work with thousands of data science teams as their engineering focused people data partner. These include enterprises like adidas, eBay, and Acxiom, as well as startups like Madison Logic, Zoho, and Workable. Backed by Founders Fund. I consult with our engineering customers to solve people data building challenges - sean@peopledatalabs.com",
"location_name": "san francisco, california, united states",
"location_locality": "san francisco",
"location_metro": "san francisco, california",
"location_region": "california",
"location_country": "united states",
"location_continent": "north america",
"location_street_address": null,
"location_address_line_2": null,
"location_postal_code": null,
"location_geo": "37.77,-122.41",
"location_last_updated": "2021-12-15",
"linkedin_connections": 10135,
"inferred_salary": ">250,000",
"inferred_years_experience": 9,
"summary": "Interested in solving the hardest problems the enterprise is facing.",
"phone_numbers": [
"+14155688415"
],
"emails": [
{
"address": "sthorne@uoregon.edu",
"type": null
},
{
"address": "sean@hallspot.com",
"type": "professional"
},
{
....

Concluding

We discussed various aspects related to the People Data Labs person identify API and its object table and JSON output. We went over the objects listed in the table and provided detailed descriptions of each one. We also analyzed a sample JSON output that contained information about a person's profile, highlighting the different data attributes included in it. The information provided in this conversation can be valuable for developers and programmers who are working with the People Data Labs API and are looking to understand the structure and meaning of the data they receive. Understanding the different objects and their meaning can help improve the accuracy of data retrieval and analysis and enhance the overall utility of the API.

Endnote

You can request access to the People Data Labs person identify API through the third-party data marketplace of Worldindata. Worldindata is a leading provider of data solutions and offers access to a wide range of datasets and APIs, including the People Data Labs person identify API. By requesting access to the API through Worldindata, you can access the People Data Labs API and leverage its rich set of data attributes to build products, enrich person profiles, power predictive modeling/AI, analysis, and more. Worldindata provides a simple and convenient way for developers and businesses to access the People Data Labs API, and they also offer support and guidance throughout the data integration process.