LinkedIn Public Data API
Retrieve public LinkedIn profile, company, post, and job data from known URLs, with normalized identity, career, company, content, engagement, and job fields.
Available LinkedIn APIs
Use Profiles for a person, Companies for an organization, Posts for known public content, or Jobs for a public job detail URL.
What LinkedIn data can you retrieve?
SocQ converts known public LinkedIn URLs into normalized records for enrichment, recruiting research, content analysis, and data products.
Professional profiles
Retrieve public identity, role, location, visible audience, experience, education, and skills from /in/ URLs.
Company pages
Retrieve descriptions, websites, logos, visible counts, industries, company size, locations, and specialties from /company/ URLs.
Post content
Resolve supported post URLs into text, author, media, publication time, post type, hashtags, and visible engagement.
Job details
Retrieve role, company, description, location, seniority, employment type, industry, application details, and available salary fields.
SocQ vs LinkedIn APIs
SocQ resolves supported public LinkedIn URLs. LinkedIn's official APIs are designed for authorized member, organization and partner integrations.
| Capability | SocQ | LinkedIn APIs |
|---|---|---|
| Primary use | Collect public profile, company, post and job records from known URLs | Build authorized member, organization, marketing or partner integrations |
| Customer OAuth | SocQ API key; no customer LinkedIn OAuth | OAuth 2.0, product permissions and often LinkedIn approval |
| Starting input | Supported public LinkedIn URL | Authorized account context, LinkedIn URNs or resource IDs |
| Create or manage content | Not supported | Supported for eligible members and organizations with required permissions |
| Response format | Normalized SocQ records | Native LinkedIn REST objects |
How the LinkedIn API works
Profiles, Companies, Posts, and Jobs use the same asynchronous task and paginated result workflow.
1. Submit public URLs
Send a urls array to the API matching the LinkedIn path and save the returned task_id.
2. Track the task
Poll /v1/tasks/{task_id} until processing is complete.
3. Retrieve the results
Read data.results.items and use next_cursor while has_more is true.
Authenticate with your SocQ API key and submit one or more public /in/ URLs. Companies, Posts, and Jobs follow the same task flow.
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 trueCommon LinkedIn API use cases
Lead and account enrichment
Add public professional and company context to profile or company URLs already in your workflow.
Recruiting research
Compare selected public profiles and job listings with consistent role, company, location, employment, and salary fields.
Content and campaign analysis
Resolve selected post URLs into content, author, media, publication time, and collection-time engagement.
Research and data products
Use consistent LinkedIn records in warehouses, search indexes, classifiers, review queues, and dashboards.
Limits and public-data policy
SocQ returns publicly accessible LinkedIn data as it appears when the task runs.
- Every API starts from a known public URL. These APIs do not search LinkedIn for people, companies, posts, or jobs.
- Visible counters and changing page fields are snapshots anchored to collected_at, not real-time feeds.
- Optional fields may be null or empty when they are not published or visible during collection.
- The APIs read public data only and do not connect to, publish for, or manage LinkedIn accounts.
LinkedIn API frequently asked questions
What is the LinkedIn API?
The LinkedIn API is a set of SocQ endpoints that converts known public profile, company, post, and job URLs into normalized records for each resource.
Which LinkedIn API should I choose?
Use Profiles for /in/ URLs, Companies for /company/ URLs, Posts for supported post paths, and Jobs for /jobs/view/ URLs.
Can I search LinkedIn with these APIs?
No. Each API requires a known public URL and resolves that specific person, company, post, or job resource.
How does task processing work?
Submit a POST request, poll /v1/tasks/{task_id}, then read data.results.items and continue with next_cursor while has_more is true.
Are the results complete or real time?
Results are snapshots of publicly visible fields at collection time. They do not provide complete history or continuous real-time coverage.
How is LinkedIn data collection priced?
Profiles cost 2.5 credits per returned result, Companies cost 2, Posts cost 1, and Jobs cost 0.8.