R
Renan Goulart
The
/v2/li-profiles-by-urls/result
endpoint currently returns the lead's current position(s)/role at their company, but doesn't include past positions (work history).
Problem:
for outbound personalization, ICP scoring, and buying-intent analysis based on career trajectory, past roles are just as important as the current one. Knowing a lead's career path (previous companies, roles, tenure, industry transitions) is often what signals relevant context for outreach — e.g., someone who recently moved from a competitor, was promoted into a decision-making role, or has relevant domain experience from earlier roles.
Request:
extend the endpoint's response to include the full work history (past positions), not just the current one.
Expected fields per past position:
  • Company name
  • Company LinkedIn URL/domain (if available)
  • Job title
  • Start date / end date (or duration)
  • Location (if available)
  • Description (if available)
Additional request — optional email lookup parameter:
There's currently no dedicated endpoint to find and verify an email address directly from a LinkedIn profile URL (see related feature request). It would be very valuable if this endpoint also supported an optional parameter (e.g.
include_email: true
) to return the email lookup result (address + verification status) together with the profile data in the same call.
Why combine them:
profile data and email are both commonly needed for the same lead in outbound workflows. Being able to request both in a single call would reduce the number of API calls needed per lead and simplify enrichment pipelines.
**Expected additional response fields (when
include_email
is set):**
  • Email address
  • Email verification status (valid/invalid/unknown)
  • Source/confidence score (if available)
Business justification:
enables richer profile-based personalization, trajectory analysis, and intent scoring directly from the API response, without needing to scrape or reconstruct work history through other means — and, combined with optional email lookup, reduces the number of calls needed to fully enrich a lead in one pass.
Use case:
RevOps/outbound workflows that score and personalize messaging based on a lead's career path (job changes, tenure patterns, industry moves) as a proxy for buying intent and relevance, while also needing a verified contact email for the same lead.