GET /v1/threads/user/posts
Threads User Posts API
Returns a Threads user's most recent posts, usually about 15. Send limit above 15 (up to 50) to collect more of the same feed, with view counts and display names filled in.
10–1,650 credits, metered · single call · failed calls free · 10 free calls to start
curl "https://api.insightsocial.app/v1/threads/user/posts?handle=zuck" \-H "x-api-key: $INSIGHTSOCIAL_API_KEY"
When to use it
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.
Parameters
Query parameters for GET /v1/threads/user/posts. Send your key in the x-api-key header.
| Name | 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 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. 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. |
| 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. Adds 4 to 12 seconds, never more than 15. One token only: engagement. |
Response fields
The same unified schema every platform returns, so code written for Threads works on the other eight. A field the platform did not provide is null and listed in unavailable.
| Field | Type | Notes |
|---|---|---|
| id | string | An identifier, always a string. Never parse it as a number: several platforms use ids above 2^53. |
| url | string | null | |
| kind | string | null | The format of the post. Format words only, never a platform name. short = short-form vertical video (a reel, a TikTok, a YouTube Short). |
| content.text | string | null | |
| content.media_urls | array | null | |
| content.thumbnail_url | string | null | |
| content.duration_seconds | number | null | |
| author.id | string | null | |
| author.username | string | null | |
| author.display_name | string | null | |
| author.avatar_url | string | null | |
| author.verified | boolean | null | |
| engagement.views | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| engagement.likes | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| engagement.comments | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| engagement.shares | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| engagement.saves | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| flags.nsfw | boolean | null | |
| flags.spoiler | boolean | null | |
| flags.pinned | boolean | null | |
| flags.deleted | boolean | |
| flags.likes_hidden | boolean | null | |
| flags.comments_hidden | boolean | null | |
| flags.shares_hidden | boolean | null | |
| flags.views_hidden | boolean | null | |
| flags.saves_hidden | boolean | null | |
| published_at | string | null | ISO-8601 timestamp in UTC, ending in Z. |
| language | string | null | The content's language as the platform states it, e.g. en, pt-BR. Detected languages come later (§7.1). |
| ext | object | null | Platform-specific fields, snake_case. |
Every field, error and example is in the Threads User Posts API reference.
How much does the Threads User Posts API cost?
Metered: 10–1,650 credits a call. The ceiling is reserved when the call starts and you are charged what it actually read.
Failed calls are free
A call that errors or finds nothing costs 0 credits.
Know the price first
Add dry_run=1 and the response quotes the call without making it. Nothing is charged.
One balance
API calls and Chrome extension exports share the same credits, on the free plan too.
Threads User Posts API: frequently asked questions
Send GET /v1/threads/user/posts with the handle parameter and your key in the x-api-key header. Returns a Threads user's most recent posts, usually about 15. Send limit above 15 (up to 50) to collect more of the same feed, with view counts and display names filled in.
Metered: 10–1,650 credits a call. The ceiling is reserved when the call starts and you are charged what it actually read. A call that errors or finds nothing costs 0 credits, and an answer from the shared cache costs 2. Pro's 10,000 monthly credits cover about 1,000 calls at 10 credits each. Add dry_run=1 to see the price of a call without making it.
No. There is no Threads app, OAuth flow or app review. One InsightSocial API key works for this endpoint and every other platform, and your first 10 calls priced at 100 credits or less are free.
One call returns the posts in the data object of the standard response envelope. Fields the platform did not provide are listed in unavailable, so a null there means unknown, not zero.
You get an error or an empty result, and it costs 0 credits. The API reads public Threads data only, so private accounts and deleted content come back as not found rather than as partial data.
Yes. Add the hosted MCP server at https://api.insightsocial.app/mcp to your AI app and sign in. The assistant finds this endpoint by name, shows its price and calls it with your credits.