Get LinkedIn Comment Replies
View all LinkedIn Data API endpoints →Provide post_id, comment_id and replies_cursor copied from the parent comment's previous_replies_token. All three inputs are required; the cursor is thread-continuation data, not an account login token. The documented data array contains comment, commenter, created_at, urn, num_replies, reaction_counts and edit, pin or author flags, with page, total and has_more. Attach replies to the originating comment rather than merging unrelated discussion threads.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/linkedin-scraper/get-comments-replies API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/linkedin-scraper/get-comments-replies?key=<API_KEY>&comment_id=<comment_id>&post_id=<post_id>&replies_cursor=<replies_cursor>'
Query Result
Use Cases
- Continue a selected feedback thread after the initial comments page.
- Attach additional responses to the correct parent comment in a review tool.
- Collect source-contextual replies for a manual product-feedback summary.
- Keep separate thread continuations isolated during discussion research.
Frequently asked questions
Where do I get replies_cursor?
Copy previous_replies_token from the matching get-post-comments record. The public replies_cursor input forwards that continuation value; do not reuse a cursor from another comment.
Can I request replies using only comment_id?
No. post_id, comment_id and replies_cursor are all required. The documented result supplies reply records, but does not justify inventing a missing continuation input.