Threads Scraper (Apify) ⚡

High-performance Threads Scraper to collect user profiles (with bio links), user posts, and user search results. Built as an Apify Actor for reliability, batching, and scale.

Target keyword: Threads Scraper

Related keywords: Instagram Threads scraper, Threads user scraper, Threads posts scraper, Threads API alternative, Threads data extraction, social media intelligence, Threads analytics, Threads crawler.

---

Table of Contents 📚

• Features
• How it works
• Quick start
• Input configuration
• Example inputs
• Example outputs
• Best practices
• FAQ
• Changelog

---

Features ✨

Module	What you get	Input switches (single-parameter)
Users info	Profile info by username	users_enabled, fetch_info, info_username
User posts	Threads/posts by user_id (pk)	users_enabled, fetch_posts, posts_user_id
Search	Profiles search by username	search_enabled, search_username

This Threads Scraper is ideal for brand monitoring, creator research, social listening, competitive analysis, and content curation.

---

How it works 🧠

• Resilient requests with lightweight retries and key rotation.
• Buffered writes to the Apify dataset for performance.
• Modular inputs so you can enable only what you need.

---

Quick start ⚡

1. In your Actor run, provide input JSON using the schema below.
2. Start the Actor. Results are written to the default dataset.

---

Input configuration ⚙️

Group	Key	Type	Default	Description
Users	users_enabled	boolean	false	Enable Users module
	fetch_info	boolean	true	Fetch user info via users/info
	info_username	string	—	Username (without @) for Users info
	fetch_posts	boolean	true	Fetch user posts via users/posts
	posts_user_id	string	—	user_id (pk) from Users info response for fetching posts
Search	search_enabled	boolean	false	Enable Search module
	search_username	string	—	Username to search via search/profiles

---

Example inputs 📥

• Fetch user info and posts in one run

{
  "users_enabled": true,
  "fetch_info": true,
  "info_username": "mrbeast",
  "fetch_posts": true,
  "posts_user_id": "63634640553"
}

• Search profiles by username

{
  "search_enabled": true,
  "search_username": "mrbeast"
}

---

Example outputs 📤

• Raw Users info response

{
  "status": "Successful",
  "message": "Data retrieved successfully",
  "data": { /* user info fields including pk/id, username, etc. */ }
}

• Raw Users posts response

{
  "status": "Successful",
  "message": "Data retrieved successfully",
  "data": [ /* array of threads/posts as returned by API */ ]
}

• Raw Search profiles response

{
  "status": "Successful",
  "message": "Data retrieved successfully",
  "data": [ /* array of profiles as returned by API */ ]
}

• Summary (final item)

{
  "success": true,
  "pages_fetched": 3,
  "total_pushed": 421,
  "fetched_at": "2025-01-01T12:34:56.000Z",
  "resultsMeta": { "groups_processed": ["users", "search"] }
}

---

Best practices 🧩

• Single-parameter per endpoint: keep inputs minimal (info_username, posts_user_id, search_username).
• Derive posts_user_id: first call Users info to get pk/id, then set it as posts_user_id.
• Multiple fetch in one run: you can enable both fetch_info and fetch_posts simultaneously; each uses its own single parameter.

---

FAQ ❓

• Is login required?
  • No. The Actor uses public data.
• Where do results go?
  • The default Apify dataset for the run.

---

Changelog 📦

• Initial release: Users details, User posts, and Users search.

---