Threads API

Threads User posts API

List a Threads user's recent public posts by username: text, engagement counts, and post URLs.

POST/v1/run/threads.user_posts
Uptime
100.00%
30d · 6 calls
Requests
6
30d · weekly, last 12 wks
Response
5.2s
median · 30d

Provider network

Providers ranked by traffic

Try it

Make your first request

Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.
{
  "data": {
    "posts": [
      {
        "code": "a1b2c3d4",
        "createdUtc": 12.5,
        "id": "a1b2c3d4",
        "likeCount": 12500,
        "quoteCount": 12500,
        "replyCount": 12500,
        "repostCount": 12500,
        "text": "A short example description of this item.",
        "url": "https://example.com/page",
        "username": "alex_rivera"
      }
    ]
  },
  "found": true
}
Response interface
interface ThreadsUserPostsResponse {
  data: {
    posts: {
      code: string;
      createdUtc: number;
      id: string;
      likeCount: number;
      quoteCount: number;
      replyCount: number;
      repostCount: number;
      text: string;
      url: string;
      username: string;
    }[];
  } | null;
  found: boolean;
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

Request, response, and price

Last verified 2026-09-16 · uptime and latency measured over 30d
POST /v1/run/threads.user_posts
curl -X POST https://api.getanyapi.com/v1/run/threads.user_posts \
  -H "Authorization: Bearer $ANYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"handle":"trendspider"}'
FieldTypeExample value
Request body
handlestring"trendspider"The Threads username to list posts for, without the @ prefix.
Response
dataobjectWrapper holding the posts array, or null when nothing was found.
data.postsobject[]The user's recent posts. Populated whenever the provider has data for the entity.
data.posts[].codestringThreads post shortcode.
data.posts[].createdUtcnumberUTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.
data.posts[].idstringPost identifier. Populated whenever the provider has data for the entity.
data.posts[].likeCountintegerNumber of likes on the post.
data.posts[].quoteCountintegerNumber of quote posts.
data.posts[].replyCountintegerNumber of replies to the post.
data.posts[].repostCountintegerNumber of reposts of the post.
data.posts[].textstringPost text content. Populated whenever the provider has data for the entity.
data.posts[].urlstringCanonical URL of the post. Populated whenever the provider has data for the entity.
data.posts[].usernamestringUsername of the author. Populated whenever the provider has data for the entity.
foundbooleanTrue when the user's posts were found; false when the lookup returned nothing.
Price
Price per requestUSD$0.0012
Price /1k reqUSD$1.20

FAQ

About the Threads User posts API

The AnyAPI Threads User posts API returns Threads user posts data as normalized JSON from one POST call to /v1/run/threads.user_posts. List a Threads user's recent public posts by username: text, engagement counts, and post URLs. AnyAPI routes each request across 2 sources and falls back automatically when one fails. It costs from $1.20 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of Threads user posts calls through AnyAPI succeeded, with a median response time of 5.2 seconds across 6 measured calls.

It costs from $1.20 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet, each call draws it down, and a failed request costs $0.

List a Threads user's recent public posts by username: text, engagement counts, and post URLs. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of Threads user posts calls through AnyAPI succeeded, with a median response time of 5.2 seconds across 6 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.