LinkedIn 数据 API | API 文档

# LinkedIn Data API

Read member and company profiles, posts, job details, job search results, and comments through 13 authenticated LinkedIn Web V2 endpoints.

## Authentication

Send your API Hop API key in the Authorization header. Access depends on enabled gateways and your key permissions; documentation does not confirm production availability.

```http
Authorization: Bearer YOUR_API_KEY
```

## Requests

Synchronous operations use GET query parameters without a body. Unknown fields and duplicate scalar fields are rejected. Only fields marked as arrays accept repeated keys, for example company_ids=1035&company_ids=1441. Preserve IDs and cursors as strings; do not convert large identifiers to JavaScript numbers. Optional empty values are omitted.

```bash
curl --get "https://api.apihop.ai/v1/linkedin/web-v2/users/profile" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  --data-urlencode "url=https://www.linkedin.com/in/williamhgates/"
```

## Billing

For synchronous operations: Member profiles, company profiles, and post details cost $0.008 (8000 credits) per successful request. The other five operations cost $0.05 (50000 credits). These are default customer prices; account-specific prices take precedence. Every requested page is billed separately, not per item. Upstream failures release the reservation. Settlement failures do not trigger another upstream call.

## Pagination and limits

For synchronous operations: Member posts return only the latest 50 items: start and pagination_token have no effect, even when the response contains a token. Company posts use start=0, 50, 100, ...; pagination_token has no effect. Job search uses start=0, 25, 50, .... Comments support page (starting at 1) and pagination_token. There is no automatic pagination. Requests time out after 60 seconds with no automatic retries. The supplier warns that resource constraints can cause intermittent failures.

## Scope

Eight synchronous Web V2 operations and five asynchronous task operations are available. Create profile, company, or post tasks with POST and a JSON url field. Creation returns HTTP 202 and a decimal platform task ID as a string. GET status and result reads require the same tenant and are free; unknown, foreign-tenant, and other-product tasks return 404. Status omits result; result is null before COMPLETED. Each task reserves its price at creation and charges once on success ($0.008 / 8000 credits by default). Failure or a 30-minute timeout releases the reservation. Background polling runs every 5 seconds; pending responses include Retry-After: 5. Results are stored in the platform job. Use the platform ID, never a supplier task ID. An uncertain submission is not automatically repeated. A completed task returns result.records. Integers beyond the JavaScript safe range are stored and returned as decimal strings. Examples are illustrative, not live acceptance results.

[Complete reference](https://apihop.ai/en/docs/api-reference/linkedin/reference)

## Responses

For synchronous operations: The native JSON code/data envelope and numeric precision are preserved. Response shapes vary by operation. HTTP 200 alone is not success: business errors, including error/error_code records, are rejected. A successful empty result is billable. This is an illustrative response, not a live acceptance result.

```json
{"code":200,"data":[]}
```

## Errors

HTTP 400: invalid parameters; 401: invalid authentication; 402: insufficient credit; 403: denied gateway access; 405: unsupported method; 408: cancellation; 429: rate limit; 502/503/504: supplier failure, unavailable configuration, or timeout. Keep X-Request-Id for troubleshooting.

## Sources

Checked on 2026-10-31 against the official OpenAPI V5.3.2 and current endpoint prices. These sources describe the contract and prices, not successful live verification of every endpoint.

[TikHub](https://docs.tikhub.io/4592766m0) · [OpenAPI](https://api.tikhub.io/openapi.json) · [Prices](https://api.tikhub.io/api/v1/tikhub/user/get_all_endpoints_info)

通过 13 个需要鉴权的 LinkedIn Web V2 接口查询用户与公司资料、帖子、职位详情、职位搜索结果和评论。

鉴权

在 Authorization 请求头中发送 API Hop API Key。可用性取决于已启用的网关和密钥权限；文档不代表生产环境已经开放。

http

Authorization: Bearer YOUR_API_KEY

请求

同步操作使用 GET 查询参数，不接受请求体。未知字段与重复的标量字段会被拒绝。只有标记为数组的字段允许重复键，例如 company_ids=1035&company_ids=1441。标识和游标须保留为字符串，不要将大整数标识转为 JavaScript 数字。可选空值会被省略。

bash

curl --get "https://api.apihop.ai/v1/linkedin/web-v2/users/profile" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  --data-urlencode "url=https://www.linkedin.com/in/williamhgates/"

计费

同步操作：用户资料、公司资料和帖子详情每次成功请求为 $0.008（8000 credits），其余 5 个操作为 $0.05（50000 credits）。这是默认客户价，账户专属价格优先。每次请求的分页单独计费，不按条目数收费。上游失败会释放预扣，结算失败不会触发第二次上游调用。

分页与限制

同步操作：用户帖子只返回最新 50 条：start 和 pagination_token 均无效，即使响应中存在令牌也不能翻页。公司帖子使用 start=0、50、100 等偏移，pagination_token 无效。职位搜索使用 start=0、25、50 等偏移。评论支持从 1 开始的 page 和 pagination_token。接口不会自动翻页，60 秒超时且不自动重试。供应商提示资源紧张可能造成间歇性失败。

范围

支持 8 个同步 Web V2 操作和 5 个异步任务操作。使用 POST 和包含 url 的 JSON 创建用户资料、公司资料或帖子详情任务，返回 HTTP 202 及字符串形式的平台十进制任务 ID。GET 状态和结果接口只允许本租户读取且免费；不存在、其他租户或其他产品的任务均返回 404。状态响应不含 result；完成前结果为 null。创建时预占，成功后仅结算一次，默认 $0.008 / 8000 credits；失败或 30 分钟超时释放预占。后台每 5 秒轮询，处理中响应含 Retry-After: 5。结果保存在平台任务中。只能使用平台 ID，不能传供应商任务 ID；提交结果不确定时不会自动重提。完成后数据位于 result.records。超出 JavaScript 安全范围的整数以十进制字符串存储并返回。示例仅用于说明，不是真实验收结果。

完整接口参考

响应

同步操作：保留原始 JSON 的 code/data 结构与数字精度，各接口响应结构不同。HTTP 200 本身不代表成功：业务错误以及含 error/error_code 的错误记录会被拒绝。成功的空结果仍会计费。以下仅为说明性响应，不是真实验收结果。

json

{"code":200,"data":[]}

错误

HTTP 400：参数无效；401：鉴权失败；402：余额不足；403：无网关权限；405：方法不支持；408：请求取消；429：限流；502/503/504：供应商故障、配置不可用或超时。排查时请保留 X-Request-Id。

来源

于 2026-10-31 核对官方 OpenAPI V5.3.2 与当前端点价格。来源证明接口契约和价格，不代表每个端点均已通过真实调用验收。

TikHub · OpenAPI · 价格