Skip to main content
GET
Get posts published by a company page

Endpoint

Authentication

Include your API key in the request header:

Parameters

string
required
The company / organization whose posts to fetch. Accepts any of:
  • Company page URL. Example: https://www.linkedin.com/company/microsoft (a trailing slash makes no difference)
  • Public identifier (slug), also fine. Example: microsoft
  • Organization URN. Example: urn:li:fsd_organizationalPage:1035
The slug is the last path segment of a company page URL (/company/<slug>). Either form works — the bare slug or the company/<slug> fragment.Member profile inputs (a /in/<slug> URL or a urn:li:fsd_profile:…) are rejected with a 400 INVALID_PARAMETER — “Expected a company page, not a member profile.” — free of charge. Use Get Posts for people.
string
Accepted as an alternative name for the same value, because Get Posts has always taken company pages under it. Pass either name — when both are given, companyUrlOrUrn wins.
integer
default:"10"
Number of posts to fetch per page.
  • Minimum: 1 — 0 or a negative value is rejected with 400
  • Maximum: 100 — a higher value is clamped, not rejected
  • Default: 10
integer
default:"0"
deprecated
Not supported on this endpoint. This feed is cursor-paginated and ignores offsets, so a non-zero start is rejected with 400 rather than silently returning the first page again. Use paginationToken.
string
Cursor for the next page. Pass back the paginationToken from the previous response, unchanged; omit it to start from the beginning. A value this API did not issue is rejected with 400. Keep paging while hasMore is true.The token carries the source’s ranking session for this feed and stays valid for about one hour. An expired token still returns a page, but that page may overlap the ones you already have — de-duplicate on id.
boolean
default:"false"
Also return the page’s reposts without commentary, which are otherwise filtered out. Same behaviour as on Get Posts: each comes back with postType: "repost", the repost’s own id and date, empty content, no counts of its own, the company as author, repostedBy, and the original post nested under resharedPost with its own counts. Collaborative posts are also returned. true / false (or 1 / 0); any other value is a free 400.
string
default:"top"
The order of the posts.
  • top (default): the page’s own ranking, which is not chronological — see Notes.
  • recent: newest first.
With recent:
  • only the page’s own posts come back, including the ones it addressed to an audience in another language or region. Reposts without commentary are not part of this order, so includeReposts=true with sortBy=recent is a free 400;
  • count is capped at 50 per page;
  • each page is ordered on the exact publication time. The source orders to the minute, so posts published within the same minute can straddle two pages: de-duplicate on id;
  • a walk ends after a few hundred posts;
  • the paginationToken belongs to this order and this company. Pass it back with the same companyUrlOrUrn and sortBy=recent; a token of the other order, or for another company, is a free 400.
Any other value is a free 400.

Response

array
Posts published by the company page: in the page’s own ranking by default (not chronological — see Notes), newest first with sortBy=recent. Each item has the same shape as items from GET /api/v1/posts — see Get Posts for the full field list (id, shareUrn, content, date, reactionCount, commentCount, sharesCount, reactionsByType, images, video, shareUrl, permissions, author, mentions, contentAttributes, resharedPost, and job, event or celebration on those post types, …), so you can reuse the same types in your client code.The fields that matter most on a company feed:
string
Cursor to pass back as paginationToken to fetch the next page. Do not read its presence as “there is more”: decide on hasMore, which is the only end-of-feed signal on this endpoint.
boolean
Whether the feed holds more posts behind this page. Keep paging while it is true; it is false at the end of the feed — see Pagination.
integer
How many rows the feed returned for this page before any filtering — both the reposts the page carries without the organization’s own commentary (unless includeReposts=true keeps them) and any row that is not a post. Compare it with posts.length to tell the two quiet cases apart: a small pageSize means the feed itself ran short, while a full pageSize with few posts means this page was mostly filtered rows and it is worth asking for the next one.

Example Request

Example Response

Posts come back in a page object, not a bare array.

Errors

See Error Handling for the full list of error codes and recommended handling.
  • 400 MISSING_PARAMETER / INVALID_PARAMETER / INVALID_URN
  • 401 INVALID_API_KEY
  • 404 COMPANY_NOT_FOUND
  • 402 QUOTA_EXHAUSTED
  • 429 RATE_LIMITED
  • 500 INTERNAL_ERROR
  • 503 SERVICE_UNAVAILABLE

Pagination

To walk a company’s whole feed:
  1. Make an initial request without paginationToken
  2. If hasMore is true, pass the returned paginationToken into your next request, unchanged
  3. Continue until hasMore is false, which marks the end of the feed
The token carries the source’s ranking session, which lasts about an hour. Walk a feed in one sitting: a token used after it expired still returns a page, but that page can repeat posts you already received, so de-duplicate on id. With sortBy=recent the walk works the same way, and it is the one order where a date is a safe stopping point: to pick up what a page published since your last run, page until you reach a post older than that run (allow a minute of overlap) instead of walking to the end.

Notes

