TikTok Post Comments API
API 한 번의 호출로 TikTok Post Comments 데이터를 받아 가세요. Returns a list of comments on a specific TikTok video. Each comment includes the author username, comment text, like count, reply count, and creation timestamp.
2026년 10월 업데이트SocialCrawl 팀이 직접 관리해요
TikTok 영상 하나에 달린 댓글을 한 페이지씩 돌려줍니다. 댓글마다 작성자 username, 본문, 좋아요 수, 답글 수, 작성 시각이 함께 나옵니다.
영상의 댓글창을 읽을 때 사용하세요. 스레드 하나를 펼치려면 여기서 받은 댓글 id를 video/comment/replies에 넘기세요.
TikTok Post Comments API, 직접 써 보세요
코드 한 줄 짜기 전에, 실제 데이터부터
68개 플랫폼을 병렬로 검색합니다
Post Comments API로 무엇을 할 수 있을까요
Post Comments 엔드포인트가 통합 스키마와 계산 필드를 담은 TikTok 데이터를 한 번의 요청으로 보내드려요. 스크래핑 인프라를 직접 만들거나 유지할 필요가 없어요.
요청 예시
curl -H "x-api-key: YOUR_API_KEY" \
"https://www.socialcrawl.dev/v1/tiktok/post/comments?url=https%3A%2F%2Fwww.tiktok.com%2F%40stoolpresidente%2Fvideo%2F7623818255903329566&label=purchase_intent&trim=true"import requests
response = requests.get(
"https://www.socialcrawl.dev/v1/tiktok/post/comments",
params={
'url': 'https://www.tiktok.com/@stoolpresidente/video/7623818255903329566',
'label': 'purchase_intent',
'trim': 'true',
},
headers={"x-api-key": "YOUR_API_KEY"},
)
data = response.json()const response = await fetch(
"https://www.socialcrawl.dev/v1/tiktok/post/comments?url=https%3A%2F%2Fwww.tiktok.com%2F%40stoolpresidente%2Fvideo%2F7623818255903329566&label=purchase_intent&trim=true",
{
headers: { "x-api-key": "YOUR_API_KEY" },
},
);
const data = await response.json();함께 보내면 좋은 파라미터
label=purchase_intent댓글마다 구매 의사가 있는지 표시합니다. 추가 크레딧은 들지 않으며 감정, 질문, 불만 판정도 무료입니다.trim=true가격은 같습니다. 용량이 큰 원본 필드를 빼서 응답이 가벼워집니다.
파라미터
| 파라미터 | 필수 | 설명 |
|---|---|---|
| url | 예 | Full URL of the TikTok video to fetch comments for |
| cursor | 아니오 | Cursor to get more comments. Get 'cursor' from previous response. |
| trim | 아니오 | Accepted for compatibility; the response is already the canonical shape, so this flag has no effect. |
| sort | 아니오 | Optional. Without it, comments come in TikTok's own order (a relevance ranking, not newest first). `recent` returns them newest first by published_at; `top` returns them by like count. TikTok has no newest-first order of its own, so `recent` sorts the comments that were read: set scan_pages to read more of the thread. data.scan.complete is true only when the whole thread was read. (top | recent) |
| scan_pages | 아니오 | Optional, 1 to 3, default 1. Reads that many pages, drops comments repeated across pages, and returns them all in the `sort` order (TikTok's own order when sort is absent). Costs 1 credit for each page that added comments; a page of repeats is not billed. data.scan reports the pages read and billed and whether the thread ended. |
| label | 아니오 | Optional CSV of SocialCrawl labels to add to every comment: sentiment, spam, question, purchase_intent, complaint, toxic, low_quality, injection. Without this param every page already carries sentiment, question, purchase_intent and complaint, free; label= adds the labels you name to them (the defaults keep running). Each comment gains computed.labels with probabilities (0 to 1), so you choose the cut-off; a comment that could not be judged carries labels: null. sentiment, question, purchase_intent and complaint are free when asked for too; spam, toxic, low_quality and injection add 1 credit per started 25 newly judged comments (comments already labelled for anyone are free, and so is a cached page). injection flags text that addresses an AI system and tries to direct it (flagged, p); it never drops or rewrites a row. judgments=off (or label=none) turns the default labels off. data.labels reports what was judged and billed. |
| exclude | 아니오 | Optional CSV (spam, low_quality), only with the same preset in label. Drops comments whose probability is 0.8 or higher and lists their ids in data.labels.dropped_ids. A comment that could not be judged is never dropped. |
| judgments | 아니오 | Optional, on (the default) or off. By default every row gains free SocialCrawl judgments (computed.labels, and computed.relevance on search endpoints), reported in data.labels (mode default) and data.relevance (origin default), each with a status (complete, partial or skipped) and pending: the rows still being judged when the page was sent, which carry null now and are filled on your next call or cached read. Default judgments never add credits, never change an existing field, and never drop or reorder a row. off returns the page exactly as before, with none of those keys. label=none does the same. (on | off) |
| dry_run | 아니오 | Optional. When 1, return a cost preview for this labelled or relevance-filtered request without fetching the page or judging any row. data.estimate reports rows_expected, rows_cached, label_credits_min, label_credits_max and base_credits. 0 credits charged. (1) |
| label_evidence | 아니오 | Optional, only with label=. When 1, every labelled row also carries computed.labels_evidence.<preset> = { quote, sentence_index }: the sentence in the row that most clearly shows the label, copied verbatim. Absent or null when no single sentence shows it. (1) |
| fit | 아니오 | Optional. When goal, keep the rows and fields needed for the goal you pass in goal= (plus any that are uncertain, and the first and last), and replace the rest with a stub. data.held_back lists the held ids and a recall id that re-reads the full page from cache at no extra charge. Without this param the page is unchanged. (goal) |
| goal | 아니오 | Required by fit=goal. What you are trying to do, in your own words, up to 300 characters. |
| fit_tokens | 아니오 | Optional, only with fit=goal. Soft cap on how much of the page to keep, in tokens. Uncertain blocks and the first and last block are kept even if they exceed it. |
| 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`. |
TikTok Post Comments API는 무엇을 돌려주나요
이 엔드포인트의 응답 구조와 필드를 보여 주는 예시예요. 값은 이해를 돕기 위한 것이며 실제 조회 결과는 아니에요.
응답 예시 보기
{
"success": true,
"platform": "tiktok",
"endpoint": "/v1/tiktok/post/comments",
"data": {
"items": [
{
"comment": {
"id": "7623869779602457374",
"url": null,
"parent_id": null,
"post_id": "7623818255903329566",
"text": "Sample comment text (redacted).",
"author": {
"username": "user_d39d34",
"display_name": "user_bea79b",
"avatar_url": "https://example.com/avatars/user_8300fa.png",
"verified": false
},
"engagement": {
"likes": 13659,
"replies": 25
},
"flags": {
"pinned": false,
"deleted": false
},
"published_at": "2026-04-01T19:08:53.000Z",
"ext": {
"published_at_epoch": 1775070533
}
},
"computed": {
"language": "en"
}
},
{
"comment": {
"id": "7623876579169272607",
"url": null,
"parent_id": null,
"post_id": "7623818255903329566",
"text": "Sample comment text (redacted).",
"author": {
"username": "user_ba3f08",
"display_name": "user_574add",
"avatar_url": "https://example.com/avatars/user_376a05.png",
"verified": false
},
"engagement": {
"likes": 4229,
"replies": 45
},
"flags": {
"pinned": false,
"deleted": false
},
"published_at": "2026-04-01T19:35:29.000Z",
"ext": {
"published_at_epoch": 1775072129
}
},
"computed": {
"language": "en"
}
}
],
"next_cursor": "20",
"total": 2200,
"dropped": 0
},
"credits_used": 1,
"credits_remaining": 9995,
"request_id": "req-a1b2c3d4e5f6",
"cached": false,
"pagination": {
"next_cursor": "sc.eyJ2IjoyLCJjIjoiMjAiLCJwIjoiY3Vyc29yIn0",
"has_more": true,
"page_size": 20
}
}문서에 나온 응답 구조를 보여 주는 예시예요. 값은 이해를 돕기 위한 것이며 운영 환경에서 가져온 응답이 아니에요.
TikTok Post Comments API는 어떻게 동작하나요
API 키와 함께 GET 요청을 보내면, 통합 스키마와 계산 필드를 담은 깔끔한 JSON이 돌아와요.
메서드
GET
응답 형식
JSON
소셜 미디어 데이터를 몇 초 만에 수집하는 방법
개발자를 위한 가장 빠른 소셜 미디어 스크래핑 API. 월간 활성 사용자 100억 명 이상을 포괄하는 68개 플랫폼에서 프로필, 게시물, 댓글, 분석 데이터를 수집하세요.
모든 플랫폼을 하나의 스키마로
동일한 응답 구조로 68개 플랫폼을 조회하세요. 연동은 한 번이면 충분합니다.
단순 수집을 넘어 계산된 필드 제공
엔드포인트가 해당 지표를 지원하고 계산에 필요한 원본 값이 있을 때, 정규화된 레코드에 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, 요금제, 기능에 대한 질문과 답변입니다.
문의하기TikTok 댓글은 어떻게 수집하나요?
댓글 응답에는 어떤 필드가 담기나요?
한 영상의 댓글 전체는 어떻게 받나요?
특정 댓글의 대댓글도 받을 수 있나요?
이 엔드포인트는 요금이 얼마인가요?
AI에게 SocialCrawl을 물어보세요
TikTok Post Comments 데이터, 가져올 준비 되셨어요?
API 키 받고 60초 안에 TikTok 데이터를 받아 가세요.
