Threads API

Public-data Threads endpoints (Web surface).

When To Use This API

The Threads API is for agent workflows that need public, platform-native data without writing a custom collector for every task. Use it when a prompt needs evidence from live social records, when a Skill needs repeatable enrichment, or when product code needs the same contract an agent discovered through MCP.

This section lists 7 live Threads operations from the canonical OpenAPI spec. Each operation page documents the route, method, parameters, response envelope, pagination behavior when available, and the error vocabulary shared across UnifAPI.

• Fetch public Threads profiles, posts, replies, reposts, and search results for real-time social research.
• Compare recent and top conversations when an agent needs lightweight signal from Meta's text network.
• Keep profile and post lookups in the same UnifAPI envelope as other social APIs for cross-platform workflows.

Agent Contract Notes

Agents usually discover these endpoints with the hosted UnifAPI MCP server, inspect the operation schema, then call only the records needed for the current task. Developers can call the same endpoints over HTTP with an API key, which makes the path from exploratory agent run to production integration direct.

Every successful response uses a stable envelope with a request id, data payload, optional pagination cursor, and billing metadata. Errors use the same closed vocabulary across platforms, so retry logic, user-facing explanations, and cost reporting can stay consistent even when a workflow spans multiple public-data sources.

When you are choosing an operation, start from the public identifier the user already has: a profile username, post id, channel id, subreddit name, search term, or URL-derived slug. Prefer the narrowest endpoint that answers the question, then expand only when the agent needs more evidence. This keeps record usage predictable, makes citations easier to explain, and avoids turning a focused research task into an expensive crawl.

Operations

Search

• GET /threads/search/profiles — Search Threads users by keyword — Search Threads accounts by keyword, returning matching public profiles.
• GET /threads/search/recent — Search recent Threads posts — Search recent Threads posts by keyword, returning matches newest-first as a cursor-paginated list.
• GET /threads/search/top — Search top Threads posts — Search Threads posts by keyword, ranked by engagement, returning the top matches as a cursor-paginated list.

Users

• GET /threads/users/{username}/posts — List Threads posts authored by a user — Return the posts authored by a Threads user, by username, as a cursor-paginated list.
• GET /threads/users/{username}/replies — List Threads replies authored by a user — Return the replies a Threads user has authored, by username, as a cursor-paginated list.
• GET /threads/users/{username}/reposts — List Threads reposts by a user — Return the posts a Threads user has reposted, by username, as a cursor-paginated list.
• GET /threads/users/{username} — 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.