Company enrichment
Use LinkedIn endpoints to turn company enrichment into repeatable API requests with documented inputs and JSON responses.
Collect public LinkedIn company and showcase pages, resolve product pages, and search the public product directory as structured JSON with one Crawlora API key for account and product research workflows.
Use a LinkedIn API to collect public company, showcase, product-page, and product-directory data as structured JSON for B2B research.
Endpoint families
4
Documented params
12
Examples
5
Live catalog snapshot
Active endpoints
5
Methods
GET
Required params
8
Schema refs
5
{
"platform": "LinkedIn",
"endpoint": "linkedin-product-categories",
"method": "GET",
"path": "/linkedin/product/categories",
"auth": "apiKey"
}Related use cases
Use cases
Use a LinkedIn API to collect public company, showcase, product-page, and product-directory data as structured JSON for B2B research.
Use LinkedIn endpoints to turn company enrichment into repeatable API requests with documented inputs and JSON responses.
Use LinkedIn endpoints to turn product directory research into repeatable API requests with documented inputs and JSON responses.
Use LinkedIn endpoints to turn b2b product discovery into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live LinkedIn endpoint catalog — 5 endpoints, 12 documented request parameters, and 5 published response schemas — the same catalog Docs and Playground run against.
5 documented LinkedIn endpoints, grouped into 4 request families — Product, Company and Products, plus 1 more.
12 request parameters are documented across those LinkedIn endpoints, 8 of them required — the full input contract is public before you write any integration code.
5 of the 5 LinkedIn endpoints ship a recorded example response, and 5 carry a documented response schema — you can code against the real JSON before the first request.
LinkedIn endpoints document their error responses (400, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
5 hosted MCP tools back the LinkedIn endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/linkedin/product/{id}
/linkedin/company/{id}
/linkedin/products/search
/linkedin/showcase/{id}
Endpoint catalog
/linkedin/company/{id}Returns a LinkedIn company page by its company `id`. The response has the name, headline, about text, industry, company size, employee count on LinkedIn, follower count, founding year, headquarters, locations, specialties, website, logo, Products section cards, affiliated and similar pages, and recent updates with reactions and comment counts.
Response notes
- The service follows at most one permanent (`301` or `308`) canonical redirect to a validated HTTPS LinkedIn company URL. A successful response's `link` contains that final URL. - Login/authwall targets, unrelated hosts, redirect chains and malformed canonical URLs remain upstream errors. A failed canonical target does not establish that the originally requested company is missing. - `products` contains Product Page cards visible in the company's Products section. Each card includes its name, LinkedIn URL, logo, and category when LinkedIn exposes those fields. Path parameters: - `id`: required. LinkedIn Company ID.
Sampled 14 Oct 2026: 1 item, 2 fields filled in every item. is_primary: true in 1 of 1.
MCP tool linkedin_company
/linkedin/product/{id}Returns a LinkedIn product page by its product `id`. The response has the name, about text, category, owning organization, external link, logo, cover image, media items, featured customers with industry and follower count, and lists of other and similar products.
Sampled 14 Oct 2026: 6 items, 5 fields filled in every item. link: linkedin.com; logo: media.licdn.com.
MCP tool linkedin_product
/linkedin/product/categoriesReturns the standardized product categories accepted by the products/search endpoint's category_id filter. With a keyword, returns matching categories from LinkedIn's own category search. Without one, returns every known category.
Response notes
- `categories[].id` is the numeric id to pass as `category_id` to `/linkedin/products/search`. - `categories[].link` is the category's own public LinkedIn page. - Results are sorted alphabetically by `name`. - The full (no-keyword) list changes rarely and may be served from a cache for up to a week.
Sampled 14 Oct 2026: 4 items, 5 fields filled in every item. link: linkedin.com.
MCP tool linkedin_product_categories
/linkedin/products/searchReturns one page of LinkedIn's public product directory search results, optionally scoped to a keyword and/or category. Keyword matching is on word prefixes. start is an upstream card offset advanced by the previous response's next_start; LinkedIn's guest search stops returning results at offset 1200.
Response notes
- `total` is only populated on the first page (`start=0`) and is the result count for the same keyword/category scope. - `next_start` is present when another page exists and omitted once LinkedIn's guest search stops returning results. - `logo` is an empty string when a card has no product image. - `category_name` and `category_link` describe each product's own primary category as listed on LinkedIn, which can differ from the requested `category_id` (a product filed under "Electronic Health Records (EHR) Software" can still appear in the Healthcare CRM category results). `category_link` is an empty string when LinkedIn names the category without linking it.
Sampled 14 Oct 2026: 10 items, 8 fields filled in every item. link: linkedin.com; description: median 323 characters.
MCP tool linkedin_products_search
/linkedin/showcase/{id}Returns a LinkedIn showcase page by its showcase page `id`. The response has the name, headline, about text, industry, follower count, employees on LinkedIn, headquarters, locations, specialties, website, logo, Products section cards when present, affiliated and similar pages, and recent updates with reactions and comment counts.
Sampled 14 Oct 2026: 62 items, 2 fields filled in every item, 2 not. link: linkedin.com and 4 other hosts.
MCP tool linkedin_showcase
Related APIs
Business & Market Intelligence
Turn public GitHub ecosystem signals into structured data for developer-market research, open-source intelligence, recruiting, and AI-agent workflows.
Business & Market Intelligence
Collect public TrustMRR startup marketplace and leaderboard data as normalized JSON for startup research, SaaS discovery, and market intelligence workflows.
Business & Market Intelligence
Add website and competitive intelligence signals from SimilarWeb to research pipelines.
How to scrape LinkedIn
LinkedIn Pages describe organizations, Product Pages highlight products, and Showcase Pages represent a brand, business unit, or initiative. Crawlora exposes five matching public-data routes: company, product, and showcase detail by LinkedIn ID, plus product-category discovery and product-directory search. These routes do not cover member profiles or authenticated Sales Navigator prospecting and lead-search data.
Use /linkedin/company/{id}, /linkedin/product/{id}, or /linkedin/showcase/{id} with the LinkedIn ID or slug required by that route. These endpoints do not accept an arbitrary profile URL or member handle.
Call /linkedin/product/categories with an optional keyword. Matching uses word prefixes; copy categories[].id from the response instead of guessing a category slug.
Call /linkedin/products/search with an optional keyword and/or numeric category_id. start is a card offset from 0 to 1199, not a page number; advance with the previous response's next_start.
Search results provide product IDs for /linkedin/product/{id}; company and showcase detail add organization context. The search total appears only at start=0, and a result's primary category can differ from the category used to find it.
On 2026-10-30 /linkedin/company/openai returned follower_count 12,077,701, industry Research Services and a company_size band, but num_of_employees_on_linkedin 0, so a zero employee count is a missing value. /linkedin/product/categories for crm returned 4 categories.
Agent skills
Install a Crawlora agent skill and your agent can pull LinkedIn data as JSON through the documented API, without writing a scraper. These skills cover LinkedIn:
Researches public LinkedIn company, product, and showcase pages via the Crawlora API. Look up known IDs or discover and search the public product…
npx skills add github.com/Crawlora-org/crawlora-skills --skill linkedin-researchReconcile company and brand identities across Crawlora public domains, LinkedIn profiles, SEC registrants, and employer records. Use to deduplicate…
npx skills add github.com/Crawlora-org/crawlora-skills --skill company-identity-reconciliationResearches public profiles, posts, trends, and Facebook Marketplace listings across Instagram, TikTok, Threads, Bluesky, X, Pinterest, LinkedIn…
npx skills add github.com/Crawlora-org/crawlora-skills --skill social-media-researchFAQ
Five public entity and directory routes: company detail, showcase detail, product detail, product-category discovery, and product-directory search. Company and showcase responses can include organization fields and updates; product responses and search results cover public product-page metadata. Member profiles and authenticated Sales Navigator prospecting and lead-search data are outside this API's scope.
First call /linkedin/product/categories, optionally with a keyword such as crm. Pass a returned categories[].id as the numeric category_id on /linkedin/products/search. A result can list a different primary category from the requested category because LinkedIn may surface products across related categories.
start is an upstream card offset from 0 through 1199, not a page number. Begin at 0 and copy next_start into the next request when it is present. total is populated only on the first page, and next_start is omitted when no later guest-search page is available.
No. The registered routes cover public Company, Product, and Showcase pages plus the public product directory. They do not log in, read member profiles, or access authenticated Sales Navigator prospecting and lead-search data; the public product directory can still include a Sales Navigator product listing. You remain responsible for LinkedIn's terms and any privacy or data-use rules that apply to your workflow.