InsightSocial
GET /v1/linkedin/article/comments

LinkedIn Article Comments API

Returns comments on a LinkedIn Pulse article, with commenter identity, text, and timestamp.

50 credits a call · cursor pagination · failed calls free · 10 free calls to start

curl "https://api.insightsocial.app/v1/linkedin/article/comments?url=https%3A%2F%2Fwww.linkedin.com%2Fpulse%2F2024-corporate-climate-pivot-bill-gates-u89mc%2F" \
-H "x-api-key: $INSIGHTSOCIAL_API_KEY"
200 OKJSON
{
"success": true,
"platform": "linkedin",
"endpoint": "/v1/linkedin/article/comments",
"schema_version": "2",
"data": {
"items": [
{
"comment": {
"id": "<string>",
"url": "<string | null>",
"parent_id": "<string | null>",
"post_id": "<string | null>",
"text": "<string | null>",
"author": {
"id": "<string | null>",
"username": "<string | null>",
"display_name": "<string | null>",
"avatar_url": "<string | null>",
"verified": "<boolean | null>"
},
"engagement": {
"likes": "<integer | null>",
"replies": "<integer | null>"
},
"flags": {
"pinned": "<boolean | null>",
"deleted": "<boolean>"
},
"published_at": "<string | null>",
"language": "<string | null>",
"replies": "<array | null>",
"ext": "<object | null>"
}
}
]
},
"pagination": {
"next_cursor": "<string | null>",
"has_more": "<boolean>"
},
"unavailable": [],
"credits_used": "<integer>"
}

When to use it

Use it after article or profile/articles, passing the article URL.

Parameters

Query parameters for GET /v1/linkedin/article/comments. Send your key in the x-api-key header.

NameRequiredDescription
urlYesFull URL of the LinkedIn Pulse article.
pageNo1-based page number. Defaults to 1.
sinceNoOnly rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following next_cursor, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept.
untilNoOnly rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept.
max_pagesNo1 to 50 (default 1). Walk up to this many pages in one call and return the rows from all of them.
max_age_sNoThe oldest cached copy you accept, in seconds. A copy that old or younger is served, with its age in age_s and the X-Cache-Age header. Without it a copy up to 300 seconds old is served. A lower value fetches fresh (billed) when the copy is older, and 0 always fetches live, like Cache-Control: no-cache.
cursorNoThe pagination.next_cursor from the previous page, sent back unchanged. Omit it for the first page.

Response fields

The same unified schema every typed endpoint returns, so code written for LinkedIn reads the other platforms too. A field the platform did not provide is null and listed in unavailable.

FieldTypeNotes
idstringAn identifier, always a string. Never parse it as a number: several platforms use ids above 2^53.
urlstring | null
parent_idstring | nullAn identifier, always a string. Never parse it as a number: several platforms use ids above 2^53.
post_idstring | nullAn identifier, always a string. Never parse it as a number: several platforms use ids above 2^53.
textstring | null
author.idstring | null
author.usernamestring | null
author.display_namestring | null
author.avatar_urlstring | null
author.verifiedboolean | null
engagement.likesinteger | nullA count. null when the platform does not expose it; 0 only when it is really zero.
engagement.repliesinteger | nullA count. null when the platform does not expose it; 0 only when it is really zero.
flags.pinnedboolean | null
flags.deletedboolean
published_atstring | nullISO-8601 timestamp in UTC, ending in Z.
languagestring | nullThe content's language as the platform states it, e.g. en, pt-BR. Detected languages come later (§7.1).
repliesarray | null
extobject | nullPlatform-specific fields, snake_case.

Every field, error and example is in the LinkedIn Article Comments API reference.

How much does the LinkedIn Article Comments API cost?

50 credits per successful call.

  • Failed calls are free

    A call that errors or finds nothing costs 0 credits.

  • Know the price first

    Add dry_run=1 and the response quotes the call without making it. Nothing is charged.

  • One balance

    API calls and Chrome extension exports share the same credits, on the free plan too.

LinkedIn Article Comments API: frequently asked questions

Send GET /v1/linkedin/article/comments with the url parameter and your key in the x-api-key header. Returns comments on a LinkedIn Pulse article, with commenter identity, text, and timestamp.