Profile Enrichment API
Send a professional profile URL and get a structured record back: current role, employer, location, full work history, education, skills, languages, certifications and recommendations.
Every call is answered by fetching the record at that moment, so what you store is what is published now rather than whatever a dataset vendor last collected.
- requests served per month
- 40M+requests served per month
- uptime
- 99.9%uptime
- median response time
- 1smedian response time
- serving production traffic since
- 2023serving production traffic since
What you send, what you get
A public professional profile URL, a public identifier, or a profile URN.
- Identity
- firstName, lastName, title, description, location, countryCode, geoCountryName, profilePictureUrl, publicIdentifier, memberId
- Current role
- currentPosition, jobTitle, companyName, companyId, companyPublicId, currentSchool
- History
- experiences, educations, certifications, testScores
- Capabilities
- skills, languages, volunteerCauses, recommendations
- Signals
- openToWork, openProfile, premium, inRemembrance, joinDate, followerCount
GET /api/v1/profile. Full field reference in the documentation.
One call, start to finish
Request
curl "https://api.fetchin.io/api/v1/profile?url=https://www.linkedin.com/in/williamhgates" \
-H "X-API-Key: your-api-key"Response
{
"profile": {
"firstName": "William",
"lastName": "Gates",
"title": "Co-chair, Bill & Melinda Gates Foundation",
"location": "Seattle, Washington",
"countryCode": "us",
"jobTitle": "Co-chair",
"companyName": "Bill & Melinda Gates Foundation",
"companyId": "163336",
"openToWork": false,
"followerCount": 35000000,
"experiences": [ ... ],
"educations": [ ... ],
"skills": [ ... ]
}
}What teams build with it
CRM enrichment
Fill in role, seniority and employer on records that arrived as nothing but an email and a name, so routing and scoring have something to work with.
Lead qualification
Score inbound signups against your ICP at the moment they arrive, using their current title and company size rather than what they typed into a form.
Recruiting and sourcing
Build candidate records with full work history, education and skills, and re-check them before outreach so you are not contacting someone about a job they left.
Data hygiene
Re-enrich a stale database on a schedule and catch the job changes that quietly turned a third of your contacts into bounces.
Why this endpoint
- Fetched live on every request, never served from a stored copy that ages between refreshes
- Over 100 attributes in one call, including recommendations and test scores that most providers drop
- No account or session of your own to supply, and nothing to keep logged in
- Failed requests are not billed
- 1s median, 1.5s P95, so it fits inside a signup flow rather than a nightly job
Walkthroughs that use it
Each of these takes one job end to end, with the flow and the code.
Questions
- What is profile enrichment?
- Profile enrichment takes a thin record, often just a name and an email or a profile URL, and fills it out with the attributes you actually need: current role, employer, seniority, location, work history and skills. The point is to make a record usable for routing, scoring or outreach without anyone researching it by hand.
- How fresh is the data?
- It is fetched at the moment you call. There is no collection lag and no refresh cycle, because nothing is stored between your requests. That matters most for the fields that change and break workflows when they are wrong, like job title and employer.
- Do I need to supply my own account?
- No. You send a URL and an API key. There is no session to maintain, nothing to keep logged in, and no per-seat cost hiding behind the per-request price.
- What does one enrichment cost?
- One profile call is one credit, from $1.00 per 1,000 on the starter plan and $0.90 per 1,000 from a million credits. Requests that fail are not billed. You can try it with 1,000 free credits and no card.
- Can I enrich in bulk?
- Yes. Call the endpoint concurrently up to your rate limit, which is 5 requests per second on self-serve plans and 10 to 100 or more on request. There is no separate batch API to learn and no job queue to poll.
The rest of the API
Try it on your own data
1,000 free credits, no card. Failed requests are never billed, so a test that does not work costs nothing.