LinkedIn Data APIPublic data · JSON · REST
LinkedIn Data API for public profile, company, and job data
Send a public LinkedIn profile URL, a company domain, or a job keyword and get structured JSON back. EnvoAPI covers profiles, companies, jobs, posts and search through 58 endpoints, one API key and one response shape. No LinkedIn login, no OAuth flow, and 100 free credits to start.
View API docs100 free creditsNo credit card required
EnvoAPI is independent and not affiliated with LinkedIn. It returns public data only.
Coverage
What the LinkedIn data API covers
Five data families sit behind one key. Each has its own page with the full field list, parameters and error behavior.
Profiles
Name, headline, current role, location, experience, education and skills for any public profile. Look up by URL, username or a stored ID. 1 credit per lookup.
fullNameheadlineexperience[]education[]skills[]- 1 credit
Companies
Industry, headcount, headquarters, founding year, specialties and products for any public company page. Look up by URL, slug, website domain or name, then pull its people, posts, open jobs and similar companies.
primaryIndustryemployeeCountheadquartersspecialtiesproducts- 1 credit
Jobs
Search public job postings by keyword, location, experience level and workplace type. Open any posting by URL, or list every open role at a company, newest first.
LinkedIn Jobs APIPosts
Post details, comments and reactions from public post URLs, plus the recent posts, comments and reactions of a profile or company page.
API referenceSearch
Find people, companies, posts and hashtags by keyword. Resolve locations, industries and schools into the IDs that filters need.
LinkedIn search API guide
Lookup routes
Start from the identifier you already have
Pick the route that matches what is in your CRM, spreadsheet or signup form. Every route returns the same data and meta envelope.
| You have | Call | You get | Cost |
|---|---|---|---|
| People | |||
| A profile URL | GET/v1/profiles/details/by-url | Name, headline, current role, location, experience, education, skills and more: 30 fields | 1 credit |
| A profile username | GET/v1/profiles/details/by-username | The same record | 1 credit |
A stored profile ID (profile_…) | GET/v1/profiles/details/by-id | The same record, for scheduled refreshes | 1 credit |
| A person's role, company or school | GET/v1/profiles/search | Matching profiles with IDs you can fetch in full | 1 credit / page |
| Companies | |||
| A company page URL or slug | GET/v1/companies/details/by-urlor by-slug | Company profile: 21 fields | 1 credit |
| A company website domain | GET/v1/companies/by-domain | The company pages tied to that domain, to fetch by slug | 1 credit |
| A company name | GET/v1/companies/search | Up to 10 matches per page, filterable by location, industry and size | 1 credit / page |
| Jobs | |||
| A job keyword and location | GET/v1/jobs/search | Job cards with title, URL, location, company and posting date | 1 credit / page |
| A job URL | GET/v1/jobs/details | Full description, workplace and employment type, open or closed status | 1 credit |
Public contact details (email, phone, websites and social handles a profile shows) come from a separate Profile Contact endpoint at 2 credits per lookup.
Request & response
One request, one response shape
Authentication is one header, sent from your server. The record comes back under data; the credit cost and the status of each section come back under meta.
meta.creditCostand theX-Credits-Remainingheader show what the call cost and what is left.X-RateLimit-Limit,X-RateLimit-RemainingandX-RateLimit-Resetshow your request window; a 429 tells you when to retry.- Errors carry
error.code,error.messageanderror.retryable, so your client knows whether a retry can help. meta.sectionsmarks each profile section complete, empty, incomplete or unavailable, so a null is never ambiguous.
Typed clients for Python, Node.js and Go are on GitHub. Full parameters and schemas are in the API reference.
curl -G "https://api.envoapi.com/v1/profiles/details/by-url" \ -H "Authorization: Bearer $ENVO_API_KEY" \ --data-urlencode "url=https://www.linkedin.com/in/avery-chen-synthetic/"import osimport requestsresponse = requests.get( "https://api.envoapi.com/v1/profiles/details/by-url", headers={"Authorization": f"Bearer {os.environ['ENVO_API_KEY']}"}, params={"url": "https://www.linkedin.com/in/avery-chen-synthetic/"},)profile = response.json()["data"]const url = new URL("https://api.envoapi.com/v1/profiles/details/by-url");url.searchParams.set("url", "https://www.linkedin.com/in/avery-chen-synthetic/");const response = await fetch(url, { headers: { Authorization: `Bearer ${process.env.ENVO_API_KEY}` },});const { data } = await response.json();endpoint := "https://api.envoapi.com/v1/profiles/details/by-url"req, _ := http.NewRequest(http.MethodGet, endpoint, nil)req.Header.Set("Authorization", "Bearer "+os.Getenv("ENVO_API_KEY"))query := req.URL.Query()query.Set("url", "https://www.linkedin.com/in/avery-chen-synthetic/")req.URL.RawQuery = query.Encode()res, err := http.DefaultClient.Do(req){ "data": { "publicId": "profile_7Qf2Ld9xBm4Rt8Nv3Kw6Jz1Ce5Hy0Pa2Su7Kd7V", "username": "avery-chen-synthetic", "fullName": "Avery Chen", "headline": "Revenue operations leader at Northstar Systems", "location": { "displayName": "San Francisco Bay Area", "countryCode": "US" }, "experience": [ { "title": "Head of Sales", "company": { "name": "Northstar Systems" } } ] }, "meta": { "creditCost": 1, "sections": { "experience": "complete", "skills": "incomplete" } }}curl -G "https://api.envoapi.com/v1/companies/by-domain" \ -H "Authorization: Bearer $ENVO_API_KEY" \ --data-urlencode "domain=northstar.com"The response lists the matching company pages with name, slug and LinkedIn URL. Pass the slug to /v1/companies/details/by-slug for the full profile.
Official vs unofficial
Official LinkedIn API vs unofficial LinkedIn data API
LinkedIn’s own APIs let approved applications act on the platform. A public data API reads public records at scale. Most teams need one or the other, and a few need both.
| What you need | Official LinkedIn API | EnvoAPI |
|---|---|---|
| Sign members in to your app | Sign In with LinkedIn using OpenID Connect | Not the use case |
| Run ads or report on campaigns | Marketing Developer Platform, partner approval | Not the use case |
| Publish as a company or manage a page | Community Management API, partner approval | Not the use case |
| Post jobs from an applicant tracking system | Job Posting API, certified partners | Not the use case |
| Read any public profile from its URL | Not offered: the profile API describes the member who signed in | Profile Details by URL, username or ID |
| Firmographics for any public company | Not offered | Company Details by URL, slug or domain |
| Read public job listings at scale | Not offered | Jobs Search and Company Jobs |
| How you get access | OAuth 2.0 plus LinkedIn Partner Program approval | An API key in a header; first call in minutes |
Use the official products when your app needs member sign-in, consent, advertising, page management or job posting. Use a public data API when your system needs structured public profile, company or job data without asking each person to sign in.
Read the full comparison: LinkedIn API: official vs unofficial. EnvoAPI is not an official LinkedIn API.
Use cases
What teams build with it
Each use case is a short chain of calls. The same key and the same response envelope run through all of them.
CRM and signup enrichment
Fill title, company, industry and headcount on contacts and accounts from a saved profile URL or a company domain. Store
publicIdto refresh records later.- domain
/v1/companies/by-domain/v1/companies/details/by-slug
- profile URL
/v1/profiles/details/by-url
Sales intelligence
Resolve an account from its domain, list the people who work there, then read the profiles that matter before outreach.
/v1/companies/by-domain/v1/companies/people/v1/profiles/details/by-id
Recruiting and sourcing
Search people by role, location, company or school, then pull full work history for the shortlist, with
/v1/jobs/searchfor the market around the role./v1/profiles/search/v1/profiles/details/by-id
Hiring signals
See which roles a company opens, where, and whether a posting is a repost or has closed.
/v1/companies/jobs/v1/jobs/details
AI agents and research assistants
A hosted MCP server exposes 40 read-only tools to Claude, ChatGPT, Cursor and other MCP clients. Same credits, same rate limits, same usage reports as the REST API.
MCP server
Market
How EnvoAPI compares with other LinkedIn data APIs
LinkedIn data APIs differ most in how they get the data, so the table groups them by model rather than ranking brands.
Checked 7 October 2026 · confirm on each vendor’s own site
| Model | Example | How access works | Worth checking |
|---|---|---|---|
| Account-based API | Unipile | You connect a LinkedIn account (hosted login, credentials or cookies) and the API reads or acts as that account. Messaging and invitations are included. | Who owns the connected account, and how its limits and health affect your pipeline |
| URL-in scraper API and datasets | Bright Data | You send a profile, company, job or post URL, or discover by name or keyword, and receive the record. Datasets are sold separately. | How pricing is billed (per record, minimum orders) and which fields each input returns |
| Actor marketplace | Apify | You run scrapers built by different publishers. Each actor has its own input and output. | Different schemas per actor, and maintenance that depends on the publisher |
| Unified public data API | EnvoAPI | One API key, one response envelope, and no LinkedIn account in the retrieval path. Public data only. | Fields can be null, and it is not an official LinkedIn API |
For a longer comparison of enrichment providers, read the full provider comparison.
Pricing
LinkedIn data API pricing in credits
Every plan runs on credits and a request-per-minute limit. Start free with 100 credits and no card.
- profile · company · job · search = 1 credit
- public contact data = 2 credits
Free
$0
No subscription
- Credits
- 100 starter credits
- Rate limit
- 10 RPM
- Per 1,000
- n/a
Launch
$49
Per month
- Credits
- 10,000 / month
- Rate limit
- 60 RPM
- Per 1,000
- $4.90
GrowthRecommended
$149
Per month
- Credits
- 50,000 / month
- Rate limit
- 120 RPM
- Per 1,000
- $2.98
Scale
$499
Per month
- Credits
- 250,000 / month
- Rate limit
- 300 RPM
- Per 1,000
- $2.00
- Choose Volume →
Volume
$1,799/month · 1,000,000 credits · 600 RPM · $1.80 per 1,000
- Talk to sales →
Enterprise
2,000,000+ credits · Custom rate limits · SLA, DPA and procurement-friendly invoicing
Top-up packs start at 5,000 credits for $29. Full pricing →
Responsible use
Limits and responsible use
Know what the data is before you build on it.
Public data only
The API returns what a profile, company page or job posting publishes. It does not return private messages, connection lists or anything behind a login.
Fields can be null
A section a page does not publish comes back null, and
meta.sectionssays whether it is complete, empty, incomplete or unavailable.Job postings have a fixed shape
You get title, URL, location, company, posting date, description, workplace and employment type, open or closed status and a repost flag. There is no salary, apply link or applicant count field.
Not an official LinkedIn product
EnvoAPI is independent and is not affiliated with or endorsed by LinkedIn. Do not describe it to your users as official.
Keep the key on your server
Call the API from your backend so the Authorization header never reaches a browser or mobile build.
Your obligations stay yours
Review the platform terms, privacy laws such as GDPR and CCPA, and your own compliance rules, and honor opt-out requests when you use enriched data for outreach. How EnvoAPI handles access, deletion and opt-out requests is described on the Trust and compliance page.
FAQ
LinkedIn data API FAQ
What is a LinkedIn data API?
A LinkedIn data API returns structured data about LinkedIn profiles, companies, jobs and posts as JSON. It comes in two kinds: official LinkedIn products that need member permission, and third-party public data APIs such as EnvoAPI.
Is EnvoAPI an official LinkedIn API?
No. EnvoAPI is an independent service and is not affiliated with or endorsed by LinkedIn. It returns public data only.
Does LinkedIn have an official API for any profile?
Not for arbitrary profiles. Sign In with LinkedIn returns the signed-in member's own name, email and photo. No official endpoint takes another person's profile URL and returns their data.
Do I need a LinkedIn account or OAuth to use it?
No. You send an API key in the Authorization header from your server. No LinkedIn sign-in, consent screen or token exchange is involved.
What data can I get?
Public profiles (30 fields), company pages (21 fields), job postings, posts, comments and reactions, plus people, company and job search. Anything a page does not publish comes back as null.
How much does the LinkedIn data API cost?
A profile, company, job or search request costs 1 credit. New accounts get 100 free credits with no card, and paid plans start at $49 per month for 10,000 credits.
Does it return email addresses or phone numbers?
Not from Profile Details. A separate Profile Contact endpoint returns the public email, phone, websites and social handles a profile shows, when available, for 2 credits per lookup. To find a work email from a name and domain, see the Email Finder API.
What are the rate limits?
From 10 requests per minute on the Free plan to 600 on Volume. Every response carries rate-limit and credit-balance headers, and a 429 tells you when to retry.
Can I use it from AI agents or no-code tools?
Yes. A hosted MCP server exposes 40 read-only tools to Claude, ChatGPT, Cursor and other MCP clients. Any tool that can send an HTTP request with a custom header, such as n8n, Make or Zapier, can call the REST API.
Is it legal to use LinkedIn data?
That depends on your purpose, the platform terms that apply to you and the privacy laws in your markets. EnvoAPI returns public professional data and describes its approach on the Trust page; you remain responsible for how you use the output, so check with your own counsel.
Start building
Start with 100 free credits.
Create a key, make your first call in minutes, and see the JSON in your own pipeline. No credit card required.