LinkedIn Profiles
A public LinkedIn profile presents a professional's identity, current role, location, work history, education, skills, and visible audience size. These details support contact enrichment, career-path research, identity checks, and comparison of public profile changes over time.
Features
- Public profile URL inputProcess one or more LinkedIn /in/{slug} URLs without mixing in company pages, posts, or job listings.
- Current professional contextReturn the public name, about text, avatar, location, position, and current company in one normalized record.
- Structured career historyPreserve experience, education, and skills as separate sections for filtering, indexing, and record enrichment.
- Visible audience metricsReturn available follower and connection counts as separate metrics alongside the professional profile fields.
Parameters
| Parameters | Required | Description |
|---|---|---|
urls | Required | Required list of public LinkedIn profile URLs. Every URL must use the /in/{slug} path on linkedin.com or a LinkedIn subdomain. |
How to Use
Start with known profile links, let the profile task finish, then consume career records page by page.
- Keep only public LinkedIn links whose path matches /in/{slug}.
- Send those links in urls to /v1/linkedin/profiles and retain the task_id.
- Check /v1/tasks/{task_id} until profile processing reaches succeeded or failed.
- After success, read data.results.items and follow next_cursor whenever has_more is true.
curl -X POST "https://api.socq.ai/v1/linkedin/profiles" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"urls":["https://www.linkedin.com/in/satyanadella"]}'
# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is trueBest Use Cases
- Contact and candidate enrichment: Add current role, company, location, experience, education, and skills to records linked to known profile URLs.
- Career-path research: Use structured experience and education sections to examine role progression and professional background.
- Public profile monitoring: Compare saved profile snapshots to identify changes in position, current company, skills, or visible audience counts.
Pro Tips
- Normalize and deduplicate /in/ URLs before submission so alternate URL forms do not create repeated profile records.
- Use the returned id as the profile key when available, with url as the fallback for records without an identifier.
- Treat experience, education, skills, and audience counts as optional because a public profile may omit any of them.
- Keep collected_at with each stored snapshot when comparing role or audience changes over time.
Related APIs
Use these APIs when you need a different type of public LinkedIn data.
- LinkedIn Companies API — Normalize public company descriptions, websites, logos, visible audience and employee counts, industries, locations, and specialties.
- LinkedIn Posts API — Collect public post text, authors, visible engagement, media, publication time, type, and hashtags from supported URLs.
- LinkedIn Jobs API — Normalize public job titles, companies, descriptions, locations, qualifications, employment details, application links, and available salary fields.
Combine LinkedIn data with public data from other supported social platforms.