LinkedIn Company Posts

API docs
https://api.sandbase.ai/v1/api/linkedin/web-v2/company-posts

Returns posts from a LinkedIn organization page using the company URL. Supports ordering by top or recent posts and offset or token pagination.

Price
$0.05USD / call
Method
POST
Response
JSON
Parameters
1 required · 3 optional

Playground

Input
Company URL.
Token from the `paging` object of the previous response.
top or recent.
Pagination offset — 0 for page 1, 50 for page 2, and so on.
OutputReady

Your output will appear here

Complete the inputs, then click Run.

API README

The LinkedIn company profile and posts API example separates the two requests and their historical observations. Start with the required company URL; do not infer a pagination token path from another provider's API.

Optional input types are unspecified here and pending product confirmation; the published parameter schema remains authoritative. The exact token extraction path and the behavior when offset and token are sent together also need confirmation before a continuation example. The first-request example sends only url; no sorting or continuation request is demonstrated here.

LinkedIn Company Posts API

Retrieve posts from a company's profile by supplying the organization url. Adjust feed ordering with sort_by and manage multi-page results using start or pagination_token.

Use cases

  • Monitor recent announcements and feed activity from target company pages.
  • Analyze post performance trends by reviewing entries ranked as top content.
  • Aggregate competitor content feeds into marketing intelligence dashboards.

Request

curl -X POST "https://api.sandbase.ai/v1/api/linkedin/web-v2/company-posts" \
  -H "Authorization: Bearer $SANDBASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://www.linkedin.com/company/microsoft/"}'

Parameters

NameTypeRequiredDescription
urlstringYesCompany URL.
startunspecified (pending confirmation)NoPagination offset — 0 for page 1, 50 for page 2, and so on.
sort_byunspecified (pending confirmation)Notop or recent.
pagination_tokenunspecified (pending confirmation)NoToken from the paging object of the previous response.

Notes

  • Set sort_by to top or recent to adjust output order.
  • Paginate using start in increments of 50 or by passing the pagination_token returned in the previous response.

Pricing

Flat price per call. Failed calls, including lookups whose target does not exist, are not charged.

Explore more

Related APIs

All APIs
APIPriceResponse
LinkedIn$0.05 per callJSON
LinkedIn$0.008 per callJSON
LinkedIn$0.05 per callJSON
LinkedIn$0.05 per callJSON
LinkedIn$0.008 per callJSON
LinkedIn$0.05 per callJSON

Questions

FAQ

How do I use the LinkedIn Company Posts API?

Send a POST request to https://api.sandbase.ai/v1/api/linkedin/web-v2/company-posts with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.

How much does the LinkedIn Company Posts API cost?

$0.05 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.

What parameters does the LinkedIn Company Posts API accept?

Required: url (string). Optional: pagination_token (any), sort_by (any) and start (any). The Parameters table and the Playground on this page list every field.

What does the LinkedIn Company Posts API return?

A JSON response returned in the same HTTP request (synchronous).

Do I need a LinkedIn developer account or API key?

No. LinkedIn Company Posts runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for LinkedIn API access separately.

How do I request posts from a known LinkedIn company page?

Send the full LinkedIn company page URL in the required url field, including https://. The first-request example uses only this field. The current README describes sort_by values top and recent; recent is an ordering option, not a freshness guarantee. Check the endpoint reference for the current optional input types before adding sorting or pagination.

Does pagination guarantee all company posts or exactly 50 posts per page?

No complete-history or fixed-page-size guarantee is established here. The README describes start offsets of 0, 50 and onward, or continuation with pagination_token from a previous response. These offsets do not prove that each page contains 50 posts. The exact token extraction path and the behavior when offset and token are sent together need to be confirmed before publishing a continuation example.