List Threads posts authored by a user · Threads API
Return the posts authored by a Threads user, by username, as a cursor-paginated list. Useful for profiling a creator's content, monitoring a brand, or building an archive.
Try it without an API key: Threads viewer.
Using ChatGPT, Claude Code or another client? See the setup steps
curl https://api.unifapi.com/threads/users/{username}/posts \
-H "Authorization: Bearer $UNIFAPI_KEY"Parameters
- usernamepathrequired
- cursorquery
This operation is part of the Threads API in the social platforms category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.
Use it when a workflow needs Threads public data alongside other social networks, but should still keep one API key, one account balance, and one predictable JSON contract.
Common agent workflows
- Fetch canonical public Threads content for summarization, ranking, monitoring, or enrichment.
- Attach engagement, author, media, and source metadata to an agent workflow.
- Give an AI agent a stable Threads data source without building a per-platform integration.
- Normalize Threads responses into the same UnifAPI envelope used across the catalog.
Unified envelope, platform-native fields
- List-style responses return `data` as an array of top-level records plus optional `pagination` for continuation tokens or cursors.
- The `billing.records_charged` field reports the charged billable-record quantity for the successful response.
- If the workspace balance cannot cover every result, the response can be truncated and `billing.truncated_due_to_balance` tells the caller why.
Response status codes
Billing
This operation charges 1 credit per billable record, with a 1 credit ($0.001) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.
Errors and retries
Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.
Fields on each record in data
A successful List Threads posts authored by a user call returns data as an array; each record carries these fields.
- idstring
- Threads post code (URL slug).
- codestring
- media_idstring
- textstring
- taken_atnumber
- like_countnumber
- image_urlstring
- video_urlstring
- userobject | null
Agents & Skills built on Threads
You rarely call List Threads posts authored by a user by hand. These prebuilt agents and skills already read Threads data inside Claude or Codex — start from one of them, or call this endpoint yourself.
Try it free in the browser
More Threads operations
Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.
Get a Threads user profile by username
Return a Threads user's public profile by username, including display name, bio, follower count, and verification status. Useful as the entry point for any account-level research.
List Threads replies authored by a user
Return the replies a Threads user has authored, by username, as a cursor-paginated list. Useful for understanding how an account engages in conversation beyond its own posts.
List Threads reposts by a user
Return the posts a Threads user has reposted, by username, as a cursor-paginated list. Useful for inferring an account's interests and the content it amplifies.
Get a Threads post by URL
Returns one Threads post by URL with its author, media, counts, the rest of its thread, replies and related posts. Returns `not_found` when the post does not exist.
Resolve a Threads post URL into its numeric media ID
Convert a public Threads post URL into its post code and numeric `media_id`. Accepts threads.com and threads.net links. Useful for normalizing saved links and matching identifiers across datasets. This identifier conversion does not verify that the post still exists or is publicly accessible.
Search Threads users by keyword
Search Threads accounts by keyword, returning matching public profiles. Useful for creator discovery, audience research, and finding accounts active on a topic. Bio and follower count can be empty in search results; fetch the profile for them.