Threads User Posts API
API 한 번의 호출로 Threads User Posts 데이터를 받아 가세요. Returns the most recent posts from a Threads user. By default you get the window the upstream bundles, typically about 15 posts, for 1 credit. Each post includes the text content, like count, reply count, repost count, media attachments, and creation timestamp. Carousel posts return every slide as an array in `content.media_urls`; video posts return a playable video URL there with the cover frame in `content.thumbnail_url`. Posts filed under a Threads topic tag also carry that tag name at `post.ext.topic_tag` (e.g. `bali`, `dokter gigi`) with its stable id at `post.ext.topic_tag_id`; both are absent on untagged posts, which are the majority. Quote posts are fully resolved: a post that quotes another usually carries no caption or media of its own, so the text and video shown on its page are returned under `post.ext.quoted_post` as `{ id, url, author, text, media_urls, thumbnail_url }`. That attachment belongs to a different account, so it is kept there rather than merged into `content`, and `post.content` always stays this post's own content. The field is absent on posts that are not quote posts. `post.flags.pinned` says whether the author pinned the post to their profile. `post.ext.quote_count` and `post.ext.reshare_count` complete the reshare picture that `engagement.shares` (plain reposts) only starts. A call with no `limit`, or `limit` at 15 or below, is that same window for 1 credit, and `engagement.views` is null on those rows: the default source does not publish a view count on list items. Send `limit` above 15, up to 50, to collect more of the same feed from a second source: measured 09/09/2026 on `@zuck`, the default call returned 15 and `limit=50` returned 32 top-level posts going back to 25/09/2025. That deeper read is metered at 3 credits per post returned, and it is the lane that carries `engagement.views` and `post.author.display_name` (the default window has neither). To get both on the default window instead, send `include=engagement`: each post is looked up on `/v1/threads/post` by its permalink in the same call, and only the view count and the display name are copied onto the row, so nothing already on it changes and `computed.engagement_rate` is filled from the views it gains. It costs 1 credit per post filled, adds 4 to 12 seconds (never more than 15), and a `data.hydration` block reports the rows looked up, filled and served from cache and the credits held and kept. A post the lookup could not fill is refunded and named by `data._warnings: ["engagement_partial"]`. A response is still a single page with no cursor. For a keyword search of older posts, use `/v1/threads/search` with a date window or `/v1/search/everywhere`.
2026년 10월 업데이트SocialCrawl 팀이 직접 관리해요
Threads 사용자의 최근 글을 기본 1크레딧에 보통 15개 반환합니다. limit를 15보다 크게(최대 50) 보내면 같은 피드를 더 깊게 모으고, 조회수와 표시 이름도 채워집니다.
최근 활동을 빠르게 볼 때 사용하세요. 기본 호출은 약 15개의 한 페이지입니다. 같은 엔드포인트에서 더 예전 글까지 가려면 limit를 15보다 크게 보내고, 키워드로 찾으려면 search를 쓰세요. 인용 글은 인용된 원글이 post.ext.quoted_post에 담깁니다.
68개 플랫폼을 병렬로 검색합니다
User Posts API로 무엇을 할 수 있을까요
User Posts 엔드포인트가 통합 스키마와 계산 필드를 담은 Threads 데이터를 한 번의 요청으로 보내드려요. 스크래핑 인프라를 직접 만들거나 유지할 필요가 없어요.
요청 예시
curl -H "x-api-key: YOUR_API_KEY" \
"https://www.socialcrawl.dev/v1/threads/user/posts?handle=zuck&since=2026-09-01&trim=true"import requests
response = requests.get(
"https://www.socialcrawl.dev/v1/threads/user/posts",
params={
'handle': 'zuck',
'since': '2026-09-01',
'trim': 'true',
},
headers={"x-api-key": "YOUR_API_KEY"},
)
data = response.json()const response = await fetch(
"https://www.socialcrawl.dev/v1/threads/user/posts?handle=zuck&since=2026-09-01&trim=true",
{
headers: { "x-api-key": "YOUR_API_KEY" },
},
);
const data = await response.json();함께 보내면 좋은 파라미터
since=2026-09-01이 날짜 이후에 올라온 게시물만 반환합니다. 매일 조회할 때 새 게시물이 있는 페이지만 과금됩니다.trim=true가격은 같습니다. 용량이 큰 원본 필드를 빼서 응답이 가벼워집니다.
파라미터
| 파라미터 | 필수 | 설명 |
|---|---|---|
| handle | 예 | Threads username without the @ symbol |
| since | 아니오 | Only posts published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Older posts 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`. Pinned posts sit out of date order and never end the walk. The page still costs what a page costs, so a daily poll pays for the pages it walks and no more. |
| stop_at_id | 아니오 | The id (`post.id`) or URL (`post.url`) of the newest post you already hold. The page stops just before it: that post and everything after it are left off, `next_cursor` is not returned, and `pagination.stopped_at` is `known_id`. A pinned post never counts as the stop point. If it is not on this page the page is returned in full with its cursor, so keep walking. `pagination.stopped_at` is `end` when the list ran out first and `null` while there is more to walk. |
| 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 15, because the deeper source has no trimmed mode. |
| limit | 아니오 | How many posts to collect, 1 to 50. Leave it off, or send 15 or less, and nothing changes: you get the bundled window for exactly 1 credit. Above 15 the posts come from a deeper source and the call is metered at 3 credits per post actually returned, so an account with only 20 public posts costs 60 credits however high you set this. |
| include | 아니오 | Send `engagement` to fill `engagement.views` and `post.author.display_name` on each post of the default window by looking it up on `/v1/threads/post` in the same call. 1 credit per post filled from a fresh lookup (15 at most); posts served from that lookup's cache (10 minutes) and posts it could not fill are free. Adds 4 to 12 seconds, never more than 15. One token only: `engagement`. Beside a `limit` above 15 it costs nothing, because those rows already carry both fields. (engagement) |
| 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 User Posts API는 무엇을 돌려주나요
모든 응답은 하나의 통합 스키마를 따라요. 크레딧을 쓰기 전에 어떤 필드가 돌아오는지, 실제 응답 본문 그대로 확인해 보세요.
응답 예시 보기
{
"success": true,
"platform": "threads",
"endpoint": "/v1/threads/user/posts",
"data": {
"items": [
{
"post": {
"id": "3996155940894885511",
"url": "https://www.threads.com/@zuck/post/Dd1MqfcG0aH",
"content": {
"text": "We believe superintelligence will create significant new opportunities for all people and businesses. Meta already serves billions of people at scale and helps hundreds of millions of businesses reach customers. Today we are starting the next major pillar of our business, Meta Enterprise Platform, to help businesses use AI to grow and transform in new ways as well.",
"media_urls": null,
"thumbnail_url": null,
"duration_seconds": null
},
"author": {
"username": "zuck",
"display_name": null,
"avatar_url": "https://scontent-atl3-1.cdninstagram.com/v/t51.82787-19/825322135_17989325280103224_1252773933700107438_n.jpg?stp=dst-jpg_s150x150_tt6&efg=eyJ2ZW5jb2RlX3RhZyI6InByb2ZpbGVfcGljLmRqYW5nby4xMDgwLmMyIn0&_nc_ht=scontent-atl3-1.cdninstagram.com&_nc_cat=100&_nc_oc=Q6cZ2gHAvvgkHO46pUE5q2vnmLUY0pl3DdUZUNRT5E_7gpcGIKrJYr7l1iiarldDUU1sIOw&_nc_ohc=zzy0VpJKOQMQ7kNvwERh1-I&_nc_gid=fg32RurBuZNT2dAjc8sO0A&edm=AA3DLpEBAAAA&ccb=7-5&oh=00_AQOhnegtcwSCQp8FcPfGkgAoXntv2yJUmaxHOEoIUibnbw&oe=6AC595EB&_nc_sid=d92198",
"verified": true
},
"engagement": {
"views": null,
"likes": 2616,
"comments": 2445,
"shares": 162,
"saves": null
},
"flags": {
"nsfw": null,
"spoiler": null,
"pinned": false,
"deleted": false
},
"published_at": "2026-09-28T12:35:32.000Z",
"ext": {
"published_at_epoch": 1790598932,
"quote_count": 150,
"topic_tag": null,
"reshare_count": 174,
"topic_tag_id": null
}
},
"computed": {
"engagement_rate": null,
"language": "en",
"content_category": "other",
"estimated_reach": null,
"vs_creator": {
"ratio": 1.42,
"metric": "likes",
"reason": null
}
}
},
{
"post": {
"id": "3994109866205639942",
"url": "https://www.threads.com/@zuck/post/Ddt7cL5EfUG",
"content": {
"text": "Agrippa said it's time to get back to work 😎",
"media_urls": [
"https://scontent-atl3-1.cdninstagram.com/v/t51.82787-15/823965183_17989304049103224_2823186847710225415_n.webp?_nc_cat=110&ig_cache_key=Mzk5NDA5NjMwNTI0NDIwMTIwNQ%3D%3D.3-ccb7-5&ccb=7-5&_nc_sid=58cdad&efg=eyJ2ZW5jb2RlX3RhZyI6IkNBUk9VU0VMX0lURU0ueHBpZHMuMjE2MC5zZHIucmVndWxhcl9waG90by5DMyJ9&_nc_ohc=K_fp4afjatQQ7kNvwH2Fovp&_nc_oc=Adr8t0CqBhk51DpFoXvBN0y6WlNAA91kXSCIZr9_TLwTAjGIWxSybOyGTkfarC5uTBk&_nc_ad=z-m&_nc_cid=0&_nc_zt=23&_nc_ht=scontent-atl3-1.cdninstagram.com&_nc_gid=fg32RurBuZNT2dAjc8sO0A&_nc_ss=7a22e&oh=00_AQMF3bXQ-J5nTOAVt2dacbGe5N-D3O91MUhHIrWNVdgzhA&oe=6AC5AD45",
"https://scontent-atl3-1.cdninstagram.com/v/t51.82787-15/821972247_17989304061103224_4453555141637471915_n.webp?_nc_cat=106&ig_cache_key=Mzk5NDA5NjMwNTc1NTg1Mjg1OQ%3D%3D.3-ccb7-5&ccb=7-5&_nc_sid=58cdad&efg=eyJ2ZW5jb2RlX3RhZyI6IkNBUk9VU0VMX0lURU0ueHBpZHMuMTYzOC5zZHIucmVndWxhcl9waG90by5DMyJ9&_nc_ohc=0Rs1QdoBv1UQ7kNvwE8x9rv&_nc_oc=Adr8fF1MbaZ6uiEUgDRMGlI-MgbruDe1v1W0ROWxeCM0X4aDgXFq9G5qw323lztDcTo&_nc_ad=z-m&_nc_cid=0&_nc_zt=23&_nc_ht=scontent-atl3-1.cdninstagram.com&_nc_gid=fg32RurBuZNT2dAjc8sO0A&_nc_ss=7a22e&oh=00_AQOA-J2ib-VBaThFhtBNhlYxKCwFPBoIOGemknxQClK3XQ&oe=6AC59C1C"
],
"thumbnail_url": null,
"duration_seconds": null
},
"author": {
"username": "zuck",
"display_name": null,
"avatar_url": "https://scontent-atl3-1.cdninstagram.com/v/t51.82787-19/825322135_17989325280103224_1252773933700107438_n.jpg?stp=dst-jpg_s150x150_tt6&efg=eyJ2ZW5jb2RlX3RhZyI6InByb2ZpbGVfcGljLmRqYW5nby4xMDgwLmMyIn0&_nc_ht=scontent-atl3-1.cdninstagram.com&_nc_cat=100&_nc_oc=Q6cZ2gHAvvgkHO46pUE5q2vnmLUY0pl3DdUZUNRT5E_7gpcGIKrJYr7l1iiarldDUU1sIOw&_nc_ohc=zzy0VpJKOQMQ7kNvwERh1-I&_nc_gid=fg32RurBuZNT2dAjc8sO0A&edm=AA3DLpEBAAAA&ccb=7-5&oh=00_AQOhnegtcwSCQp8FcPfGkgAoXntv2yJUmaxHOEoIUibnbw&oe=6AC595EB&_nc_sid=d92198",
"verified": true
},
"engagement": {
"views": null,
"likes": 5032,
"comments": 497,
"shares": 259,
"saves": null
},
"flags": {
"nsfw": null,
"spoiler": null,
"pinned": false,
"deleted": false
},
"published_at": "2026-09-25T16:50:21.000Z",
"ext": {
"published_at_epoch": 1790355021,
"quote_count": 47,
"topic_tag": null,
"reshare_count": 140,
"topic_tag_id": null
}
},
"computed": {
"engagement_rate": null,
"language": "en",
"content_category": "other",
"estimated_reach": null,
"vs_creator": {
"ratio": 2.74,
"metric": "likes",
"reason": null
}
}
}
],
"total": null,
"_sc_terminal": true,
"creator_baseline": {
"baseline": {
"rows_used": 10,
"median_views": null,
"median_likes": 2226,
"median_comments": 456,
"median_gap_hours": 47.43,
"median_saves_per_view": null,
"median_shares_per_view": null
},
"reason": null,
"rows_used": 10,
"cadence": "measured"
},
"dropped": 0
},
"credits_used": 1,
"request_id": "req_example000000",
"cached": false,
"pagination": {
"next_cursor": null,
"has_more": false,
"page_size": 10,
"stopped_at": "since"
},
"credits_remaining": 9999,
"source": "captured",
"captured_at": "2026-10-02T15:39:56.508Z",
"redacted": true
}통합 응답 구조를 보여 주는 실제 샘플이에요. 필드 값은 조회한 대상에 따라 달라져요.
Threads User Posts 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, 요금제, 기능에 대한 질문과 답변입니다.
문의하기Threads 사용자의 최근 게시물은 어떻게 가져오나요?
각 게시물에는 어떤 필드가 포함되나요?
응답을 간결하게 받을 수 있나요?
영상과 이미지 게시물도 지원하나요?
게시물 데이터는 얼마나 최신인가요?
AI에게 SocialCrawl을 물어보세요
Threads User Posts 데이터, 가져올 준비 되셨어요?
API 키 받고 60초 안에 Threads 데이터를 받아 가세요.
