此端点可以帮助您
响应包含公开的公司数据以及后续 API 请求所需的上下文。
何时使用
当输入标识符或参数已知、需要一个可预期的 API 结果时,请使用此方法。
先查看结果和常见工作流,然后再了解参数和可运行的请求示例。
响应包含公开的公司数据以及后续 API 请求所需的上下文。
当输入标识符或参数已知、需要一个可预期的 API 结果时,请使用此方法。
只请求您需要的对象,而无需加载更大的集合。
将 LinkedIn API 结果添加到记录、工作流和内部工具中。
将响应用作相邻方法和多步骤工作流的输入。
两个版本完成相同的任务,接受相同的参数。使用切换按钮比较响应结构,并选择您的客户端所需的版本。
在本页面切换版本,即可在同一文档 URL 下比较响应结构。
V1 和 V2 的身份验证、必填参数和请求结构均相同。实际上,您只需在构建端点路径和解析响应时选择版本。
主要区别在于响应结构。新集成请使用 V2;仅在需要兼容现有客户端契约时保留 V1。
两个版本使用相同的 API 密钥请求头和相同的查询参数。本文档先展示共享的参数集合,然后展示各版本特定的端点路径和代码片段。
| 参数 | 必填 | 类型 | 示例 | 说明 |
|---|---|---|---|---|
screen_name |
是 | str |
microsoft |
LinkedIn company universal name from linkedin.com/company/{screen_name}. Example: microsoft. |
复制确切的端点路径、示例 URL 和代码片段时请选择版本。上方的参数列表保持不变。
GET /api/v2/linkedin.com/company/posts-by-screen-namecurl --request GET \
--url "https://www.scrapestorm.net/api/v2/linkedin.com/company/posts-by-screen-name" \
--header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
--get --data-urlencode 'screen_name=microsoft'
from urllib.parse import urljoin
import requests
BASE_URL = "https://www.scrapestorm.net"
ENDPOINT = "/api/v2/linkedin.com/company/posts-by-screen-name"
HEADERS = {"Accept": "application/json", "X-API-Key": "00000000-0000-4000-8000-000000000000"}
params = {
"screen_name": "microsoft",
}
with requests.Session() as session:
response = session.request(
method="GET",
url=urljoin(BASE_URL, ENDPOINT),
headers=HEADERS,
params=params,
timeout=30,
)
response.raise_for_status()
payload = response.json()
print(payload)
const BASE_URL = "https://www.scrapestorm.net";
const endpoint = "/api/v2/linkedin.com/company/posts-by-screen-name";
const params = new URLSearchParams({
screen_name: "microsoft",
});
const response = await fetch(`${BASE_URL}${endpoint}?${params.toString()}`, {
method: "GET",
headers: {
Accept: "application/json",
"X-API-Key": "00000000-0000-4000-8000-000000000000",
},
});
if (!response.ok) {
throw new Error(`Request failed: ${response.status} ${response.statusText}`);
}
const payload = await response.json();
console.log(payload);
import axios from "axios";
const client = axios.create({
baseURL: "https://www.scrapestorm.net",
timeout: 30000,
headers: {
Accept: "application/json",
"X-API-Key": "00000000-0000-4000-8000-000000000000",
},
});
const params = {
screen_name: "microsoft",
};
const { data: payload } = await client.request({
method: "GET",
url: endpoint,
params,
});
console.log(payload);
<?php
declare(strict_types=1);
use GuzzleHttp\Client;
use GuzzleHttp\Exception\GuzzleException;
$client = new Client([
'base_uri' => "https://www.scrapestorm.net",
'timeout' => 30.0,
'headers' => [
'Accept' => 'application/json',
'X-API-Key' => "00000000-0000-4000-8000-000000000000",
],
]);
$query = [
"screen_name" => "microsoft",
];
try {
$response = $client->request("GET", "/api/v2/linkedin.com/company/posts-by-screen-name", [
'query' => $query,
]);
$payload = json_decode(
(string) $response->getBody(),
true,
512,
JSON_THROW_ON_ERROR
);
var_dump($payload);
} catch (GuzzleException $e) {
throw $e;
}
package main
import (
"encoding/json"
"fmt"
"net/http"
"net/url"
"time"
)
func main() {
baseURL := "https://www.scrapestorm.net"
endpoint := "/api/v2/linkedin.com/company/posts-by-screen-name"
params := url.Values{}
params.Set("screen_name", "microsoft")
req, err := http.NewRequest(
"GET",
fmt.Sprintf("%s%s?%s", baseURL, endpoint, params.Encode()),
nil,
)
if err != nil {
panic(err)
}
req.Header.Set("Accept", "application/json")
req.Header.Set("X-API-Key", "00000000-0000-4000-8000-000000000000")
client := &http.Client{Timeout: 30 * time.Second}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
var payload any
if err := json.NewDecoder(resp.Body).Decode(&payload); err != nil {
panic(err)
}
fmt.Printf("%+v\n", payload)
}
预览保留了关键字段和集合中的前几项,便于您快速浏览响应结构。切换版本会改变 JSON 格式。
此简明 JSON 示例来自 V2 最近一次成功的验证运行。
{
"success": true,
"status": "ok",
"search_context": {
"screen_name": "microsoft"
},
"data": {
"posts": {
"count": 2,
"items": [
{
"url": "https://www.linkedin.com/posts/microsoft_june-activity-7477715981667086336-BV_s",
"created_at": "2026-06-30T13:33:39.256Z",
"post_id": "7477715981667086336",
"entity_urn": "urn:li:activity:7477715981667086336",
"text": "The most meaningful breakthroughs happen when technology is built with people in mind.\n \nThat was the message at Microsoft Build this month, where we announced a host of new too…",
"hashtags": [],
"emails": [],
"posted_time_text": null,
"author": {
"url": "https://www.linkedin.com/company/microsoft",
"entity_id": null,
"name": "Microsoft",
"headline": null,
"author_type": "company",
"avatar_url": null
},
"reaction_count": 1017,
"comment_count": 83,
"repost_count": null
},
{
"url": "https://www.linkedin.com/posts/microsoft-news-and-stories_microsoft-frontier-company-ai-engineering-activity-7478433392762699777-76eY",
"created_at": "2026-07-02T13:04:23.385Z",
"post_id": "7478433392762699777",
"entity_urn": "urn:li:activity:7478433392762699777",
"text": "Introducing Microsoft Frontier Company — built to deliver Frontier Transformation through AI. We're embedding 6k industry and engineering experts in customer organizations to co…",
"hashtags": [],
"emails": [],
"posted_time_text": null,
"author": {
"url": "https://www.linkedin.com/showcase/microsoft-news-and-stories/",
"entity_id": null,
"name": "Microsoft News and Stories",
"headline": null,
"author_type": "company",
"avatar_url": null
},
"reaction_count": 303,
"comment_count": 20,
"repost_count": null
}
]
}
}
}
将本文档作为第一个决策点,然后在将端点接入常规使用之前,继续了解价格、平台覆盖范围和集成规则。
借助这些解答,判断此 API 方法是否适合您的工作流、版本选择和上线计划。
该方法针对公司执行“按显示名称获取帖子”操作。下方的简明响应示例展示了确切的字段结构。
新集成请选择 V2,因为它提供规范化的结构。仅在兼容已使用平台原生格式的客户端时使用 V1。
创建 API 密钥,在请求头中发送它,并提供表格中的必填参数。代码示例中已包含正确的路径和请求结构。