Public profile research
Use Threads endpoints to turn public profile research into repeatable API requests with documented inputs and JSON responses.
Turn public Threads conversations and creator activity into structured JSON for social listening, research, and monitoring.
Fetch public Threads profiles, posts, replies, search results, and paginated profile posts through documented Crawlora API endpoints.
Endpoint families
3
Documented params
13
Examples
5
Live catalog snapshot
Active endpoints
5
Methods
GET
Required params
12
Schema refs
5
{
"platform": "Threads",
"endpoint": "threads-search",
"method": "GET",
"path": "/threads/search",
"auth": "apiKey"
}Use cases
Fetch public Threads profiles, posts, replies, search results, and paginated profile posts through documented Crawlora API endpoints.
Use Threads endpoints to turn public profile 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 profile-post monitoring into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Threads endpoint catalog — 5 endpoints, 13 documented request parameters, and 5 published response schemas — the same catalog Docs and Playground run against.
5 documented Threads endpoints, grouped into 3 request families — Post, Profile and Search.
13 request parameters are documented across those Threads endpoints, 12 of them required — the full input contract is public before you write any integration code.
5 of the 5 Threads endpoints ship a recorded example response, and 5 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.
5 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
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/threads/post/{username}/{code}
/threads/profile/{username}
/threads/search
Endpoint catalog
/threads/searchReturns the public first page of Threads search results for a query. Logged-out search does not expose a continuation cursor.
Response notes
Returns the first public page of post results visible to logged-out visitors. Threads does not expose a continuation cursor for this public search view, so `has_more` is false and `next_cursor` is omitted.
MCP tool threads_search
/threads/profile/{username}Returns public profile metadata for a Threads username, including the visible biography and counts.
Response notes
- Counts are normalized 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. Example response: ```json {"code":200,"msg":"OK","data":{"username":"zuck","name":"Mark Zuckerberg","url":"https://www.threads.com/@zuck","biography":"Mostly superintelligence and MMA takes","followers_count":5700000,"threads_count":151}} ```
MCP tool threads_profile
/threads/profile/{username}/postsReturns public profile posts with an opaque continuation cursor when more posts are available.
Response notes
Returns public posts in the profile feed. When `has_more` is true, pass `next_cursor` unchanged to retrieve the next page.
MCP tool threads_profile_posts
/threads/post/{username}/{code}Returns the public text, author, canonical URL, and preview image for a Threads post.
Response notes
- Returns only fields exposed in the credential-free public page metadata; 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. Example response: ```json {"code":200,"msg":"OK","data":{"code":"DakyAavlKLZ","url":"https://www.threads.com/@zuck/post/DakyAavlKLZ","text":"Example public post text","author":{"username":"zuck","name":"Mark Zuckerberg"}}} ```
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. 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.
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, content, hashtag, music, trend, and public ad creative signals from TikTok with production-ready API routes.
How to scrape Threads
Threads pages are designed for interactive browsing rather than structured export. Crawlora's Threads endpoints return public profiles, posts, replies, search results, and profile feeds as JSON.
Look up a public profile, post, replies, search query, or a profile's posts.
Pass the username, post code, search query, or optional pagination cursor to the matching endpoint.
Receive normalized author, post, engagement, reply, and pagination fields for the public content available.
Store cursors and repeat requests to follow public profile activity or analyze discussions over time.
FAQ
Send a public Threads username, post code, or search query to the matching Crawlora endpoint and receive structured JSON for profiles, posts, replies, search results, or profile feeds.
The profile-posts endpoint accepts an optional cursor and returns the next cursor when another page is available. Search currently returns the first public result page, and reply responses indicate when upstream pagination is limited.
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.