Profile enrichment
Resolve public Threads profile details for creator and social intelligence products.
Threads Data API
Supported API
Threads Data API for profiles, posts, feeds, and search
Build Threads monitoring and enrichment tools with API methods for profiles, posts, search, feed data, and user-oriented surfaces under the public threads.net domain.
ScrapeStorm is not affiliated with Threads or Meta. Use only data that your team is permitted to process.
What you can build
Threads coverage uses the internal slug threads while API paths preserve the public threads.net domain.
Conversation monitoring
Track post and feed-oriented surfaces for reports, alerts, and research.
Search discovery
Use search API methods to find users and posts relevant to a topic or campaign.
Entity directory
All supported entities
Browse every supported Threads entity below, understand what each surface is for, and open the exact docs that matches your workflow.
Threads profile data
4 API methodsProfile API methods resolve public identity, account context, and the base layer for creator, brand, or people-oriented products.
What you get. Use this entity to fetch account details, contacts, summary context, and the identifiers you need before moving into content or social API methods.
API methods inside this entity
4 API methods
Open the API method that matches the lookup, feed, summary, or discovery job you need.
API methods inside this entity
4 API methods
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Profile: Business details by user ID
Open docsStart here when you need richer public context behind profile: Business details by user ID and want the most complete identity view first.
Profile: Summary stats by username
Open docsChoose this API method when your product needs a compact performance view around profile without opening a larger content collection.
Profile: Feed metrics by user ID
Open docsRetrieve compact public feed metrics for a Threads user ID without loading a larger post collection.
Profile: Feed metrics by username
Open docsRetrieve compact public feed metrics for a Threads username without loading a larger post collection.
Threads posts data
9 API methodsPost API methods collect public publishing activity and the objects most teams use first for monitoring and analysis.
What you get. This group is a strong fit for feed views, archive jobs, campaign reporting, and any workflow that starts from the content stream itself.
API methods inside this entity
9 API methods
Open the API method that matches the lookup, feed, summary, or discovery job you need.
API methods inside this entity
9 API methods
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Posts: Details by media ID
Open docsStart here when you need richer public context behind posts: Details by media ID and want the most complete identity view first.
Posts: Details by shortcode
Open docsStart here when you need richer public context behind posts: Details by shortcode and want the most complete identity view first.
Posts: Public posts
Open docsRetrieve public Threads posts for content monitoring, archive, and reporting workflows.
Posts: Related posts by media ID
Open docsDiscover public Threads posts related to a known media ID for content exploration and research.
Posts: Related posts by shortcode
Open docsDiscover public Threads posts related to a known shortcode for content exploration and research.
Posts: Summary by media ID
Open docsChoose this API method when your product needs a compact performance view around posts without opening a larger content collection.
Posts: Summary by shortcode
Open docsChoose this API method when your product needs a compact performance view around posts without opening a larger content collection.
Posts: Web details by media ID
Open docsStart here when you need richer public context behind posts: Web details by media ID and want the most complete identity view first.
Posts: Web details by shortcode
Open docsStart here when you need richer public context behind posts: Web details by shortcode and want the most complete identity view first.
Threads search data
1 API methodSearch API methods expose public discovery surfaces, queries, and intent signals across the platform.
What you get. This entity is a natural entry point for research, prospecting, alerting, and products that need to find people, content, or topics fast.
API methods inside this entity
1 API method
Open the API method that matches the lookup, feed, summary, or discovery job you need.
API methods inside this entity
1 API method
Open the API method that matches the lookup, feed, summary, or discovery job you need.
How teams move from evaluation to launch
Each platform page follows the same decision path: choose the data surface, inspect the docs, validate the response, then scale with pricing and status visibility.
-
01
Map the platform surface
Use the coverage map to identify the entity group that matches your product workflow.
-
02
Open representative docs
Review the implementation docs for method, path, query parameters, and response shape.
-
03
Normalize into your product model
Prefer V2 API methods when you need stable fields across dashboards, scoring, or enrichment jobs.
-
04
Monitor price and status
Check API method pricing and operational status before moving a workflow into production.
Start here
First request
Start with a representative Threads request, then open the implementation docs for identifiers and pagination behavior.
API method
Profile: Business details by user ID
Request cost
2 credits
Required parameters
user_idstrcurl --request GET \
--url "https://www.scrapestorm.net/api/v2/threads.net/profile/business-details-by-user-id" \
--header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
--get --data-urlencode 'user_id=value'
Auth header
X-API-Key
Required parameters
user_id
Billing event
2 credits per successful response
Launch details
Pricing, monitoring, and launch details
Threads API method costs are listed by version and endpoint in the shared pricing table.
ScrapeStorm is not affiliated with Threads or Meta. Use only data that your team is permitted to process.
API methods14
Entities3
Credits2 credits
Per-success credit pricing
API method prices are visible before integration and credits are tied to successful API responses.
API reference and implementation docs
Each platform page links to the API reference and implementation docs for exact request and response details.
Responsible data use
ScrapeStorm is independent from the listed platforms; your team remains responsible for permitted data processing.
Adjacent APIs
View all platforms
Related platform data APIs
Questions before launch
These answers cover coverage, pricing, response formats, and launch details before you commit engineering time.
Why do API paths show threads.net?
The SEO slug is threads, but public API API methods use the platform domain threads.net for clarity and consistency.
Are pagination fields documented?
Yes. Endpoint docs show optional cursor fields where the method supports repeated requests.