This endpoint consumes 1 credit from your credit balance per API call, regardless of the count parameter value. Errors are free — with one exception: a 404 not found costs 1 credit. See Quotas.
The default order is not chronological. With sortBy=top (the default), the source serves a company page’s posts in its own ranking, so date moves both ways as you read down a page and across pages. In that order, do not use a date as a paging boundary — “stop at the first post older than X” will cut the walk short and miss posts. Page with paginationToken and stop on hasMore.To follow a company’s posts newest first, pass sortBy=recent.count is also a ceiling, not a promise. The feed carries reposts the page made without its own commentary, and those are filtered out of posts (unless you pass includeReposts=true), so a page can hold fewer posts than you asked for — including none at all — while more still remain. A small count makes this likely: a count=3 request on an active company page returned posts: [] with pageSize: 3 and hasMore: true, meaning all three rows were filtered. Read pageSize to tell that apart from a feed that ran dry, and keep paging while hasMore is true.
Each item has the same shape as items from Get Posts, so one set of types and one parser covers both a person’s feed and a company’s.

Use Cases

Competitor monitoring

Track what the accounts you compete with publish, and how their audience responds

Account signals

Spot hiring pushes, launches and funding news on a target account’s own page

Content benchmarking

Compare reaction and comment counts across company feeds in your market

Brand archive

Keep a dated record of everything an organization published, media included

Authorizations

X-API-Key
string
header
required

Query Parameters

companyUrlOrUrn
string
required

The company / organization whose posts to fetch. Accepts a company page URL (example https://www.linkedin.com/company/microsoft; a trailing slash is ignored), a public identifier/slug on its own (also fine; example microsoft), or an organization URN (example urn:li:fsd_organizationalPage:1035). The slug is the last path segment of a company page URL, so pass just the slug, not the /company/ prefix. A member profile input (a /in/<slug> URL or a urn:li:fsd_profile:...) is rejected with a free 400 INVALID_PARAMETER - "Expected a company page, not a member profile." - use GET /api/v1/posts for people.

Example:

"microsoft"

profileUrlOrUrn
string

Accepted as an alternative name for companyUrlOrUrn, because GET /api/v1/posts has always taken company pages under it. Pass either name; when both are given, companyUrlOrUrn wins.

Example:

"https://www.linkedin.com/company/microsoft"

count
integer
default:10

Number of posts to fetch per page (default: 10). A higher value is clamped to 100, or to 50 with sortBy=recent.

Required range: 1 <= x <= 100
start
integer
default:0

Not supported on this endpoint. This feed is cursor-paginated and ignores offsets, so a non-zero value is rejected with 400 rather than silently returning the first page again. Page with paginationToken instead.

Required range: x >= 0
paginationToken
string

Cursor for the next page: pass back the paginationToken from the previous response, unchanged. Omit it to start from the beginning. A value this API did not issue is rejected with 400. Keep paging while hasMore is true. The token carries the source's ranking session and stays valid for about one hour; an expired token still returns a page, but it may overlap the pages you already have, so de-duplicate on id. With sortBy=recent the token belongs to that order and that company: a token of the other order, or for another company, is a free 400.

includeReposts
boolean
default:false

Also return the reposts WITHOUT commentary, which are otherwise filtered out. Each one comes back as the repost itself: postType: "repost", id = the repost's own activity URN, date = when it was reposted, content = "", no counts of its own (reactionCount, commentCount, sharesCount, reactionsByType omitted), the reposting profile or page as author and profile, repostedBy, and the original post nested under resharedPost with its own counts - the same shape a quote repost has. Collaborative posts are also returned when this is on. Accepts true/false (or 1/0); any other value is a free 400. The price does not change.

sortBy
enum<string>
default:top

Order of the posts. top (default) is the source's own ranking, which is not chronological. recent returns the page's own posts newest first, including the ones it addressed to an audience in another language or region; reposts without commentary are not part of this order, so includeReposts=true with sortBy=recent is a free 400. With recent, each page is ordered on the exact publication time, but the source orders to the minute, so posts published within the same minute can straddle two pages: de-duplicate on id. A walk ends after a few hundred posts. Any other value is a free 400.

Available options:
top,
recent

Response

Successfully fetched the company page's posts

posts
object[]

Posts on this page. With the default sortBy=top they come in the order the source ranks them, which is NOT chronological: date moves both ways within and across pages, so never use a date as a paging boundary in that order. With sortBy=recent they come newest first. Same item shape as GET /api/v1/posts. Reposts the page made without its own commentary are filtered out unless includeReposts=true, so a page can hold fewer items than count - including NONE, while hasMore is still true - so read pageSize to tell a page of filtered rows from an exhausted feed, and trust hasMore.

paginationToken
string | null

Cursor to pass back as paginationToken to fetch the next page. Valid for about one hour. Decide on hasMore, not on the presence of this value.

Example:

"dXJuOmxpOmFjdGl2aXR5Ojc0ODUxMDk4ODc2NTQzMjE2NjQ="

hasMore
boolean

Whether the feed holds more posts behind this page. Keep paging while true; false at the end of the feed.

pageSize
integer

How many rows the feed returned for this page before reposts were filtered out of posts. Compare it with the length of posts to tell a feed that ran short from a page that happened to be mostly reposts.

Example:

5