Skip to main content
GET
Get comments a profile has written

Endpoint

This endpoint returns the comments a member has made, anywhere — each one paired with the full context of the post it was made on (its text, its author, its media and its engagement counts).
Do not confuse it with Get Post Comments, which goes the other way round: that one takes a post and returns the comments left on it. This one takes a profile and returns the comments that profile wrote.

Authentication

Include your API key in the request header:

Parameters

string
required
The professional profile whose comments to fetch. Accepts any of:
  • Profile URN, recommended for consistency: a profile’s public identifier (slug) can change over time, the URN does not. Example: urn:li:fsd_profile:ACoAAA8BYqEBCGLg_vT_ca6mMEqkpp9nVffJ3hc
  • Public identifier (slug), also fine. Example: williamhgates
  • Profile URL. Example: https://www.linkedin.com/in/williamhgates (a trailing slash makes no difference)
The slug is the last path segment of a profile URL. Pass just the slug, not the /in/ prefix.Member profiles only: a company page URL or URN is rejected with a 400 error, free of charge.
integer
default:"10"
Number of comments 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. Keep paging while hasMore is true.Pass it back verbatim. A token this API did not issue is not rejected — it is forwarded, and the page comes back empty and still costs a credit, so do not construct or edit one.

Response

array
Array of comments the profile wrote, newest first. Each item carries the comment itself, its author, and the post it was written on.
string
Token for fetching the next page of comments. Do not read its presence as “there is more”: decide on hasMore.
boolean
Indicates whether there are more comments to fetch.

Example Request

Example Response

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 PROFILE_NOT_FOUND
  • 402 QUOTA_EXHAUSTED
  • 429 RATE_LIMITED
  • 500 INTERNAL_ERROR
  • 503 SERVICE_UNAVAILABLE

Pagination

To collect a profile’s whole comment history:
  1. Make an initial request without paginationToken
  2. If hasMore is true, use the returned paginationToken in your next request
  3. Continue until hasMore is false — not until a page comes back short

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.
Comments are returned in reverse chronological order (most recent first), and count is a ceiling rather than a promise: a page requested with count=100 routinely comes back with slightly fewer items. A short page is not the end of the feed — keep paging while hasMore is true, and never stop because you received fewer comments than you asked for.
Each item already embeds the post it was written on — its text, author, media and engagement counts — so you rarely need a follow-up call to Get Posts to make a comment actionable.

Use Cases

Buying-intent signals

Spot prospects commenting on your category, your competitors or your own content

Voice of the customer

Mine what a decision maker actually writes, in their own words, for personalized outreach

Network mapping

See whose posts a profile keeps engaging with to infer relationships and influence

Lead scoring

Score leads on how often, how recently and how substantively they comment

Authorizations

X-API-Key
string
header
required

Query Parameters

profileUrlOrUrn
string
required

The professional profile whose comments to fetch. Accepts a profile URN (recommended for consistency, since a profile's public identifier can change over time while the URN does not; example urn:li:fsd_profile:ACoAAA8BYqEBCGLg_vT_ca6mMEqkpp9nVffJ3hc), a public identifier/slug (also fine; example williamhgates), or a full profile URL (example https://www.linkedin.com/in/williamhgates; a trailing slash is ignored). The slug is the last path segment of a profile URL, so pass just the slug, not the /in/ prefix. Member profiles only: a company page URL or URN is rejected with a 400 error, free of charge.

Example:

"urn:li:fsd_profile:ACoAAA8BYqEBCGLg_vT_ca6mMEqkpp9nVffJ3hc"

count
integer
default:10

Number of comments to fetch per page (default: 10). Values above 100 are clamped to 100. This is a ceiling: a page can return slightly fewer items without meaning the feed is exhausted.

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. Pass it back verbatim: a token this API did not issue is NOT rejected here, it is forwarded, and the page comes back empty and still costs a credit. Keep paging while hasMore is true.

Response

Successfully fetched the comments the profile has written

comments
object[]

Comments the profile wrote, newest first.

paginationToken
string

Token for fetching the next page. Only present when more comments are available.

hasMore
boolean

Whether more comments are available.