公司数据增强
Use LinkedIn endpoints to turn 公司数据增强 into repeatable API requests with documented inputs and JSON responses.
通过一个 Crawlora API 密钥，将公开的 LinkedIn 公司页、Showcase 页、产品页和产品目录搜索转换为结构化 JSON，用于客户与产品研究。
使用 LinkedIn API 采集公开的公司、Showcase、产品页面和产品目录数据，以结构化 JSON 用于 B2B 研究。
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
使用 LinkedIn API 采集公开的公司、Showcase、产品页面和产品目录数据，以结构化 JSON 用于 B2B 研究。
Use LinkedIn endpoints to turn 公司数据增强 into repeatable API requests with documented inputs and JSON responses.
Use LinkedIn endpoints to turn 产品目录研究 into repeatable API requests with documented inputs and JSON responses.
Use LinkedIn endpoints to turn b2b 产品发现 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.
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.
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.
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.
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.
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 描述组织，Product Pages 展示产品，Showcase Pages 代表品牌、业务部门或项目。Crawlora 提供五条对应的公开数据路由：按 LinkedIn ID 获取公司、产品和 Showcase 详情，以及产品分类发现和产品目录搜索。这些路由不覆盖会员个人资料或需要认证的 Sales Navigator 潜客与线索搜索数据。
使用 /linkedin/company/{id}、 /linkedin/product/{id} 或 /linkedin/showcase/{id}，并传入该路由要求的 LinkedIn ID 或 slug。这些端点不接受任意个人资料 URL 或会员 handle。
调用 /linkedin/product/categories，可选传入 keyword。匹配方式是单词前缀；请复制响应中的 categories[].id，而不要猜分类 slug。
调用 /linkedin/products/search，可选传入 keyword 和/或数值 category_id。start 是 0 至 1199 的卡片偏移量，不是页码；使用上一响应的 next_start 继续。
使用搜索结果中的产品 ID 调用 /linkedin/product/{id}，再与公司或 Showcase 详情组合。total 只在 start=0 时返回；结果的主分类可能不同于搜索所用分类。
FAQ
五条公开实体与目录路由：公司详情、Showcase 详情、产品详情、产品分类发现和产品目录搜索。会员个人资料和需要认证的 Sales Navigator 潜客与线索搜索数据不在此 API 的范围内。
先调用 /linkedin/product/categories，可选传入 crm 等 keyword。把返回的 categories[].id 作为数值 category_id 传给 /linkedin/products/search。LinkedIn 可能跨相关分类展示产品，因此结果的主分类可能不同于请求分类。
start 是 0 至 1199 的卡片偏移量，不是页码。从 0 开始，并在 next_start 存在时复制到下一次请求。total 只在第一页返回；没有后续访客搜索页面时，next_start 会省略。
不可以。已注册路由只覆盖公开 Company、Product、Showcase 页面和公开产品目录；不会登录、读取会员个人资料或访问需要认证的 Sales Navigator 潜客与线索搜索数据。公开产品目录仍可能包含 Sales Navigator 的产品条目。你仍需负责遵守 LinkedIn 条款以及适用于工作流的隐私和数据使用规则。