How the Person Profile Endpoint Works
What the Person Profile endpoint returns, how credits are charged, and when to use it.
The Person Profile endpoint lets you access detailed information about individuals based on a known LinkedIn URL. It's designed for 1:1 enrichment — you provide a direct profile link and get structured data about that person in return.
What it returns
A successful call can return:
- Full name, headline, and job title
- Company and role details
- Work history, education, and skills
- Optional enrichments: certifications, projects, publications
You can exclude optional fields to reduce credit usage.
How it works
Send a request with a valid LinkedIn profile URL as input:
{
"linkedin_profile_url": "https://linkedin.com/in/example-user"
}Without optional enrichments, the response returns core information only.
Credit usage
A basic call costs 1 credit. You may be charged 2 or more credits if:
- Data freshness is enabled (
use_cache=if-recent) - You include enrichments that require deeper data lookups
When to use it
- Enriching leads in your CRM
- Pulling profile data for personalized outreach
- Verifying job history or current position
- Building user segments based on industry, education, or company
If the profile doesn't exist or can't be found, no credits are deducted.
Understanding incomplete data
Some fields may be missing or incomplete. Common reasons:
Privacy settings — LinkedIn users can set sections of their profile to private. We respect those preferences and return null for restricted fields. This is part of our GDPR compliance.
Missing dates — Some profiles have missing start or end dates in experiences or education. This happens when the user didn't provide the information, historical data is incomplete, or the entry predates date tracking. We use approximately 10 years of historical data to backfill where possible.
School names — May be missing if the user set their education to private or LinkedIn has restricted access.
Public vs. private data
Our API only collects data that is publicly visible on LinkedIn. This is why results may differ from what you see when viewing a profile while logged in or connected to that person. When data is set to private, the API returns null for those fields.