Overview

In an effort to ensure responsible data stewardship we have obscured values for contact data from all Person API Endpoints for all Free plans effective in the January 2025 release (v29.0).

What’s Changed?

All affected fields will now display as true or false in the API responses for all affected API products. This allows you to continue to test your workflows using our Free plans before deciding to upgrade to a Pro plan.

Each product will need to be subscribed to a Pro plan to unlock the values. For example, if you have a Pro plan for the Person Enrichment API, you will continue to see true or false for affected fields when using your Free plan for the Person Search API.

Affected API products

• Person Enrichment API
• Person Search API
• Person Identify APIs

Affected fields

Example output

Abridged API Response prior to the change

{

  "id": "NvnAvOpyEVAoNGnVZQUqLU_0000",
  "full_name": "sarah richard",
  "first_name": "sarah",
  "middle_initial": null,
  "middle_name": null,
  "last_initial": "r",
  "last_name": "richard",
  "sex": "female",
  "birth_year": 1987,
  "birth_date": "1987-06-07",
  "linkedin_url": "linkedin.com/in/sr49",
  "linkedin_username": "sr49",
  "linkedin_id": "NvnAvO",
  "work_email": null,
  "personal_emails": [
    "sr49@icloud.com",
    "sr50@icloud.com",
    "sr51@icloud.com"
  ],
  "recommended_personal_email": "sr49@icloud.com",
  "mobile_phone": "+18097463343",
  "industry": "online media",
  "job_title": "musician",
  "job_title_role": null,
  "job_title_sub_role": null,
  "job_title_levels": ["senior"],
  "location_name": "changchester, ontario, canada",
  "location_locality": "changchester",
  "location_metro": "changchester",
  "location_region": "ontario",
  "location_country": "canada",
  "location_continent": "north america",
  "location_street_address": "0487 hull village suite 759",
  "location_address_line_2": "suite 604",
  "location_postal_code": "A6A 6A0",
  "location_geo": "13.4134995,26.826999",
  "location_last_updated": "2021-09-09",
...
}

Abridged API response after the change

{
  "id": "NvnAvOpyEVAoNGnVZQUqLU_0000",
  "full_name": "sarah richard",
  "first_name": "sarah",
  "middle_initial": null,
  "middle_name": null,
  "last_initial": "r",
  "last_name": "richard",
  "sex": "female",
  "birth_year": true,
  "birth_date": true,
  "linkedin_url": "linkedin.com/in/sr49",
  "linkedin_username": "sr49",
  "linkedin_id": "NvnAvO",
  "work_email": false,
  "personal_emails": true,
  "recommended_personal_email": true,
  "mobile_phone": true,
  "industry": "online media",
  "job_title": "musician",
  "job_title_role": null,
  "job_title_sub_role": null,
  "job_title_levels": ["senior"],
  "location_name": true,
  "location_locality": true,
  "location_metro": true,
  "location_region": true,
  "location_country": "canada",
  "location_continent": "north america",
  "location_street_address": true,
  "location_address_line_2": true,
  "location_postal_code": true,
  "location_geo": true,
  "location_last_updated": "2021-09-09",
...
}

What do I need to do?

• Your existing workflows that are using a Free plan for any affected products and fields will need to be adjusted to handle the true or false values
  • E.g. if you are checking for a null value, you will need to switch this check to look for a “false” value
• If your workflow relies on a Free plan to extract and serve one of the affected fields, you will need to upgrade to a Pro plan to unlock the values

Need additional support?

Get in touch with support by submitting a ticket.