Threads Post Comments API
Threads가 글과 함께 묶어 주는 답글을 기본 1크레딧에 보통 20개 반환합니다. limit를 25보다 크게(최대 50) 보내면 다른 소스에서 1단계 답글을 더 모읍니다.
GET /v1/threads/post/commentsThreads Post Comments API는 언제 쓰나요
글 URL이 있고 그 아래 반응을 볼 때 사용하세요. 커서 없이 한 묶음만 옵니다. 기본 창이 모자라면 limit를 25보다 크게 보내세요.
API 레퍼런스 영문 원문
Returns the replies on a Threads post. By default you get the window Threads bundles with the post itself, typically about 20 replies, for 1 credit. Each comment carries its text, like count, direct reply count, author handle, display name, avatar and verification status, and creation timestamp. Send limit above 25 to collect more than that window holds, up to 50: measured 07/09/2026 on a post with 1,141 replies, the default call returned 24 and limit=50 returned 50. The deeper read is metered at 1 credit per 5 replies returned. It comes from a different source, but every field is normalised to the same shape and the same id space before it reaches you, so a comment carries the identical comment.id and comment.post_id whatever limit you sent, and raising limit returns more of the same objects rather than a different shape. comment.parent_id stays null on both lanes: nothing upstream says which comment a nested reply answers. A response is still a single page with no cursor. Same upstream call as /v1/threads/post on the default lane, so a post and its replies cost one call each.
75개 플랫폼을 병렬로 검색합니다
Post Comments API로 무엇을 할 수 있을까요
Post Comments 엔드포인트가 통합 스키마와 계산 필드를 담은 Threads 데이터를 한 번의 요청으로 보내드려요. 스크래핑 인프라를 직접 만들거나 유지할 필요가 없어요.
요청 예시
# GET /v1/threads/post/comments: Metered: holds 10 credits per call up front and refunds what the call does not use. 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 14: 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.
IDEMPOTENCY_KEY=$(od -An -N16 -tx1 /dev/urandom | tr -d ' \n')
curl -sS --max-time 14 --retry 3 -o response.json \
-H "x-api-key: YOUR_API_KEY" \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
"https://www.socialcrawl.dev/v1/threads/post/comments?url=https%3A%2F%2Fwww.threads.com%2F%40zuck%2Fpost%2FDZpPDXbCeTt&limit=50&trim=true" && cat response.json# GET /v1/threads/post/comments: Metered: holds 10 credits per call up front and refunds what the call does not use. 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 = 14 # this endpoint's measured p99 latency x 1.5.
MAX_RETRIES = 3
URL = "https://www.socialcrawl.dev/v1/threads/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.threads.com/@zuck/post/DZpPDXbCeTt",
"limit": "50",
"trim": "true",
}
body = socialcrawl(params)
if body is not None:
print(body["data"])// GET /v1/threads/post/comments: Metered: holds 10 credits per call up front and refunds what the call does not use. 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 = 14_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/threads/post/comments");
url.searchParams.set("url", "https://www.threads.com/@zuck/post/DZpPDXbCeTt");
url.searchParams.set("limit", "50");
url.searchParams.set("trim", "true");
const body = await socialcrawl(url);
if (body) console.log(body.data);함께 보내면 좋은 파라미터
trim=true가격은 같습니다. 용량이 큰 원본 필드를 빼서 응답이 가벼워집니다.
파라미터
| 파라미터 | 필수 | 설명 |
|---|---|---|
| url | 예 | Full URL of the Threads post whose replies you want, for example https://www.threads.com/@zuck/post/DZpPDXbCeTt. Both threads.com and threads.net are accepted. |
| trim | 아니오 | Ask the upstream for a stripped record. This is a real shape change, not just less whitespace: a trimmed row carries only the id, text, shortcode, like count, timestamp and author, so media, reply count, share count, view count, topic tag, pinned flag and quoted post all come back null. Same 1 credit either way, so send it only when the text and the like count are all you need. Ignored when `limit` is above 25, because the deeper source has no trimmed mode. |
| limit | 아니오 | How many replies to collect, 1 to 50. Leave it off, or send 25 or less, and nothing changes: you get the bundled window for exactly 1 credit. Above 25 the replies come from a deeper source and the call is metered at 1 credit per 5 replies actually returned, so a post with only 12 replies costs 3 credits however high you set this. Threads publishes only part of a large conversation without a login, so a post declaring a thousand replies will still return about 50. |
| 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 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. `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`. |
Threads Post Comments API는 무엇을 돌려주나요
모든 응답은 하나의 통합 스키마를 따라요. 크레딧을 쓰기 전에 어떤 필드가 돌아오는지, 실제 응답 본문 그대로 확인해 보세요.
응답 예시 보기
{
"success": true,
"platform": "threads",
"endpoint": "/v1/threads/post/comments",
"data": {
"items": [
{
"comment": {
"id": "3920732800241693703",
"url": "https://example.com/redacted",
"parent_id": null,
"post_id": "3920731152608519405",
"text": "Sample comment text (redacted).",
"author": {
"username": "user_31d736",
"display_name": "user_d1f39c",
"avatar_url": "https://example.com/avatars/user_d98cbd.png",
"verified": false
},
"engagement": {
"likes": 2135,
"replies": 32
},
"flags": {
"pinned": false,
"deleted": false
},
"published_at": "2026-06-16T11:03:13.000Z",
"ext": {
"published_at_epoch": 1781607793
}
},
"computed": {
"language": "en"
}
},
{
"comment": {
"id": "3920780620280555692",
"url": "https://example.com/redacted",
"parent_id": null,
"post_id": "3920731152608519405",
"text": "Sample comment text (redacted).",
"author": {
"username": "user_fdcf76",
"display_name": "user_757a8b",
"avatar_url": "https://example.com/avatars/user_139f51.png",
"verified": true
},
"engagement": {
"likes": 1022,
"replies": 12
},
"flags": {
"pinned": false,
"deleted": false
},
"published_at": "2026-06-16T12:38:13.000Z",
"ext": {
"published_at_epoch": 1781613493
}
},
"computed": {
"language": null
}
}
],
"total": null,
"comment_recency": {
"policy_version": "Sample comment text (redacted).",
"n": 10,
"counted": 10,
"abstained": 0,
"share_last_24h": 0,
"share_later_half": null,
"too_few": false,
"stage": "unknown",
"order": "default",
"recent_share_is_floor": true,
"receipts": []
},
"dropped": 0
},
"credits_used": 1,
"request_id": "req_example000000",
"cached": false,
"pagination": {
"next_cursor": null,
"has_more": false,
"page_size": 10
},
"credits_remaining": 9999,
"source": "captured",
"captured_at": "2026-10-02T13:09:14.735Z",
"redacted": true
}통합 응답 구조를 보여 주는 실제 샘플이에요. 필드 값은 조회한 대상에 따라 달라져요.
Threads 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, 요금제, 기능에 대한 질문과 답변입니다.
문의하기Threads 게시물 댓글은 어떻게 가져오나요?
답글마다 어떤 정보가 담기나요?
Threads 댓글 API로 20개보다 많이 받을 수 있나요?
요금은 얼마인가요?
커서로 다음 페이지를 넘길 수 있나요?
AI에게 SocialCrawl을 물어보세요
Threads Post Comments 데이터, 가져올 준비 되셨어요?
API 키 받고 60초 안에 Threads 데이터를 받아 가세요.
