Threads Public Data API
Retrieve public Threads profiles, resolve known posts, or collect posts from selected profiles with normalized identity, content, media, engagement, and timestamp fields.
Available Threads APIs
Use Profiles for account data, Posts for one known public post, or User Posts for a bounded collection from selected profiles.
What Threads data can you retrieve?
SocQ returns normalized public account and post records with identity, content, media, visible engagement, source, and collection-time context.
Public profile details
Retrieve profile IDs, URLs, usernames, display names, biographies, images, linked websites, visible account counts, and collection time.
Known post content
Resolve a public post URL into post identity, text, author details, source URL, and available media.
Visible post engagement
Keep publication and collection times with available like, comment, repost, and share counts.
Posts from selected profiles
Browse a bounded set of public posts from each profile URL and keep the submitted profile connected to the results.
SocQ vs Threads API
SocQ focuses on supported public Threads collection. Meta's Threads API is designed for authorized publishing, replies, insights and supported discovery workflows.
| Capability | SocQ | Threads API |
|---|---|---|
| Primary use | Collect public profiles, posts and a user's recent posts | Build authorized publishing, reply, insight and discovery integrations |
| Customer OAuth | SocQ API key; no customer Threads OAuth | Meta app, Threads user authorization and access token |
| Starting input | Public Threads profile or post URL | Authorized account context, Threads IDs and supported search parameters |
| Publish or manage replies | Not supported | Supported with the required Threads permissions |
| Response format | Normalized SocQ records | Native Threads Graph API objects |
How the Threads API works
Profiles, Posts, and User Posts use the same asynchronous task and paginated result workflow.
1. Submit public URLs
Send profile or post URLs to the matching API and save the returned task_id.
2. Track the task
Poll /v1/tasks/{task_id} until processing is complete.
3. Retrieve the results
Read data.results.items and use next_cursor while has_more is true.
Authenticate with your SocQ API key and submit a public profile URL to User Posts. Profiles and Posts use the same task flow.
curl -X POST "https://api.socq.ai/v1/threads/user-posts" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"urls":["https://www.threads.com/@example"],"results_limit":100}'
# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is trueCommon Threads API use cases
Creator and profile research
Enrich known profile URLs with public identity, biography, website, visible account metrics, and collection time.
Known post analysis
Resolve selected post URLs into content, author, media, publication time, visible engagement, and source fields.
Creator content monitoring
Collect a bounded set of posts from selected profiles and compare content across repeat collections.
Engagement reporting
Use visible counts and collected_at to compare public post snapshots without treating them as real-time metrics.
Limits and public-data policy
Threads results are point-in-time public records. These APIs do not access private content or publish, edit, delete, or manage Threads accounts and posts.
- Profiles accepts threads.com and threads.net /@username URLs. Bare usernames and post URLs are rejected.
- Posts accepts /@username/post/{post_id} URLs. It does not support results_limit or profile-post discovery.
- User Posts accepts /@username profile URLs. results_limit defaults to 100, accepts 1 to 2,000, and applies separately to each profile.
- User Posts does not identify whether a result is an original post, reply, quote, or repost.
- A post can include comments_count, but individual replies and reply trees are not returned.
- Optional identity, content, media, timestamp, and engagement fields can be empty when the public record does not expose them.
Threads API frequently asked questions
What is the Threads API?
The Threads API is a set of SocQ endpoints for retrieving public profile data, resolving known posts, and collecting a bounded set of posts from selected profiles.
Which Threads API should I use?
Use Profiles for /@username account records, Posts for exact /@username/post/{post_id} links, and User Posts for a bounded collection from each /@username profile URL.
How does the User Posts result limit work?
results_limit defaults to 100, accepts integers from 1 through 2,000, and applies separately to every submitted profile URL.
Do User Posts results identify replies or reposts?
No post subtype is exposed in the normalized result. Treat each item as a public post discovered from the submitted profile without inferring whether it is an original, reply, quote, or repost.
Are Threads posts and engagement metrics complete or real time?
No. Results reflect public fields available at collection time, do not include full reply trees, and should be treated as point-in-time snapshots rather than real-time feeds.
How is Threads collection priced?
Each returned profile costs 0.6 credits, while each returned post from Posts or User Posts costs 0.5 credits. Empty result sets have no result charge.