Meta Threads Profile Scraper
Pricing
from $2.99 / 1,000 results
Meta Threads Profile Scraper
📌 Meta Threads Profile Scraper extracts public profile data fast and accurately for leads, research, and marketing. 🔍 Target by keywords and segment insights instantly—ideal for growth teams and agencies. 🚀 Save time, boost outreach.
Pricing
from $2.99 / 1,000 results
Rating
0.0
(0)
Developer
SolidScraper
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
Meta Threads Profile Scraper 🔍
Meta Threads Profile Scraper is a purpose-built tool that extracts comprehensive profile metadata and the latest posts from Threads.net profiles. Whether you’re using a Threads profile scraper for lead research, building Threads profile analytics, or simply scraping Threads usernames for outreach workflows, this actor helps you automate the busy work—at scale—using publicly available data. It’s designed for marketers, researchers, and data analysts who want structured Threads user profile data in minutes, saving you hours of manual work.
Why choose Meta Threads Profile Scraper?
| Feature | Benefit |
|---|---|
| ✅ All-in-one Threads profile extraction | Pull profile metadata and latestPosts in a single run for faster analysis |
| ✅ Profile + latest posts in structured JSON | Get clean, consistent data fields ready for downstream processing |
| ✅ Resilient scraping approach | Uses built-in proxy support for reliable scraping and resilience |
| ✅ Designed for batch runs | Scrape multiple Threads accounts by listing usernames once |
| ✅ Automation-friendly output | Produces a predictable JSON structure you can export and reuse (JSON/CSV via Apify) |
| ✅ Clear failure states | Returns an error field for profiles that can’t be processed |
Key features
- 📊 Comprehensive profile metadata: Extracts fields like
is_private,follower_count,is_verified,biography,full_name, and more. - 🆔 Threads public profile scraper for usernames: Accepts an array of Threads usernames so you can scrape multiple accounts in one go.
- 📝 Latest posts included: Returns a
latestPostslist formatted into the output schema’s post fields. - 🔄 Resilience built for reliability: Includes proxy support and robust handling so runs keep moving through profiles.
- 💾 Structured data for easy analysis: Outputs consistent JSON per profile, making it simple to load into spreadsheets, BI tools, or ETL pipelines.
- 🌐 Built-in URL normalization: Produces the profile
urlfor each username automatically in the output.
Input
Provide input via an input.json file. Example structure:
{"usernames": ["guinnessworldrecords"]}
Input Fields
| Field | Required | Description |
|---|---|---|
usernames | Yes | List of Threads usernames to scrape. Example: guinnessworldrecords. |
Output
The actor saves each profile’s data in JSON format, pushed as a single item containing a result array of all scraped profiles.
Example output structure:
{"result": [{"url": "https://www.threads.net/@exampleuser","is_private": false,"profile_pic_url": "https://example.com/pic.jpg","friendship_status": "SOME_STATUS","has_onboarded_to_text_post_app": true,"pk": 123456,"text_post_app_is_private": false,"username": "exampleuser","text_post_app_remove_mention_entrypoint": "SOME_VALUE","text_app_custom_feeds": "SOME_VALUE","gating": "SOME_VALUE","follower_count": 1234,"profile_context_facepile_users": [],"hd_profile_pic_versions": [],"text_post_app_public_views": 5678,"is_verified": false,"biography": "Example biography text","text_app_biography": "Example text app biography","full_name": "Example Full Name","bio_links": [],"profile_tags": [],"transparency_label": "SOME_LABEL","show_text_post_app_badge": true,"platform_podcast_info": null,"platform_podcast_episode_info": null,"id": "SOME_ID","latestPosts": [{"id": "POST_ID","logging_info_token": "LOG_TOKEN","pk": 98765,"user": { "username": "exampleuser" },"text_post_app_info": { "SOME": "VALUE" },"is_paid_partnership": false,"audio": null,"caption": "Example caption","caption_is_edited": false,"transcription_data": null,"carousel_media": [],"code": null,"image_versions2": null,"original_height": 1080,"original_width": 1080,"accessibility_caption": null,"usertags": [],"video_versions": [],"has_audio": false,"media_type": 1,"caption_add_on": null,"like_count": 42,"giphy_media_info": null,"prototyping_only_glimmer_post_info": null,"media_overlay_info": null,"metaPlace": null,"meta_place": null,"gen_ai_detection_method": null,"taken_at": 1710000000,"organic_tracking_token": null,"__token": null,"canonical_url": "https://www.threads.net/@exampleuser/POST_ID","like_and_view_counts_disabled": false}]}]}
Note: For profiles that can’t be processed, the actor returns an object containing
errorandusernameinstead of the profile fields.
Output Fields
| Field | Type | Description |
|---|---|---|
url | string | Normalized Threads profile URL for the scraped account |
is_private | boolean | Whether the profile is marked as private |
profile_pic_url | string | URL of the profile picture |
friendship_status | any | Current relationship/friendship status from the profile data |
has_onboarded_to_text_post_app | boolean | Whether the user has onboarded to the text posting experience |
pk | any | Profile primary key from the profile data |
text_post_app_is_private | boolean | Privacy state specifically for the text posting experience |
username | string | The username used for scraping |
text_post_app_remove_mention_entrypoint | any | Mention-related entrypoint value from the profile data |
text_app_custom_feeds | any | Custom feeds configuration from the profile data |
gating | any | Gating information from the profile data |
follower_count | number | Number of followers |
profile_context_facepile_users | array | Facepile users shown in the profile context |
hd_profile_pic_versions | array | Higher-definition profile picture versions |
text_post_app_public_views | any | Public view metric from the profile data |
is_verified | boolean | Whether the profile is verified |
biography | string | Main profile biography text |
text_app_biography | string | Biography text from the text app context |
full_name | string | Full name shown on the profile |
bio_links | array | Links listed in the bio |
profile_tags | array | Tags associated with the profile |
transparency_label | any | Transparency label from the profile data |
show_text_post_app_badge | boolean | Whether the text post app badge is shown |
platform_podcast_info | any | Podcast info (if present) |
platform_podcast_episode_info | any | Podcast episode info (if present) |
id | any | Profile id field from the profile data |
latestPosts | array | List of latest post objects formatted into the post schema below |
error | string | Error details when scraping fails for a username |
username | string | Username associated with the error |
latestPosts post fields (returned inside latestPosts) include: id, logging_info_token, pk, user, text_post_app_info, is_paid_partnership, audio, caption, caption_is_edited, transcription_data, carousel_media, code, image_versions2, original_height, original_width, accessibility_caption, usertags, video_versions, has_audio, media_type, caption_add_on, like_count, giphy_media_info, prototyping_only_glimmer_post_info, media_overlay_info, metaPlace, meta_place, gen_ai_detection_method, taken_at, organic_tracking_token, __token, canonical_url, like_and_view_counts_disabled.
How to use Meta Threads Profile Scraper (via Apify Console)
-
Open Apify Console
Go to console.apify.com and sign in. -
Find the actor page
Search for Meta Threads Profile Scraper and open the actor details page. -
Go to the INPUT section
Paste your input JSON into the input editor. This actor expects ausernamesarray. -
Add one or more Threads usernames
Enter usernames (e.g.,guinnessworldrecords) underusernames. This supports scraping multiple Threads accounts in one run. -
(Optional) Review proxy settings
The run uses proxy support for reliable scraping. If you’re running large batches, you can rely on the actor’s built-in resilience. -
Start the run
Click Run. Watch the logs to see progress as each profile is scraped and processed. -
Wait for results
When finished, open the run’s OUTPUT / dataset results. You’ll receive a JSON structure containingresultwith an array of profile objects (each withlatestPosts). -
Export for analysis
Export the dataset to your preferred format (for example, JSON and CSV are commonly available in Apify exports) and load it into your CRM, spreadsheet, or analytics workflow.
No coding required—get accurate Meta Threads Profile Scraper results in minutes. 🚀
Advanced features & SEO optimization
- 🔧 Engineered for Meta Threads profile data extraction: Specifically built to excel at “Threads profile scraper” workflows where you need profile fields plus
latestPosts. - 🔍 Keyword-driven profile research: Supports scraping Threads usernames for automated Threads user profile scraper pipelines (for example, building a structured lead list).
- 🛡️ Reliability-first scraping: Uses built-in proxy support and includes resilience so runs handle real-world variability better.
- 💾 Structured JSON output: Produces a stable schema for Threads public profile scraper use cases—ideal for Threads profile analytics scraper projects.
- 🌐 Public-facing data collection: Collects publicly available data and returns it in a clean, analysis-ready format (with clear error outputs when something can’t be extracted).
Best use cases
- 📈 Growth marketing lead research: Automate collection of Threads profile metadata and latest posts to enrich lead lists at scale.
- 🕵️ Competitive profiling: Compare multiple Threads account profiles quickly using consistent fields like
follower_count,is_verified, andbiography. - 🎓 Academic or UX research: Build datasets for Threads profile analytics by capturing structured profile context and post content metadata.
- 🧾 Data analysis & reporting: Feed the JSON output into notebooks or dashboards to explore engagement signals like
like_countover recent posts. - 🤝 Community management: Track public-facing profile attributes across many accounts for outreach and relationship workflows.
- 🛠️ Automation pipelines (API or ETL-like workflows): Integrate the actor output into your data processing stack as part of Meta Threads API scraping-style processes.
- 📊 Influencer discovery: Use Threads profile scraper outputs to evaluate accounts for collaboration based on verified status, follower counts, and bios.
Technical specifications
- Supported Input Formats
- ✅
usernames: array of Threads usernames (e.g.,"guinnessworldrecords")
- ✅
- Proxy Support
- ✅ Built-in proxy support for reliable scraping
- Retry Mechanism
- ❗ Retries/fallback behavior is handled internally; the actor is designed to keep runs resilient across profiles
- Dataset Structure
- ✅ Actor pushes a single item containing:
result: array of per-username objects (profile data or error objects)
- ✅ Actor pushes a single item containing:
- Rate Limits & Performance
- ✅ Processing includes pacing between profiles (small delay) to reduce the chance of rate limiting
- ✅ Performance varies by profile accessibility and network conditions
- Limitations
- ❌ If the actor cannot find profile data in the returned HTML, it returns an
errorfor thatusername - ❌ Some posts/profile fields may be missing depending on what’s available publicly for a given account
- ❌ If the actor cannot find profile data in the returned HTML, it returns an
FAQ
What does Meta Threads Profile Scraper extract from each account?
✅ It extracts profile metadata such as is_private, follower_count, is_verified, biography, full_name, bio_links, and more, and it also includes a latestPosts array formatted with many post-level fields.
Can I scrape multiple Threads accounts in one run?
✅ Yes. You provide a list of Threads usernames in the usernames input field, and the actor processes them one by one, returning results for each.
What does the output look like if a profile fails?
❌ If the actor cannot process a username successfully, it returns an object containing error and username for that entry (instead of the full profile fields).
Is authentication or login required?
❌ The actor is designed to extract publicly available data from Threads.net profiles and does not require user authentication via the input.
How do I get the results after the run completes?
✅ After the actor finishes, open the run’s dataset/output in Apify Console. The actor pushes a single item containing result, which is an array of all scraped profile objects.
Can I export the data to tools like spreadsheets or BI dashboards?
✅ Yes. Since the actor outputs structured JSON, you can export the dataset from Apify to formats such as CSV/JSON (depending on your Apify setup) and then load it into your tools.
Does this help with automated Threads profile scraping for analytics?
✅ Absolutely. The returned latestPosts and profile metadata fields make it suitable for building datasets for Threads profile analytics scraper workflows and other automated Threads profile scraping software projects.
Support & feature requests
If you’re using Meta Threads Profile Scraper and want improvements, tell us what would make your Threads profile scraping workflow faster or more reliable. 😊
- 💡 Feature Requests: For example, you could ask for enhancements like additional export formats or extra normalization for specific fields used in Threads profile data scraper pipelines.
- 📧 Contact: Email us at dataforleads@gmail.com.
Your feedback helps shape the roadmap for better Meta Threads profile extraction. 🚀
If you’re looking for the most comprehensive Meta Threads Profile Scraper for structured profile metadata and latest posts, this actor is built to get you there fast and reliably.