What this endpoint helps with
The response includes public Company data and context needed for subsequent API requests.
When to use it
Use this method when an input identifier or parameter is known and one predictable API result is required.
Retrieve Company data from LinkedIn through the focused “Posts by screen name” operation and connect it to product workflows.
Use this method when an input identifier or parameter is known and one predictable API result is required.
Review the result and common workflows first, then move to parameters and a working request example.
The response includes public Company data and context needed for subsequent API requests.
Use this method when an input identifier or parameter is known and one predictable API result is required.
Request the object you need without loading a larger collection.
Add the LinkedIn API result to records, workflows, and internal tools.
Use the response as input for adjacent methods and multi-step workflows.
Both versions solve the same job and accept the same parameters. Use the switch to compare the response structure and choose the version your client expects.
Switch versions on this page to compare response structures while keeping the same documentation URL.
Authentication, required parameters, and the request shape stay the same across V1 and V2. In practice, you choose the version when you build the endpoint path and when you parse the response.
The main difference is the response envelope. Use V2 for new integrations and keep V1 only when you need compatibility with an existing client contract.
Use the same API key header and the same query parameters for both versions. This documentation shows the shared parameter set first, then version-specific endpoint paths and code snippets.
| Parameter | Required | Type | Example | Description |
|---|---|---|---|---|
screen_name |
Yes | str |
value |
LinkedIn company universal name from linkedin.com/company/{screen_name}. Example: microsoft. |
Choose a version when you copy the exact endpoint path, example URL, and code snippet. The parameter list above stays the same.
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=value'
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": "value",
}
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: "value",
});
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: "value",
};
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" => "value",
];
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", "value")
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)
}
The preview keeps key fields and the first collection items so you can scan the response shape quickly. Switching versions changes the JSON format.
This compact JSON example comes from the latest successful verification run for 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
}
]
}
}
}
Use this documentation as the first decision point, then move into pricing, platform coverage, and integration rules before you connect the endpoint for recurring use.
Use these answers to decide whether this API method fits your workflow, versioning choice, and rollout plan.
The method performs “Posts by screen name” for Company. The compact response example below shows the exact field structure.
Choose V2 for new integrations because it provides a normalized structure. Use V1 only for compatibility with clients that already consume the platform-native format.
Create an API key, send it in the request header, and provide the required parameters from the table. The code samples already contain the correct path and request structure.