Post › Comments › Replies
Returns the replies under one LinkedIn comment, each with the replier's name, reply text, reaction and reply counts, and timestamps.
Use it after post/comments: pass that comment's comment_id together with the post url to expand a single thread.
50 credits per call.
Paginates by cursor: see Pagination.
Request
- Base URL: https://api.insightsocial.app
- URL: https://api.insightsocial.app/v1/linkedin/post/comments/replies
- Auth: API key in header x-api-key
Query parameters
Full URL of the LinkedIn post. It has to carry the post's ACTIVITY id, either https://www.linkedin.com/feed/update/urn:li:activity:<id> or https://www.linkedin.com/posts/<slug>-activity-<id>-<code>. Every endpoint that lists posts publishes the activity form as post.url, so copy that field rather than rebuilding the URL from post.id, which is not always the activity id.
The parent comment's comment.id from /v1/linkedin/post/comments, or its comment.ext.urn (urn:li:comment:(ugcPost:<post>,<comment>)).
LinkedIn cursor.
Only 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.
Only 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.
Set to 1 to get the price of this call without making it: data.dry_run carries credits_min and credits_max. Nothing is charged.
Response
Success.
Changes
No recorded changes to this operation across all 1 revision of this API.