Skip to main content
Send exactly one of linkedinUrl or email. This page covers linkedinUrl. For email, see reverse email lookup.

Example

The response is a task. Poll it, then read data:

The result

Profile fields: full_name, first_name, last_name, headline, about, avatar_url, city, country_code, linkedin_followers, linkedin_connections. Any of them can be null when LinkedIn does not show it. memorialized is true when LinkedIn has marked the profile as belonging to someone who has died.

Positions

positions is the employment history, current roles first. Two things to know:
  • company is often null. A LinkedIn experience entry gives an employer name and rarely anything we can match to a company record. Read company_name. It is populated whenever we have an employer at all. Treat company as extra detail for the cases where we matched it.
  • Dates are always full dates but not always fully known. Read start_date_precision and end_date_precision before displaying them. A source that gave only "2021" comes back as 2021-01-01 with precision "year".

Freshness

A stored profile older than 30 days is not served as-is. The request is queued (202), the profile is re-fetched, and then the task settles. This matters more for people than for companies. A person who changed jobs is not just out of date. The new role is usually the reason you asked. Refreshing costs the same 1 credit as any other profile request. If the refresh cannot complete, the task still succeeds and returns the stored record. Compare last_enriched_at to tell the two apart.