Threads User Posts API
Scrape Threads User Posts data with one API call. 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`.
Last updated October 2026Maintained by the SocialCrawl team
Returns a Threads user's most recent posts, usually about 15 for 1 credit. Send limit above 15 (up to 50) to collect more of the same feed, with view counts and display names filled in.
Use it for a recent-activity window of about 15 posts. Set limit above 15 for deeper history on the same feed, or use search for a keyword lookup.
Searching 68 platforms in parallel
What can you do with the User Posts API?
The User Posts endpoint gives you structured Threads data with computed fields in a single request. No scraping infrastructure to build or maintain.
Example Request
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();Parameters worth sending
since=2026-09-01Returns only posts after this date, so a daily poll pays only for the pages with new posts.trim=trueSame price, lighter payload: drops the bulky raw fields.
Parameters
| Parameter | Required | Description |
|---|---|---|
| handle | Yes | Threads username without the @ symbol |
| since | No | 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 | No | 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 | 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 15, because the deeper source has no trimmed mode. |
| limit | No | 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 | No | 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 | 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 User Posts 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/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
}Live sample illustrating the unified response shape. Field values reflect the record you query.
How does the Threads User Posts 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 68 platforms covering 10B+ monthly active users.
One schema, every platform
Query 68 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 use the Threads User Posts API to list a user's feed?
What fields does each Threads post include?
Can I trim the response for lean JSON?
Does the endpoint return video and image posts?
How fresh is the post data?
Ask AI about SocialCrawl
Ready to scrape Threads User Posts data?
Get your API key and start pulling Threads data in under 60 seconds.
