Get comments a profile has written

Fetch the comments a member has made, in the order the feed returns them, each paired with the full context of the post it was written on (text, author, media and engagement counts). This is the inverse of GET /api/v1/post/comments, which takes a post and returns the comments left on it. count is a ceiling, not a promise: a page can come back with fewer items while more remain, so page while hasMore is true rather than stopping on a short page.

get/api/v1/profile/comments

Request

  • Base URL: https://api.fetchin.io
  • URL: https://api.fetchin.io/api/v1/profile/comments
  • Auth: API key in header X-API-Key

Query parameters

profileUrlOrUrnstring required
Example:urn:li:fsd_profile:ACoAAA8BYqEBCGLg_vT_ca6mMEqkpp9nVffJ3hc

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.

countinteger

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.

startinteger

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.

paginationTokenstring

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

paginationTokenstring

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

hasMoreboolean

Whether more comments are available.

Example response

{
  "comments": [
    {
      "commentText": "Congratulations to the whole team.",
      "commentUrn": "urn:li:comment:(urn:li:activity:7486820978292072449,7486901233445109760)",
      "activityUrn": "urn:li:activity:7486901262013677568",
      "commenter": {
        "name": "Bill Gates",
        "subtitle": "Chair, Gates Foundation and Founder, Breakthrough Energy",
        "url": "https://www.linkedin.com/in/williamhgates",
        "profilePictureUrl": "https://media.licdn.com/dms/image/...",
        "profileId": "ACoAAA8BYqEBCGLg_vT_ca6mMEqkpp9nVffJ3hc"
      },
      "post": {
        "id": "urn:li:activity:7486820978292072449",
        "shareUrn": "urn:li:share:7486820977348739072",
        "postUrn": "7486820978292072449",
        "postType": "image",
        "resharedPostUrn": "urn:li:activity:7513737675791646720"
      }
    }
  ]
}

Changes

No recorded changes to this operation across all 1 revision of this API.