urlstringrequired
Company URL.
https://api.sandbase.ai/v1/api/linkedin/web-v2/company-postsReturns posts from a LinkedIn organization page using the company URL. Supports ordering by top or recent posts and offset or token pagination.
Your output will appear here
Complete the inputs, then click Run.
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.
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.
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/"}'
| Name | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Company URL. |
start | unspecified (pending confirmation) | No | Pagination offset — 0 for page 1, 50 for page 2, and so on. |
sort_by | unspecified (pending confirmation) | No | top or recent. |
pagination_token | unspecified (pending confirmation) | No | Token from the paging object of the previous response. |
sort_by to top or recent to adjust output order.start in increments of 50 or by passing the pagination_token returned in the previous response.Flat price per call. Failed calls, including lookups whose target does not exist, are not charged.
Start building
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/linkedin/web-v2/company-posts" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"url": "https://www.linkedin.com/company/microsoft/"
}
SANDBASE_JSON
)
printf '%s\n' "$result"Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
urlstringrequiredCompany URL.
pagination_tokenanyToken from the `paging` object of the previous response.
sort_byanytop or recent.
startanyPagination offset — 0 for page 1, 50 for page 2, and so on.
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
| API | Price | Response |
|---|---|---|
LinkedIn Company PostsThis API LinkedIn | $0.05 per call | JSON |
LinkedIn | $0.008 per call | JSON |
LinkedIn | $0.05 per call | JSON |
LinkedIn | $0.05 per call | JSON |
LinkedIn | $0.008 per call | JSON |
LinkedIn | $0.05 per call | JSON |
Questions
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.
$0.05 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
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.
A JSON response returned in the same HTTP request (synchronous).
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.
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.
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.