Person API V2 replaces the deprecated V1 endpoint with expanded enrichment options, richer data fields, and new metadata. If you're still using api.lusha.com/bulk/person, you need to migrate before V1 is shut down.
⚠️ Important: Person API V1 was deprecated on 14 January 2025. If you haven't migrated yet, switch to V2 immediately to avoid disruptions.
What's new in V2
More lookup options - enrich by email or LinkedIn URL in addition to name + company/domain
Job change indicator - use
refreshJobInfo=trueto get current job info for a contactRicher metadata - email type, email confidence, phone type, Do Not Call (DNC) flags, company revenue, funding, intent topics, and more
What you need to change
1. Update the endpoint
GET https://api.lusha.com/v2/person
2. Update request parameters
V2 accepts these lookup combinations (pass your api_key in the header as before):
GET https://api.lusha.com/v2/person?firstName=Yoni&lastName=Tserruya&companyName=LushaGET https://api.lusha.com/v2/person?firstName=Yoni&lastName=Tserruya&companyDomain=lusha.comGET https://api.lusha.com/v2/[email protected] https://api.lusha.com/v2/person?linkedinUrl=https://www.linkedin.com/in/yonitserruya-H api_key:API_KEY
3. Add filtering options if needed
?filterBy=phoneNumbers— only return results with phone numbers?filterBy=emailAddresses— only return results with email addresses
4. Use refreshJobInfo for real-time job updates
GET https://api.lusha.com/v2/[email protected]&refreshJobInfo=true -H api_key:API_KEY
5. Update your response parsing
Review the new response structure and update your parsing logic to handle:
Email metadata:
emailType,emailConfidencePhone metadata:
phoneType,doNotCallCompany insights: revenue, funding, intent topics, and more
6. Test your integration
Run your critical workflows against V2 to confirm all API calls succeed and return the expected data. Monitor logs during and after the transition.
For full parameter and response documentation, see the Lusha API Hub.