Get a company’s LinkedIn posts
harvestapi.linkedin.company.postsGet LinkedIn company posts by company URL, ID, or universal name.
- Price
- $0.004/callAu prix du fournisseur
- Success rate
- 99,9 %Last 30 days · 46 543 calls
- Latency p50
- 2.2 sp95 5.6 s
- Last verified
- 10 sept. 2026Verified working
GEThttps://toolswitch.dev/v1/tools/harvestapi.linkedin.company.posts?page=1&companyUniversalName=googlePreview- Uses platform quota
- Synchronous response
- Reads public data
Paramètres
Use only the declared query parameters, once each, without a request body. Results are provider-native: inspect element/elements and body status/error; HTTP 200 alone does not prove a hit. Empty results can still be charged.
| Paramètre | Type | Obligatoire | Description | Exemple |
|---|---|---|---|---|
| Paramètres de requête | ||||
page | entier | Facultatif | Page number for pagination | 1 |
company | chaîne | Facultatif | Filter posts by this company URL | |
companyId | chaîne | Facultatif | Filter posts by company ID. It's faster to search by ID | |
postedLimit | chaîne | Facultatif | Filter posts by maximum posted date. Supported values: '24h', 'week', 'month'. Since LinkedIn doesn't offer a way to filter by date, the filtering will be done on our side, due to that the pagination might have incorrect values, because pagination is returned by LinkedIn without applying the postedLimit filter | |
paginationToken | chaîne | Facultatif | Required if it was returned by the previous page. Otherwise the page will always be 1 (on LinkedIn side). Doesn't apply for all queries, usually profile posts return this token | |
scrapePostedLimit | chaîne | Facultatif | Post-Filter posts by maximum posted date. Supported values: '1h', '24h', 'week','month', '3months', '6months', 'year'. This parameter will be applied after receiving results from LinkedIn, the filtering will be done on our side | |
companyUniversalName | chaîne | Facultatif | Filter posts by company universal name (last part in the URL) | google |
- Paramètres de requête
pageentierFacultatifPage number for pagination
Exemple :
1companychaîneFacultatifFilter posts by this company URL
companyIdchaîneFacultatifFilter posts by company ID. It's faster to search by ID
postedLimitchaîneFacultatifFilter posts by maximum posted date. Supported values: '24h', 'week', 'month'. Since LinkedIn doesn't offer a way to filter by date, the filtering will be done on our side, due to that the pagination might have incorrect values, because pagination is returned by LinkedIn without applying the postedLimit filter
paginationTokenchaîneFacultatifRequired if it was returned by the previous page. Otherwise the page will always be 1 (on LinkedIn side). Doesn't apply for all queries, usually profile posts return this token
scrapePostedLimitchaîneFacultatifPost-Filter posts by maximum posted date. Supported values: '1h', '24h', 'week','month', '3months', '6months', 'year'. This parameter will be applied after receiving results from LinkedIn, the filtering will be done on our side
companyUniversalNamechaîneFacultatifFilter posts by company universal name (last part in the URL)
Exemple :
google
Exemples de code
Remplacez $TOOLSWITCH_KEY par la clé créée dans la console.
curl -X GET 'https://toolswitch.dev/v1/tools/harvestapi.linkedin.company.posts?page=1&companyUniversalName=google' \
-H "X-Toolswitch-Key: $TOOLSWITCH_KEY"import os
import requests
response = requests.request(
"GET",
"https://toolswitch.dev/v1/tools/harvestapi.linkedin.company.posts?page=1&companyUniversalName=google",
headers={"X-Toolswitch-Key": os.environ["TOOLSWITCH_KEY"]},
)
response.raise_for_status()
print(response.text)const response = await fetch("https://toolswitch.dev/v1/tools/harvestapi.linkedin.company.posts?page=1&companyUniversalName=google", {
method: "GET",
headers: {
"X-Toolswitch-Key": process.env.TOOLSWITCH_KEY ?? "",
},
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
console.log(await response.text());Cette API de passerelle est en préversion ; son URL et son authentification peuvent changer. Les paramètres de l’exemple sont des données fictives. Les appels sont facturés à $0.004/call, frais de service inclus.