threads.net APIthreads.net ↗
Search Threads.net posts and user profiles by keyword. Returns post text, engagement metrics, author info, verification status, and pagination cursors.
curl -X GET 'https://api.parse.bot/scraper/48546944-bfeb-482c-9503-061e6b392624/search_posts' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for posts/threads on Threads by keyword. Returns posts matching the search query with engagement metrics, author info, and post text.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword or phrase to find posts about. |
| search_surface | string | Search result ordering. Accepts exactly one of: default, top, recent. |
{
"type": "object",
"fields": {
"posts": "array of post objects with id, code, text, like_count, reply_count, repost_count, quote_count, taken_at, and user info",
"end_cursor": "string or null pagination cursor",
"has_next_page": "boolean"
},
"sample": {
"posts": [
{
"id": "3908520567213299340",
"code": "DY92r9mDpaM",
"text": "At AltmanAI, we believe the future of AI should feel human...",
"user": {
"pk": "78025189002",
"username": "altmanai_",
"full_name": "AltmanAI",
"is_verified": false,
"profile_pic_url": "https://scontent-ord5-2.cdninstagram.com/..."
},
"taken_at": 1780151981,
"like_count": 1,
"quote_count": 0,
"reply_count": 0,
"repost_count": 0
}
],
"end_cursor": null,
"has_next_page": false
}
}About the threads.net API
The Threads.net API provides 2 endpoints for searching posts and user accounts on Threads. The search_posts endpoint returns matching threads with full engagement metrics — like count, reply count, repost count, and quote count — alongside author info and timestamps. The search_users endpoint returns profile data including verification status and whether the account is active on Threads, supporting lookups of up to 50 users per request.
Endpoints Overview
The API exposes two endpoints: search_posts and search_users. Both accept a query string as the primary required input and return structured arrays of matching objects. Responses from search_posts include a has_next_page boolean and an end_cursor string to support paginated retrieval of large result sets.
search_posts
The search_posts endpoint accepts a query string and an optional search_surface parameter that controls result ordering. Valid values for search_surface are default, top, and recent — allowing you to retrieve the most relevant results or the most recent ones depending on your use case. Each post object in the response includes id, code, text, like_count, reply_count, repost_count, quote_count, and taken_at (the post timestamp), plus a nested user object with author details.
search_users
The search_users endpoint accepts a query string and an optional limit integer (1–50) capping the number of returned profiles. Each user object includes username, full_name, pk (the platform's internal user identifier), profile_pic_url, is_verified, and is_active_on_threads. The is_active_on_threads flag distinguishes accounts that are linked from Instagram but not actively posting on Threads from those with genuine Threads activity.
- Track engagement trends for a keyword by comparing
like_count,repost_count, andquote_countacrosstopvsrecentsearch surfaces - Monitor brand mentions on Threads by querying a company or product name through
search_posts - Identify verified creators in a topic area using
is_verifiedfromsearch_usersresults - Build a Threads content aggregator by paginating
search_postsresults usingend_cursorandhas_next_page - Find accounts active on Threads (not just linked from Instagram) using the
is_active_on_threadsfield - Analyze post volume and reply activity for a hashtag or keyword over time using
taken_atandreply_count - Compile a list of usernames and profile images matching a topic for outreach or research using
search_users
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Threads have an official developer API?+
What does the search_surface parameter actually change in search_posts results?+
search_surface to top returns posts ranked by relevance or engagement. recent returns posts in reverse-chronological order. default applies the platform's standard ranking. The response shape — including all engagement fields and pagination cursors — is identical across all three values; only the ordering of results differs.Does the API return follower counts or following counts for users?+
search_users endpoint returns username, full_name, pk, profile_pic_url, is_verified, and is_active_on_threads, but does not expose follower or following counts. You can fork this API on Parse and revise it to add a profile detail endpoint that includes those fields.Can I retrieve the full reply thread or quoted post content for a given post?+
search_posts endpoint returns top-level post fields including reply_count and quote_count as counts, but does not return the content of replies or quoted posts. You can fork this API on Parse and revise it to add an endpoint that fetches a post's replies or quote-thread content.How does pagination work for search_posts?+
search_posts response includes has_next_page (boolean) and end_cursor (string or null). When has_next_page is true, pass the value of end_cursor as a cursor parameter in your next request to retrieve the following page of results. When end_cursor is null, you have reached the last page.