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
Each Crawlora platform API is designed around a specific data surface. Instead of exposing a generic fetch endpoint, Crawlora combines endpoint-specific request logic, managed infrastructure, parsing, normalization, billing, and Playground-tested examples.
Request behavior is tuned for the target platform and endpoint type.
Supported endpoints can use managed proxy routing to improve reliability and reduce infrastructure work.
Dynamic pages can be routed through managed browser instances where JavaScript rendering is required.
Challenge pages and unusable upstream responses are detected and surfaced clearly.
Results are returned as documented JSON instead of raw HTML.
Test the same route from Docs and Playground before production integration.
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.
/threads/profile/{username}Returns public profile metadata for a Threads username, including the visible biography and counts.
/threads/profile/{username}/postsReturns public profile posts with an opaque continuation cursor when more posts are available.
/threads/post/{username}/{code}Returns the public text, author, canonical URL, and preview image for a 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.
Related APIs
Social & Creator Platforms
Build creator intelligence, video research, transcript, and audience-comment workflows without maintaining YouTube scrapers.
Social & Creator Platforms
Track creator, content, hashtag, music, trend, and public ad creative signals from TikTok with production-ready API routes.
Social & Creator Platforms
Turn Instagram public data into structured inputs for social listening and creator research.
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.