Overview
We’ve enhanced our Person API V2 to provide richer and more detailed metadata for email and phone fields.
In the previous version (V1) of Lusha’s Person API, only email addresses were available in the response. The updated Email addresses now include the additional metadata: “emailType” and “emailConfidence” fields.
Similarly, while V1 provided only phone numbers, the new PhoneNumbers object now includes “phoneType” and “Do Not Call” (DNC) indication (where applicable), ensuring full compliance with regulatory standards.
To provide a better and smoother experience, we are replacing the old “phones “ and “ emails “ fields with “emailAddresses” and “phoneNumbers” fields.
Deprecation Notice
💡 The old "emails" and “phones” fields will be deprecated by August 31, 2024. Please ensure to make the necessary adjustments before this date to avoid any disruptions.
Implementation Guide
Email Fields Update
Old Email Fields: TO BE DEPRECATED
New Email Addresses Field:
Request:
Results:
Phone Fields Update
Old Phones Fields: TO BE DEPRECATED
New Phone Numbers Field:
Action Required
To adjust to the new “emailAddresses” and “phoneNumbers” fields, please update your system’s field mapping from our API response as follows:
Identify where your system currently maps the “emails” and “phones” fields.
Change these mappings to “emailAddresses” and “phoneNumbers” to align with the relevant metadata mentioned above..
💡 If you do not update these fields, you will receive an error message when attempting to enrich your system using the Lusha Person API, and you will be unable to properly interface with the API.