LinkedIn User ID Lookup
Member URN lookup from a linkedin.com /in/<slug>/ profile URL — currently in development.
What is LinkedIn?
LinkedIn is the world's largest professional network — launched in May 2003, acquired by Microsoft in December 2016 for $26.2 billion, and now home to over 1 billion members across 200+ countries.
Unlike most consumer platforms, LinkedIn does not expose its numeric member ID through the public profile URL — every account is referenced internally by a Member URN in the form urn:li:member:<id>. IDInfo's LinkedIn resolver is currently in development; this page documents the planned behaviour.
How LinkedIn user IDs evolved
From the very first IDs to today's modern numeric format — here's how the system grew alongside the platform itself.
-
2003
Sequential member IDs
LinkedIn co-founder Reid Hoffman registered as member 1. Early members got tiny sequential IDs in the 1–1000 range.
-
2008
Custom URL slugs introduced
LinkedIn added vanity URLs (
linkedin.com/in/your-slug). The numeric member ID stayed under the hood and is still the canonical identifier. -
2014
Member URN format adopted
Internally, LinkedIn standardised on the
urn:li:member:<id>URN scheme used by Voyager and the LinkedIn API. URNs replace bare integers in every modern endpoint. -
2016
Microsoft acquisition — Sales Navigator integrations
After Microsoft's acquisition, LinkedIn doubled down on its data graph. The member URN became the cross-product identity used by Dynamics 365, Sales Navigator, and Teams.
-
2024+
IDInfo LinkedIn resolver (in dev)
Resolving a public LinkedIn URL to its member URN without an authenticated session is technically harder than other platforms — LinkedIn aggressively rate-limits anonymous traffic. We are building a careful, terms-of-service-respecting resolver and will activate it on this URL when it ships.
What you get from a LinkedIn lookup
Every LinkedIn profile resolved through IDInfo returns these fields, all from public sources.
Member URN
The canonical <code>urn:li:member:<id></code> identifier used by every LinkedIn API.
Vanity slug
The /in/<slug> portion of the public URL.
Display name & headline
Public name and professional headline as visible to non-logged-in viewers.
Current company (when public)
Most recent company, where the member chose to make it public.
Why your LinkedIn member ID will matter
- LinkedIn Talent Insights / Recruiter APIs accept the member URN as the canonical identifier, never the slug.
- ATS integrations (Greenhouse, Lever, Workday) store the member URN to keep candidate records stable when people rebrand their slug.
- Sales Navigator & CRMs (Salesforce, HubSpot, Dynamics) map LinkedIn lead records by URN — the slug can change but the URN never does.
- Account-Based Marketing tools join CRM data to LinkedIn engagement data on the URN field.
LinkedIn user ID — common questions
When will LinkedIn lookup go live?
Can I use IDInfo for the other 8 platforms today?
Why is LinkedIn harder to resolve than the other platforms?
Will the LinkedIn API be free like the others?
One tool, every platform.
Resolve your first LinkedIn ID in under a second.
No sign-up. No API key. Just paste a URL.
Open the resolver →