Threads APIthreads.net ↗
Search Threads posts and user accounts by keyword. Get post text, engagement metrics, author info, and profile data from threads.net via a simple REST API.
What is the Threads API?
The Threads API provides 3 endpoints that cover post search, user search, and single-post retrieval from threads.net. The search_posts endpoint returns arrays of post objects including full text, like counts, reply counts, repost counts, and author details. The search_users endpoint surfaces user profiles with verification status. The get_post endpoint fetches a complete post record by URL, returning 10 structured fields.
curl -X GET 'https://api.parse.bot/scraper/48546944-bfeb-482c-9503-061e6b392624/search_posts?query=AI' \ -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 API
Endpoints and What They Return
The search_posts endpoint accepts a required query string and an optional search_surface parameter that controls result ordering — default, top, or recent. Each post object in the response includes a unique id, a code shortcode, the full text content, like_count, reply_count, repost_count, quote_count, a Unix taken_at timestamp, and a nested user object with the author's username, display name, profile picture URL, and verification status. Pagination is handled through end_cursor and has_next_page fields on the response.
User Search
The search_users endpoint takes a query string and an optional limit (1–50) to control result volume. Each returned user object includes username, full_name, pk (numeric account ID), profile_pic_url, is_verified, and is_active_on_threads. This makes it straightforward to identify whether an account is actively posting or simply registered on the platform.
Single Post Lookup
The get_post endpoint resolves a full Threads post URL — supporting both threads.net and threads.com domains — and returns the post's text, canonical url, code, numeric id, taken_at timestamp, like_count, quote_count, reply_count, a user object, and a title field formatted as the author's display name followed by "on Threads". This is useful for monitoring a specific post's engagement over time without running a broader search.
The Threads API is a managed, monitored endpoint for threads.net — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when threads.net changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official threads.net API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Track engagement (like_count, reply_count, repost_count) on posts matching a brand keyword over time
- Identify verified accounts discussing a topic using is_verified from search_users
- Monitor quote_count on a specific post URL via get_post to measure how widely it is being shared
- Discover active Threads creators in a niche using is_active_on_threads from user search results
- Compare post volume and engagement between top and recent orderings using the search_surface parameter
- Aggregate post text from search_posts results for keyword frequency or sentiment analysis
- Build a Threads account lookup tool using username and full_name fields from search_users
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.