Social Media API
LinkedIn API
Read public LinkedIn profiles down to experience, skills, and education — plus company pages, employees, jobs, posts, and the Ad Library — across 80+ endpoints in two series.
- Granular profile sub-sections: experience, education, skills, certifications, honors, volunteers
- Company intelligence: employees, jobs, competitors, stock quote, and employee-count ranges
- 80+ endpoints across two series — the most detailed public LinkedIn coverage available
$0.05 free credit on sign-up · no credit card · from $0.001/request
One request, structured JSON
1curl -X GET "https://api.tikhub.io/api/v1/linkedin/web_v2/get_user_profile?username=williamhgates" \2 -H "Authorization: Bearer YOUR_API_KEY"1{2 "code": 200,3 "data": {4 "public_id": "williamhgates",5 "first_name": "First",6 "last_name": "Last",7 "headline": "Sample headline",8 "location": "Seattle, Washington",9 "follower_count": 38000000,10 "connections": 9,11 "experiences": [{ "title": "Co-chair", "company": "Example Foundation" }],12 "skills": ["Leadership", "Philanthropy"]13 }14}Get your API key at user.tikhub.io/dashboard/api — or follow the getting-started guide.
What's in the LinkedIn API
TikHub's LinkedIn API provides two series with 80+ endpoints of public professional data: granular profile sub-sections (experience, education, skills, certifications, honors), company pages with employees, jobs, competitors and stock quotes, post details with comments, reactions and reposts, groups and hashtag feeds, the Ad Library, and people / job / post search.
LinkedIn Web API
LinkedIn Web V2 API
Granular profile sub-sections, not just a name and headline
Most LinkedIn data tools return a flat profile. TikHub's 80+ endpoints break profiles into the sub-sections that matter for enrichment and recruiting — experience, education, skills, certifications, honors, volunteers — and add company pages with employees, job listings, competitors, and even stock quotes. It's structured professional data deep enough to power a CRM-enrichment or talent-intelligence product.
LinkedIn API endpoints
A reference of the most-used LinkedIn endpoints. Browse the full set in the API reference or the documentation.
LinkedIn Web API
The widest coverage — profiles with every sub-section, company pages and people, posts with comments/reactions/reposts, groups, search (people / jobs / posts / schools / locations), and the LinkedIn Ad Library.
LinkedIn Web V2 API
An alternative series with optional profile sub-section flags, top cards and discovery, deeper company intelligence (competitors, stock quote, CTAs, employee-count ranges, grouped locations), and post-by-slug lookups.
Tips & troubleshooting
Hard-won operational notes for working with LinkedIn data in production.
LinkedIn has a lower per-user RPS — retry on 400
LinkedIn is heavily defended, so the per-user request rate (RPS) is lower than on other platforms. Transient 400 errors are expected under that pressure — if you hit one, just retry the request (a short backoff helps). Build a couple of automatic retries into your client and the occasional 400 stops being a problem.
Fetch only the sub-sections you need
Rather than one giant profile object, the Web V2 series lets you pull experiences, skills, contact info, follower counts, and posts as separate calls. For CRM enrichment that only needs current role and company, fetch the top-card or contact endpoint and skip the rest — it's faster and cheaper than retrieving everything. get_user_profile also accepts optional sub-section flags to compose what you need in one call.
Public IDs vs vanity URLs
LinkedIn profiles are addressed by a public identifier (the slug in linkedin.com/in/<id>). Resolve and store that public ID for anyone you track; vanity URLs can change. Company pages, employees, and job listings hang off the company series, which complements the profile endpoints for full account-based-marketing and talent-intelligence coverage.
It's read-only public data
The LinkedIn API returns publicly visible professional data — it does not send connection requests, messages, or InMail, and it can't see content gated behind a login or a connection. Use it for enrichment, research, and monitoring; for outreach actions you'd use LinkedIn's own tools.
Do I need a LinkedIn developer account?
No. Create a free TikHub account, generate an API key, and call REST endpoints directly — no LinkedIn developer application, app review, or OAuth.
What LinkedIn data can I extract?
Public profiles with granular sub-sections (experience, education, skills, certifications, honors, volunteers), company pages with employees, job listings, competitors and stock quotes, post details with comments and reactions, groups and hashtag feeds, the Ad Library, and people/job/post search.
How much does the LinkedIn API cost?
Pay-as-you-go from $0.001 per request, with automatic daily volume discounts down to $0.0005 at 30,000+ requests/day. New accounts get $0.05 free credit (~50 requests) — no credit card required.
Is using a LinkedIn API like this legal?
TikHub returns publicly available data — the same content anyone can see without logging in. US courts (hiQ v. LinkedIn) have held that scraping public data is not a CFAA violation. That said, LinkedIn's Terms of Service restrict automated access, so account or IP blocks are a real operational risk; TikHub manages that infrastructure for you. You are responsible for how you use, store, and process the data you retrieve.
LinkedIn API: granular public profile and company data in 2026
TikHub's LinkedIn API reads public professional data — profiles broken into experience, skills, and education, plus company pages, employees, jobs, and posts — across 80+ endpoints. Here's how it works, why the granularity matters, and which option fits which job.
How does the LinkedIn API work?
What is the LinkedIn API?
The TikHub LinkedIn API is a RESTful interface that returns structured JSON for public LinkedIn data. Where most LinkedIn tools return a flat profile, this series breaks a profile into granular sub-sections — experiences, education, skills, certifications, honors, contact info, follower counts — and adds company pages with employees, job listings, competitors, and post engagement, across 80+ endpoints.
That depth makes it suitable for building real products: CRM enrichment, talent intelligence, and account-based-marketing data, not just a name and a headline.
How do you access and use it?
Create a TikHub account, generate an API key, and make an HTTP GET request with the key in the Authorization header. Address a profile by its public identifier and fetch the whole profile or just the sub-sections you need; address companies through the company series for employees and jobs. There's no LinkedIn app, OAuth, or partner approval involved.
What are the benefits of using the LinkedIn API?
Why does the granularity matter?
Different products need different slices. CRM enrichment may only want current title and company; a recruiting tool wants the full experience and skills history; an ABM platform wants company employees and job listings. Fetching sub-sections independently means you retrieve (and pay for) exactly what you need, and you can compose richer records than a one-size profile scrape provides.
Who benefits, and what do they save?
B2B sales and marketing teams enriching leads, recruiters and talent-intelligence products mapping skills and movement, and analysts tracking competitor hiring. LinkedIn is heavily defended against scraping, so building and maintaining your own collector is a serious, risky effort; TikHub absorbs that and exposes a stable, structured contract.
What are common use cases and alternatives?
What are the common use cases?
Lead and CRM enrichment from public profiles, talent-movement and org-structure mapping, competitor-hiring analysis via company job listings, and B2B thought-leadership tracking via post engagement. AI teams use the structured profile and company data for entity resolution and enrichment pipelines.
What are the alternatives, and which is best?
LinkedIn's official APIs are tightly gated behind partner programs and don't expose arbitrary public profiles. Numerous scraping tools and data vendors exist, but they vary widely in depth and reliability and many return only flat profiles. For granular, sub-section-level public data through one stable API — without owning the scraping risk — a managed provider like TikHub is the practical choice.
One key, every platform
The LinkedIn API shares its key and JSON format with 15 other platforms — adding Instagram or Douyin is a one-line change.