Threads Post Comments API
Returns the replies Threads bundles with a post, usually about 20 for 1 credit. Send limit above 25 (up to 50) to collect more first-level replies from a second source.
GET /v1/threads/post/commentsLast updated November 2026Maintained by the SocialCrawl team
When to use the Threads Post Comments API
Use it to read the reaction under a post you already have the URL for. It is one window with no cursor. Set limit above 25 when the bundled window is not enough.
From the API reference
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.
Searching 69 platforms in parallel
What can you do with the Post Comments API?
The Post Comments endpoint gives you structured Threads data with computed fields in a single request. No scraping infrastructure to build or maintain.
Example Request
# 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);Parameters worth sending
trim=trueSame price, lighter payload: drops the bulky raw fields.
Parameters
| Parameter | Required | Description |
|---|---|---|
| url | Yes | 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 | No | 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 | No | 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 | No | 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 | No | 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`. |
What does the Threads Post Comments API return?
Every response follows one unified schema. Here is a real, unmodified response body, so you can see the exact fields you get back before spending a credit.
Example response
{
"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
}Live sample illustrating the unified response shape. Field values reflect the record you query.
How does the Threads Post Comments API work?
Send a GET request with your API key and get back clean, structured JSON in our unified schema. Supported computed fields are populated when the source provides the required inputs.
Method
GET
Response
JSON
How do you scrape social media data in seconds?
The fastest social media scraping API for developers. Scrape profiles, posts, comments, and analytics from 69 platforms covering 10B+ monthly active users.
One schema, every platform
Query 69 platforms with identical response structures. Write your integration once.
Computed fields, not just scraped
When an endpoint supports these metrics and the source provides the required inputs, the normalized record includes engagement_rate, estimated_reach, content_category, and language. Ready to use.
See your data before you code
Visual Data Explorer. Paste any URL, get rich result cards, sortable tables, CSV export.
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"
}
}
}Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usHow do I get comments on a Threads post with an API?
What fields does each Threads reply include?
Can the Threads comments API return more than 20 replies?
How much does the Threads comments API cost?
Is there a cursor to page through Threads replies?
Ask AI about SocialCrawl
Ready to scrape Threads Post Comments data?
Get your API key and start pulling Threads data in under 60 seconds.
