threads

List 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.

get/threads/user/posts

Request

  • Base URL: https://www.socialcrawl.dev/v1
  • URL: https://www.socialcrawl.dev/v1/threads/user/posts
  • Auth: API key in header x-api-key

Query parameters

handlestring required

Threads username without the @ symbol

sincestring

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_idstring

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.

trimboolean

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.

limitinteger

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'engagement'

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.

untilstring

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.

Headers

Cache-Controlstring

Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.

Idempotency-Keystring

Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.

Response

Successful response

successboolean required

Whether the request succeeded

platformstring required

Platform name

endpointstring required

API endpoint path

credits_usedinteger required

Number of credits consumed

credits_remaininginteger nullable required

Current account balance, or null when this response could not establish one. Free cache hits always return null because they do not establish an authoritative post-request balance. An idempotency replay also returns null when its current-balance lookup fails. It is never a fabricated zero, so a zero here means the account really is empty. The authoritative reading is the one on a billed response, which comes straight from the deduction.

request_idstring required

Unique request identifier for support

cachedboolean required

Whether the response was served from cache

idempotent_replayboolean

True only when this response is an idempotency replay

Example response

{
  "success": true,
  "platform": "threads",
  "endpoint": "/v1/threads/user/posts",
  "credits_used": 1,
  "credits_remaining": 4999,
  "request_id": "req-abc123",
  "idempotent_replay": true,
  "meta": {
    "hint": {
      "code": "search_multi",
      "message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
      "method": "GET",
      "path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
    }
  },
  "pagination": {
    "next_cursor": "sc.eyJ2IjoyLCJjIjoiMiIsInAiOiJwYWdlIn0",
    "has_more": true,
    "page_size": 30,
    "stopped_at": "known_id"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.