Public profile and tab research
Use Threads endpoints to turn public profile and tab research into repeatable API requests with documented inputs and JSON responses.
Turn public Threads conversations, creator activity, and topic discovery into structured JSON for social listening and research.
Fetch public Threads profiles, posts, replies, media and repost tabs, profile topics, and topic search through documented API endpoints.
Endpoint families
3
Documented params
25
Examples
10
Live catalog snapshot
Active endpoints
10
Methods
GET
Required params
23
Schema refs
10
{
"platform": "Threads",
"endpoint": "threads-search",
"method": "GET",
"path": "/threads/search",
"auth": "apiKey"
}Use cases
Fetch public Threads profiles, posts, replies, media and repost tabs, profile topics, and topic search through documented API endpoints.
Use Threads endpoints to turn public profile and tab research into repeatable API requests with documented inputs and JSON responses.
Use Threads endpoints to turn post and reply analysis into repeatable API requests with documented inputs and JSON responses.
Use Threads endpoints to turn search and topic monitoring into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Threads endpoint catalog — 10 endpoints, 25 documented request parameters, and 10 published response schemas — the same catalog Docs and Playground run against.
10 documented Threads endpoints, grouped into 3 request families — Profile, Post and Search.
25 request parameters are documented across those Threads endpoints, 23 of them required — the full input contract is public before you write any integration code.
10 of the 10 Threads endpoints ship a recorded example response, and 10 carry a documented response schema — you can code against the real JSON before the first request.
Threads endpoints document their error responses (400, 404 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
10 hosted MCP tools back the Threads endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/threads/profile/{username}
/threads/post/{username}/{code}
/threads/search
Endpoint catalog
/threads/searchReturns the public first page of Threads search results for a query. `sort` supports `top` and `recent`; `pagination_limited` marks the logged-out login wall because search has no continuation cursor. Author and date filters in Threads require login and are not exposed here.
Response notes
Returns the first public page of post results visible to logged-out visitors. `sort=recent` maps to Threads' Recent filter; `sort=top` uses the default Top results. Threads does not expose a continuation cursor for this public search view. `pagination_limited` is true when the page shows the login wall for additional results.
Sampled 14 Oct 2026: 21 items, 7 fields filled in every item, 7 not. created_at: 2026-02-09 to 2026-10-13; like_count: 1 to 7,077, median 102.
MCP tool threads_search
/threads/profile/{username}Returns a public Threads profile by `username` (with or without a leading `@`): name, profile URL, biography, avatar URL, `followers_count` and `threads_count`. Counts are derived from the compact figures shown on the profile page. An unavailable profile returns 404.
Response notes
- Counts are converted from the compact values visible on the public profile page. - Returns 404 when the public profile is unavailable and 503 when the public metadata cannot be parsed safely.
Sampled 14 Oct 2026: 7 of 7 fields returned with a value. followers_count: 5,700,000; url: threads.com.
MCP tool threads_profile
/threads/profile/{username}/postsLists public posts from the profile's Threads tab by `username`. Each item has its code, URL, text, creation time, image and video URLs, like, reply, repost and quote counts, reply flag and author. When `has_more` is true, pass `next_cursor` unchanged as `cursor` to fetch the next page; `pagination_limited` is true if Threads withholds a usable cursor.
Response notes
Returns public posts in the profile's Threads tab, including attached topic/community metadata when available. When `has_more` is true, pass `next_cursor` unchanged to retrieve the next page. `pagination_limited` is true if Threads reports more posts but withholds a usable cursor. This tab accepts `username` and the optional pagination `cursor`; the public page exposes no additional sort or filter controls.
Sampled 14 Oct 2026: 10 items, 9 fields filled in every item, 5 not. created_at: 2026-09-25 to 2026-10-12; like_count: 61 to 5,104, median 614.
MCP tool threads_profile_posts
/threads/profile/{username}/mediaReturns the first public page shown on a profile's Media tab. Items include image and video URLs, including carousel attachments, plus post and topic metadata. The logged-out page exposes no continuation cursor or media-type filter; `pagination_limited` reports when additional results are gated by login or lack a supported cursor.
Response notes
Returns the first public page shown on a profile's Media tab. Items preserve their author, topic metadata, and image or video attachments, including carousel items when present. The logged-out tab exposes no continuation cursor or media-type filter. `pagination_limited` is true when Threads shows a login wall for additional items or reports more items without a usable cursor.
MCP tool threads_profile_media
/threads/profile/{username}/repliesReturns the first public page shown on a profile's Replies tab. Each item preserves its actual author and public reply metadata. The logged-out page has no continuation cursor; `pagination_limited` is true when Threads reports more items without a cursor or shows a login wall for additional items.
MCP tool threads_profile_replies
/threads/profile/{username}/repostsReturns the first public page shown on a profile's Reposts tab. Each item preserves the original post author and metadata. `pagination_limited` is true when Threads gates more items behind login or reports more items without a supported cursor.
Response notes
Returns the first public page shown on a profile's Reposts tab. Each item keeps the original post author and attached topic/community metadata when available, making reposts useful for discovering related public profiles. Threads does not expose a logged-out continuation cursor; if the page shows a login wall for more reposts, `pagination_limited` is true.
MCP tool threads_profile_reposts
/threads/profile/{username}/topicsReturns every topic tag listed on a public profile, including the numeric tag id and canonical `name` to pass as `q` to `/threads/search/topics`. Community topics include their community metadata.
Response notes
Returns the complete topic tag list shown on the public profile. Use each item's `name` as `q` and `id` as `tag_id` when calling `/threads/search/topics`. Community topics include the community flag and cluster metadata. The public profile page provides no pagination cursor for this list.
MCP tool threads_profile_topics
/threads/search/topicsReturns the public first page of posts for a topic tag. Discover the required `tag_id` and its canonical query `name` from `/threads/profile/{username}/topics` or a post's `topic` metadata. Topic results have no logged-out continuation cursor; `pagination_limited` marks the login wall for more results.
Response notes
Returns the first public page of posts for the selected topic. Threads does not provide a logged-out continuation cursor. `pagination_limited` is true when Threads shows the login wall for more topic results.
MCP tool threads_topic_search
/threads/post/{username}/{code}Returns one public Threads post by `username` (with or without a leading `@`) and the post `code` from its URL. The response has the post text, canonical URL, preview image URL, and the author's id, name and username. Replies and logged-in fields are not included. An unavailable post returns 404.
Response notes
- Returns only publicly exposed fields; reply pagination and logged-in fields are not included. - Returns 404 when the post is unavailable and 503 when the public metadata cannot be parsed safely.
Sampled 14 Oct 2026: 6 of 6 fields returned with a value. url: threads.com; text: 156 characters.
MCP tool threads_post
/threads/post/{username}/{code}/repliesReturns the public replies currently exposed to logged-out visitors. The response identifies when Threads reports additional replies but withholds a usable continuation cursor.
Response notes
Returns replies visible to logged-out visitors. Items retain their actual author and attached topic metadata when available. Threads can report that additional replies exist without providing a usable public continuation cursor; in that case `has_more` and `pagination_limited` are true and `next_cursor` is omitted.
Sampled 14 Oct 2026: 33 items, 7 fields filled in every item, 6 not. created_at: 2026-07-09 to 2026-07-24; like_count: 1 to 1,053, median 11.
MCP tool threads_post_replies
Related APIs
Social & Creator Platforms
Build creator intelligence, video research, transcript, and audience-comment workflows without maintaining YouTube scrapers.
Social & Creator Platforms
Turn Twitch's public channel, stream, clip, and team data into structured JSON — live status and viewer counts, top games, clips, VODs, and team rosters — as normalized JSON. Credential-free.
Social & Creator Platforms
Track creator and video activity, discover sounds and LIVE streams, and study public ad creatives through documented TikTok API routes.
How to scrape Threads
Threads pages are designed for interactive browsing rather than structured export. Crawlora's ten documented routes cover public profiles, profile posts, Replies, Media and Reposts tabs, profile topic tags, post replies, post search, and topic search.
Look up a profile, one of its public tabs, a post and its replies, a general search query, or a topic tag.
Pass the username and optional post code, or supply the topic query and tag ID returned by a profile or post topic object.
Receive normalized posts, authors, topic tags, media attachments, and any available pagination fields; tab and topic routes may be first-page only.
Store a returned profile-post cursor where available and re-run searches or tab requests as new public content appears.
FAQ
The documented endpoints cover a public profile, its Posts, Replies, Media and Reposts tabs, listed topic tags, individual posts and replies, general post search, and topic-tag search. Topic search requires both the topic query and numeric tag ID from a profile or post topic object.
Profile posts accept a cursor and return the next cursor when available. Logged-out Media, Replies, Reposts, and topic search expose only their first public page; a pagination_limited flag records when a login wall or absent cursor prevents continuation.
No. Crawlora's endpoints collect publicly accessible Threads web data and do not require your account cookies, OAuth credentials, or a Meta developer token.
Collecting publicly accessible profile, post, and reply data is generally permissible when you respect Threads' terms, robots directives, rate limits, privacy rights, and applicable law. Only collect data you are authorized to use.