Meta Threads Profile Scraper

Batch scrape profile data from Meta Threads. Extract follower counts, bios, verification status, and contact information from multiple profiles. No login required.

Features

• Batch Processing: Process up to 200 profiles per run
• Concurrent Scraping: Processes 2 profiles simultaneously
• Contact Extraction: Extracts emails and phone numbers from bio text
• Error Tracking: Non-existent profiles are recorded in dataset with error field
• No Authentication: Works without login or cookies
• Resource Management: Automatic cleanup after each profile

Quick Start

Input

{
  "usernames": ["zuck", "mosseri", "threads"]
}

Output (per profile)

Successful profile:

{
  "username": "zuck",
  "display_name": "Mark Zuckerberg",
  "bio": "Building Meta and Threads",
  "profile_pic_url": "https://...",
  "followers_count": 5300000,
  "is_verified": true,
  "links": ["https://meta.com"],
  "emails": ["contact@example.com"],
  "phones": ["+1234567890"],
  "bio_links": ["https://threads.net/..."],
  "profile_url": "https://www.threads.net/@zuck",
  "error": null,
  "scraped_at": "2025-01-05T12:00:00.000Z"
}

Non-existent profile:

{
  "username": "nonexistent_user",
  "display_name": null,
  "bio": null,
  "profile_pic_url": null,
  "followers_count": 0,
  "is_verified": false,
  "links": [],
  "emails": [],
  "phones": [],
  "bio_links": [],
  "profile_url": "https://www.threads.net/@nonexistent_user",
  "error": "Profile not found or requires login",
  "scraped_at": "2025-01-05T12:00:00.000Z"
}

Use Cases

• Social media analytics
• Influencer research
• Competitor analysis
• Contact discovery
• Follower tracking

Best Practices

1. Start Small: Test with 2-3 profiles first
2. Valid Usernames: Use valid usernames (invalid ones will be logged with error field)
3. Respect Limits: Maximum 200 profiles per run
4. Monitor Results: Check error field in dataset for non-existent profiles

Important Notes

• Invalid usernames: Non-existent profiles still consume resources and will be recorded with error field
• Cost management: Always verify usernames before running large batches
• Private profiles: Will show error - only public profiles can be scraped

Troubleshooting

Profile shows error in dataset

• Verify username spelling
• Check if profile exists and is public
• Review error field for specific message

High costs

• Invalid usernames still consume resources
• Test with 2-3 profiles before running large batches
• Verify all usernames exist before running