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 · 價格