# Threads User Posts API (https://www.socialcrawl.dev/platforms/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`.

TL;DR: `GET /v1/threads/user/posts` costs 1 credit for the bundled window of about 15 posts, which is what a call with no `limit`, or `limit` at 15 or below, costs. Above 15 the deeper lane is metered at 3 credits per post RETURNED: the call holds `limit x 3` up front (the 50 maximum holds 150) and refunds down to what came back. With `include=engagement` the call also holds 1 credit per post of the window (15) and keeps 1 for each post whose view count or display name it filled from a fresh lookup; posts served from the post lookup's cache (10 minutes) are free and the rest is refunded, so the default window costs 16 at most. Beside a `limit` above 15 the deeper rows already carry both fields, so the 15 are refunded in full and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## 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`. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/threads/user/posts" \
  --data-urlencode "handle=zuck" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I use the Threads User Posts API to list a user's feed?

Send a GET request to /v1/threads/user/posts with the handle parameter (no @ symbol). SocialCrawl returns an array of recent posts including text, like count, reply count, repost count, media attachments, and publish timestamp.

### What fields does each Threads post include?

Every post has its id, permalink, text content, like count, reply count, repost count, quote count, media URLs, author info, pinned flag and published_at timestamp. Field names stay consistent across every SocialCrawl platform. View count is the one exception: Threads publishes it on a single post's page only, so fetch /v1/threads/post for the post you need it on.

### Can I trim the response for lean JSON?

Yes. Pass trim=true and the endpoint returns a compact payload with only the essential fields. Useful when you are embedding Threads posts at scale and want to minimise bandwidth and parsing overhead.

### Does the endpoint return video and image posts?

Yes. Both image and video posts appear in the array with their media URLs and thumbnails. Videos include view counts and, when available, duration, all normalised into the same content.media fields as other platforms.

### How fresh is the post data?

Responses reflect what is publicly visible on Threads at request time. SocialCrawl caches under the post category for a short window so repeated calls for the same handle return instantly without an extra upstream fetch.

See the full Threads API: https://www.socialcrawl.dev/platforms/threads

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- How to list Threads user posts with an API
- What data does the SocialCrawl Threads user/posts endpoint return?