Platforms/Threads
Threads API
Read public Threads profiles and posts, a post's replies and its author's follow-ups, and search results. Every call reads what a logged-out visitor sees: no Threads account and no developer app.
Threads endpoints
4 endpoints, each a GET request with your key in the x-api-key header.
| Endpoint | Request | Returns |
|---|---|---|
| Profile | GET /v1/threads/profile?handle=zuck | A user's profile: name, bio, followers and links. |
| User posts | GET /v1/threads/profiles/posts?handle=zuck | A user's latest posts: the ones their profile shows logged out. |
| Post | GET /v1/threads/posts?code=DeZtp-TkQHh | A post, with its replies, its author's follow-up posts in the thread, and the posts Threads shows with it. |
| Search | GET /v1/threads/search?q=coffee | Posts that match a search: Threads' top results. |
Your first request
Save your key and the base URL, then call the profile endpoint:
export API_KEY="your-api-key"
export API_URL="https://api.socialparse.dev"
curl -H "x-api-key: $API_KEY" "$API_URL/v1/threads/profile?handle=zuck"Every answer has the same envelope on every platform: data, page for the next page, and meta. See Responses and Errors.
Compared with Threads's own API
Meta's Threads API works through the signed-in user's account. Searching other people's public posts needs the keyword search permission, which goes through App Review. Social Parse needs neither: it reads the public pages, and you pay per successful call.
Pricing
One credit per successful call, whichever endpoint; errors cost nothing and credits never expire. New accounts start with 100 free credits. See pricing for the packs.
FAQ
Do I need Threads credentials or developer approval?
No. Social Parse reads Threads's public pages as a logged-out visitor does, so you only need an API key.
What does each Threads call cost?
One credit per successful call, live or cached; a page of results is one call, and errors cost nothing. New accounts get 100 free credits.
What about private Threads content?
Only what a logged-out visitor can see is read. Content behind a login answers 403 LOGIN_REQUIRED, and something deleted answers 404 NOT_FOUND.
How fresh is the data?
Each call reads the live page. The same call within a few minutes is answered from a short cache, and deleted content is never served from it.