LinkedIn Post Comments API
LinkedIn 게시물의 댓글을 반환합니다. 작성자 이름과 댓글 본문, 반응 수, 답글 수, 고정·수정 여부, 시각이 붙습니다.
GET /v1/linkedin/post/commentsLinkedIn Post Comments API는 언제 쓰나요
게시물의 최상위 댓글을 볼 때 사용하세요. 댓글 id를 post/comments/replies에 넘기면 스레드 하나가 열립니다.
API 레퍼런스 영문 원문
Returns a paginated list of comments on a LinkedIn post, with commenter identity, text, reaction breakdown, pin/edit flags, and reply counts. LinkedIn shows the newest reply of each thread under its comment, and so does this endpoint: it is in comment.replies, with its own author, text and time. engagement.replies is the thread's full count. When a thread has older replies than the one shown, the comment also carries ext.previous_replies_token; pass it as cursor to /v1/linkedin/post/comments/replies to read the rest, or call that endpoint without cursor for the whole thread. A one-reply thread has no token because its only reply is already in comment.replies. ext.is_submitter is true when the commenter wrote the post (LinkedIn's Author badge). Each comment also carries its own link on comment.url (a reply in comment.replies carries one where LinkedIn sends the reply's own id), the commenter's kind (ext.author_type, user or company) and, where LinkedIn shows them, the commenter's member URN (ext.author_urn), whether the comment is a contribution to a collaborative article (ext.is_contribution) and whether the thread has more replies than comment.replies holds (ext.has_previous_replies); each is null when the source that answered does not send it. A reply's id is LinkedIn's comment id when LinkedIn sends one; otherwise it is a stable id built from the parent comment's id (<parent id>:<8 hex>). When the main sources cannot answer, a backup source answers the same comments: there comment.replies holds every reply LinkedIn shows inline (not only the newest) with LinkedIn's own ids, links and like counts, a company page that commented carries its logo as author.avatar_url and its universal name as author.username, and each comment's ext.reaction_counts and ext.previous_replies_token are null, with engagement.likes still the total; data._warnings says so. If that source's relevance order comes back empty on page 1 of a post that has comments, it lists them newest first and data._warnings says that too. A repost keeps its comments on the original post, and some posts file them under their own post id, which differs from the id in the URL. LinkedIn's newest-first order (sort_order=recent, which since and its aliases set) comes back empty on such a URL, so that order is read from the post the comments are filed under, on every page, and data._warnings says which (a repost, or the post's own id). On any other post whose newest-first order comes back empty while it has comments, they are read in relevance order and listed newest first by date when they fit on one page, otherwise from the backup source's own newest-first order, and data._warnings says which. A post with no comments returns an empty page for free, and that empty answer is cached for 1 hour; send Cache-Control: no-cache to read it again sooner.
75개 플랫폼을 병렬로 검색합니다
Post Comments API로 무엇을 할 수 있을까요
Post Comments 엔드포인트가 통합 스키마와 계산 필드를 담은 LinkedIn 데이터를 한 번의 요청으로 보내드려요. 스크래핑 인프라를 직접 만들거나 유지할 필요가 없어요.
요청 예시
# GET /v1/linkedin/post/comments: 5 credits per page. Cache hits are free and failed calls are refunded.
# Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
# --max-time 24: this endpoint's measured p99 latency x 1.5.
# --retry 3: retries timeouts, 429 and 5xx, honoring Retry-After.
# -o response.json keeps only the final attempt's body.
# One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
# Next page: send pagination.next_cursor back as cursor until pagination.has_more is false.
IDEMPOTENCY_KEY=$(od -An -N16 -tx1 /dev/urandom | tr -d ' \n')
curl -sS --max-time 24 --retry 3 -o response.json \
-H "x-api-key: YOUR_API_KEY" \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
"https://www.socialcrawl.dev/v1/linkedin/post/comments?url=https%3A%2F%2Fwww.linkedin.com%2Ffeed%2Fupdate%2Furn%3Ali%3Aactivity%3A7244804629786419202" && cat response.json# GET /v1/linkedin/post/comments: 5 credits per page. Cache hits are free and failed calls are refunded.
# Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
import os
import random
import time
import uuid
import requests
API_KEY = os.environ.get("SOCIALCRAWL_API_KEY", "YOUR_API_KEY")
TIMEOUT_S = 24 # this endpoint's measured p99 latency x 1.5.
MAX_RETRIES = 3
URL = "https://www.socialcrawl.dev/v1/linkedin/post/comments"
def backoff(attempt):
# Exponential backoff with jitter: about 1 s, 2 s, then 4 s.
return 2 ** attempt * (0.5 + random.random() / 2)
def socialcrawl(params):
# One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
idempotency_key = str(uuid.uuid4())
for attempt in range(MAX_RETRIES + 1):
try:
res = requests.get(
URL,
params=params,
headers={"x-api-key": API_KEY, "Idempotency-Key": idempotency_key},
timeout=TIMEOUT_S,
)
body = res.json()
except (requests.RequestException, ValueError):
# A timeout, a dropped connection or a non-JSON gateway page: retry with the same key.
if attempt == MAX_RETRIES:
raise
time.sleep(backoff(attempt))
continue
if body["success"]:
return body
error = body["error"]
# Branch on error["type"], never on the message text.
if error["type"] == "RESOURCE_NOT_FOUND":
return None # refunded: nothing to read
retry_after = res.headers.get("Retry-After")
# SERVICE_UNAVAILABLE without Retry-After is a withdrawn endpoint: permanent.
permanent = error["type"] == "SERVICE_UNAVAILABLE" and retry_after is None
if not error.get("retryable") or permanent or attempt == MAX_RETRIES:
raise RuntimeError(f"{error['type']}: {error['message']} (request_id {body['request_id']})")
# Retry-After (seconds) wins; otherwise back off.
time.sleep(float(retry_after) if retry_after else backoff(attempt))
params = {
"url": "https://www.linkedin.com/feed/update/urn:li:activity:7244804629786419202",
}
# Walk the list: send pagination.next_cursor back as cursor until has_more is false.
MAX_PAGES = 10 # each page is one call
items = []
for _ in range(MAX_PAGES):
body = socialcrawl(params)
if body is None:
break
items.extend(body["data"]["items"])
page = body.get("pagination") or {}
if not page.get("has_more") or not page.get("next_cursor"):
break
params["cursor"] = page["next_cursor"]
print(f"{len(items)} items")// GET /v1/linkedin/post/comments: 5 credits per page. Cache hits are free and failed calls are refunded.
// Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
const API_KEY = process.env.SOCIALCRAWL_API_KEY ?? "YOUR_API_KEY";
const TIMEOUT_MS = 24_000; // this endpoint's measured p99 latency x 1.5.
const MAX_RETRIES = 3;
type Page = { next_cursor: string | null; has_more: boolean };
type SocialCrawlResponse =
| { success: true; data: any; pagination?: Page; credits_used: number; request_id: string }
| { success: false; error: { type: string; message: string; retryable: boolean }; request_id: string };
const sleep = (ms: number) => new Promise((resolve) => setTimeout(resolve, ms));
// Exponential backoff with jitter: about 1 s, 2 s, then 4 s.
const backoffMs = (attempt: number) => 2 ** attempt * 1000 * (0.5 + Math.random() / 2);
async function socialcrawl(url: URL) {
// One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
const idempotencyKey = crypto.randomUUID();
for (let attempt = 0; ; attempt++) {
let res: Response;
let body: SocialCrawlResponse;
try {
res = await fetch(url, {
headers: {
"x-api-key": API_KEY,
"Idempotency-Key": idempotencyKey,
},
signal: AbortSignal.timeout(TIMEOUT_MS),
});
body = (await res.json()) as SocialCrawlResponse;
} catch (error) {
// A timeout, a dropped connection or a non-JSON gateway page: retry with the same key.
if (attempt >= MAX_RETRIES) throw error;
await sleep(backoffMs(attempt));
continue;
}
if (body.success) return body;
// Branch on error.type, never on the message text.
if (body.error.type === "RESOURCE_NOT_FOUND") return null; // refunded: nothing to read
const retryAfter = res.headers.get("Retry-After");
// SERVICE_UNAVAILABLE without Retry-After is a withdrawn endpoint: permanent.
const permanent = body.error.type === "SERVICE_UNAVAILABLE" && retryAfter === null;
if (!body.error.retryable || permanent || attempt >= MAX_RETRIES) {
throw new Error(`${body.error.type}: ${body.error.message} (request_id ${body.request_id})`);
}
// Retry-After (seconds) wins; otherwise back off.
await sleep(retryAfter ? Number(retryAfter) * 1000 : backoffMs(attempt));
}
}
const url = new URL("https://www.socialcrawl.dev/v1/linkedin/post/comments");
url.searchParams.set("url", "https://www.linkedin.com/feed/update/urn:li:activity:7244804629786419202");
// Walk the list: send pagination.next_cursor back as cursor until has_more is false.
const MAX_PAGES = 10; // each page is one call
const items: unknown[] = [];
for (let page = 0; page < MAX_PAGES; page++) {
const body = await socialcrawl(url);
if (!body) break;
items.push(...body.data.items);
const next = body.pagination?.next_cursor;
if (!body.pagination?.has_more || !next) break;
url.searchParams.set("cursor", next);
}
console.log(`${items.length} items`);파라미터
| 파라미터 | 필수 | 설명 |
|---|---|---|
| url | 예 | 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>`. A `urn:li:share:` or `urn:li:ugcPost:` URL names a different id for the same post and is rejected with a 400 before any credits are charged, because it cannot be resolved to the post. 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. |
| page | 아니오 | Page number for pagination (default 1). |
| post_type | 아니오 | Upstream post type: 'activity' (default) or 'ugc'. (activity | ugc) |
| sort_order | 아니오 | Comment ordering: 'relevance' or 'recent'. (recent | relevance) |
| since | 아니오 | 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 the page, and the page that reaches one ends the walk: `next_cursor` is not returned and `pagination.stopped_at` is `since`. Sending it sets the newest-first sort shown in this endpoint's sort parameter (any other sort value is a free 400). The page still costs what a page costs, so you pay for the pages you walk and no more. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| until | 아니오 | 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. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
| max_pages | 아니오 | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| max_items | 아니오 | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| max_credits | 아니오 | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |
LinkedIn Post Comments API는 무엇을 돌려주나요
모든 응답은 하나의 통합 스키마를 따라요. 크레딧을 쓰기 전에 어떤 필드가 돌아오는지, 실제 응답 본문 그대로 확인해 보세요.
응답 예시 보기
{
"success": true,
"platform": "linkedin",
"endpoint": "/v1/linkedin/post/comments",
"data": {
"items": [
{
"comment": {
"id": "7336136129479397376",
"url": null,
"parent_id": null,
"post_id": "7244804629786419202",
"text": "Sample comment text (redacted).",
"author": {
"username": "user_cb954f",
"display_name": "user_493d8b",
"avatar_url": null,
"verified": null
},
"engagement": {
"likes": null,
"replies": 0
},
"flags": {
"pinned": false,
"deleted": false
},
"published_at": "2025-06-04T21:05:52.086Z",
"ext": {
"author_id": "user_6de041",
"urn": "user_929792",
"reaction_counts": [],
"is_edited": false,
"previous_replies_token": null,
"author_headline": "user_e4bf49",
"is_submitter": null
}
},
"computed": {
"language": "en"
}
},
{
"comment": {
"id": "7245081891136040961",
"url": null,
"parent_id": null,
"post_id": "7244804629786419202",
"text": "Sample comment text (redacted).",
"author": {
"username": "user_01e9b6",
"display_name": "user_5eed8e",
"avatar_url": null,
"verified": null
},
"engagement": {
"likes": null,
"replies": 0
},
"flags": {
"pinned": false,
"deleted": false
},
"published_at": "2024-09-26T14:48:49.959Z",
"ext": {
"author_id": "user_b0cb8f",
"urn": "user_ad43d2",
"reaction_counts": [],
"is_edited": false,
"previous_replies_token": null,
"author_headline": "user_1e15b8",
"is_submitter": null
}
},
"computed": {
"language": "en"
}
}
],
"total": null,
"comment_recency": {
"policy_version": "d09-1",
"n": 3,
"counted": 3,
"abstained": 0,
"share_last_24h": 0,
"share_later_half": null,
"too_few": true,
"stage": "unknown",
"order": "default",
"recent_share_is_floor": true,
"receipts": []
},
"dropped": 0
},
"credits_used": 5,
"request_id": "req_example000000",
"cached": false,
"pagination": {
"next_cursor": "sc.eyJ2IjoyLCJjIjoiMiIsImUiOiJsaW5rZWRpbi9wb3N0L2NvbW1lbnRzIiwicCI6InBhZ2UifQ",
"has_more": true,
"page_size": 3
},
"credits_remaining": 9999,
"source": "captured",
"captured_at": "2026-10-02T15:38:13.114Z",
"redacted": true
}통합 응답 구조를 보여 주는 실제 샘플이에요. 필드 값은 조회한 대상에 따라 달라져요.
LinkedIn Post Comments API는 어떻게 동작하나요
API 키와 함께 GET 요청을 보내면, 통합 스키마와 계산 필드를 담은 깔끔한 JSON이 돌아와요.
메서드
GET
응답 형식
JSON
소셜 미디어 데이터를 몇 초 만에 수집하는 방법
개발자를 위한 가장 빠른 소셜 미디어 스크래핑 API. 월간 활성 사용자 100억 명 이상을 포괄하는 75개 플랫폼에서 프로필, 게시물, 댓글, 분석 데이터를 수집하세요.
모든 플랫폼을 하나의 스키마로
동일한 응답 구조로 75개 플랫폼을 조회하세요. 연동은 한 번이면 충분합니다.
단순 수집을 넘어 계산된 필드 제공
엔드포인트가 해당 지표를 지원하고 계산에 필요한 원본 값이 있을 때, 정규화된 레코드에 engagement_rate, estimated_reach, content_category, language를 함께 담아 바로 활용할 수 있습니다.
코드 한 줄 쓰기 전에, 데이터부터
Visual Data Explorer에 URL만 붙여넣으면 결과 카드와 정형화된 테이블, CSV 내보내기를 바로 사용할 수 있습니다.
import requests
response = requests.get(
'https://www.socialcrawl.dev/v1/tiktok/profile',
params={'handle': 'charlidamelio'},
headers={'x-api-key': 'sc_YOUR_API_KEY'}
)
data = response.json(){
"success": true,
"platform": "tiktok",
"data": {
"author": {
"username": "charlidamelio",
"followers": 152400000
},
"engagement": {
"likes": 12400000000,
"engagement_rate": 0.087
},
"metadata": {
"language": "en",
"content_category": "lifestyle"
}
}
}자주 묻는 질문
API, 요금제, 기능에 대한 질문과 답변입니다.
문의하기LinkedIn 게시물의 댓글은 어떻게 받나요?
댓글을 관련순이나 최신순으로 정렬할 수 있나요?
모든 댓글은 어떻게 페이지네이션하나요?
이 엔드포인트 요금은 얼마인가요?
각 댓글은 어떤 필드를 주나요?
댓글을 소셜 리스닝에 쓸 수 있나요?
AI에게 SocialCrawl을 물어보세요
LinkedIn Post Comments 데이터, 가져올 준비 되셨어요?
API 키 받고 60초 안에 LinkedIn 데이터를 받아 가세요.
