🧵 Threads Search Post Scraper

🧵 Threads Search Post Scraper

🧵 Threads Search Post Scraper collects public Threads post data and replies by resolving a post from a URL, numeric ID, or search phrase, then fetching the replies connection and outputting flat, normalized post objects. It solves the challenge of turning Threads search results and post pages into clean, structured data for social listening, competitor monitoring, and reporting. Built for marketers, developers, analysts, and researchers, this Meta Threads scraper scales from quick lookups to automated pipelines with consistent fields that are export-ready.

What data / output can you get?

Below are examples of the normalized fields pushed to your Apify dataset. Values are illustrative and reflect the actual keys produced by the actor.

Data field	Description	Example value
post_url	Resolved Threads permalink constructed from username and code	https://www.threads.com/@zuck/post/AbCdEfGhIjK
pk	Post primary key (numeric string)	"123456789012345"
code	Post code used in the permalink	"AbCdEfGhIjK"
caption	Post text or caption payload	{"text":"Excited to share what’s next…"}
like_count	Number of likes (if present)	1523
taken_at	Unix timestamp of the post	1714156800
user	Normalized author object (ordered fields incl. username, is_verified, etc.)	{"username":"zuck","is_verified":true,...}
text_post_app_info	Threads-specific metadata incl. share_info and text_fragments	{"share_info":{"can_quote_post":true,...},"text_fragments":{"fragments":[...]}}
media_type	Media type indicator	1
image_versions2	Image versions payload (if present)	{"candidates":[...]}
video_versions	Video versions payload (if present)	[{"type":101,"url":"..."}]
sharing_friction_info	Defaulted when absent; sharing friction metadata	{"should_have_sharing_friction":false,"sharing_friction_payload":null}

Bonus fields include canonical_url, original_height, original_width, usertags, audio, carousel_media, gen_ai_detection_method, and more — all kept in a flat, analysis-ready structure. You can download your dataset from Apify in formats like JSON, CSV, or Excel for downstream use.

Key features

• 🔎 Public GraphQL discovery & resolution
  Loads Threads GraphQL credentials from the public search page, resolves each target post via URL, numeric ID, or search phrase, and fetches the replies connection for the chosen thread.

• 🧱 Flat, normalized posts
  Outputs flat post objects with a consistent field order and helpful defaults (e.g., gen_ai_detection_method, sharing_friction_info), ideal for analysis and export. Great as a Threads search results scraper or Threads keyword search scraper.

• 🧪 No login required
  Works without credentials by using public search and endpoints, making it a safe choice when you need a Meta Threads scraper without account risk.

• 🌐 Tiered proxy escalation for reliability
  Smart connectivity flow: start with no proxy → try SHADER (datacenter) → escalate and remain on RESIDENTIAL with up to 3 retries and fresh sessions. Perfect for higher-sensitivity loads.

• 📥 Batch-friendly inputs
  Accepts a list of targets where each line can be a full Threads post URL, a numeric post ID (10+ digits), or a search phrase — handy for scheduling or bulk research.

• 💻 Developer-ready
  Built on Apify with Python and aiohttp under the hood. Clean JSON output fits data pipelines, and it’s easy to integrate with Python or automation tools. Ideal for a Threads Python scraper workflow.

• 🔌 Workflow integration
  Use as a Threads search post scraper in automation stacks (e.g., n8n, Make, Zapier) to trigger downstream alerts, dashboards, or enrichment jobs.

• 🛠 Production reliability
  Robust error handling, sensible defaults, and consistent output schema make it a dependable Threads data extractor for repeated runs.

How to use 🧵 Threads Search Post Scraper - step by step

1. Create or log in to your Apify account.
2. Open the 🧵 Threads Search Post Scraper actor.
3. In “Targets to collect” (urls), enter one item per line:
   • Full post URL: https://www.threads.com/@username/post/AbCdEfGhIjK
   • Numeric post ID: 10+ digit string like 123456789012345
   • Search phrase: e.g., Mark Zuckerberg (the first thread from that search’s HTML is used to fetch replies)
4. (Optional) Configure “Proxy (optional)” if you need extra reliability. If not provided, the run starts without a proxy and escalates as needed.
5. Click Start. The actor will:
   • Discover GraphQL credentials from the public search page
   • Resolve each target into a post ID
   • Fetch the replies connection and normalize posts
6. Monitor the run logs for progress. You’ll see messages for discovery, resolution, download, parsed items, and saved rows.
7. Download results from the run’s Dataset — export to JSON, CSV, or Excel for analysis or reporting.

Pro tip: Use search phrases to Scrape Threads search results quickly, then schedule the actor to track replies over time and feed the JSON into your analytics or CRM.

Use cases

Use case	Description
Social listening & trend tracking	Monitor keyword-driven Threads conversations and capture replies for context-rich insights.
Competitor post monitoring	Collect replies and engagement metrics from competitor posts to benchmark content performance.
Campaign performance review	Export flat post and reply data to analyze like_count trends and audience reactions.
Academic & media research	Build structured datasets from public Threads search phrases for longitudinal analysis.
Reporting & dashboards	Pipe outputs into BI tools to visualize thread activity over time.
Automation pipelines (API)	Trigger a Threads posts scraper workflow that resolves posts from search and pushes JSON into downstream systems.
Brand monitoring by keywords	Use as a Threads keyword search scraper to detect conversations mentioning your brand.
Hashtag discovery workflows	Treat hashtags as search phrases to quickly collect the first thread and its replies.

Why choose 🧵 Threads Search Post Scraper?

This tool prioritizes precision, automation, and reliability for scraping Threads posts and replies at scale.

• 🎯 Accurate, normalized output: Flat post objects with consistent fields and sensible defaults.
• 🌍 No-login approach: Uses public discovery and endpoints without requiring accounts or cookies.
• 📈 Scales to batch runs: Handle multiple URLs, IDs, or search phrases in one go.
• 💻 Developer access: Clean JSON suitable for APIs, Python scripts, and data pipelines.
• 🔐 Safe & public: Operates on publicly available data discovered via the Threads search page.
• 💸 Cost-effective reliability: Tiered proxy strategy for robust execution when targets get busy.
• 🔗 Integrations-ready: Fits automation stacks and export workflows without additional cleanup.

Unlike unstable browser extensions, this Threads posts scraper delivers structured, repeatable results and robust connectivity through a smart proxy escalation strategy.

Is it legal / ethical to use 🧵 Threads Search Post Scraper?

Yes — when used responsibly. The actor discovers credentials from the public Threads search page and fetches public data for the specified targets. It does not access private or authenticated data.

Guidelines for compliant use:

• Scrape only publicly available content.
• Avoid collecting or processing personal data beyond what’s publicly visible.
• Follow applicable regulations (e.g., GDPR, CCPA) and Terms of Service.
• Work with your legal team for edge cases or commercial deployments.

Input parameters & output format

Example JSON input

{
  "urls": [
    "Mark Zuckerberg",
    "https://www.threads.com/@zuck/post/AbCdEfGhIjK",
    "123456789012345"
    ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

• urls (array, required):
  Description: Each line can be a full post URL (threads.com or threads.net), a numeric post ID (10+ digits), or a search phrase. Phrases behave like the script’s search query: the first thread from that search’s HTML is used to fetch replies.
  Default: not set (UI prefill: ["Mark Zuckerberg"]).

• proxyConfiguration (object, optional):
  Description: Leave off for a simple run. Turn on Apify Proxy to route requests through Apify’s network — useful on busy or sensitive targets.
  Default: not set (UI prefill: {"useApifyProxy": false}).

Example JSON output

Each item in the dataset is a flat post object. Below is a representative example with real field names from the actor:

{
  "post_url": "https://www.threads.com/@zuck/post/AbCdEfGhIjK",
  "pk": "123456789012345",
  "user": {
    "friendship_status": {
      "muting": false,
      "following": false,
      "followed_by": false,
      "outgoing_request": null,
      "blocking": null
    },
    "id": "9876543210",
    "pk": "9876543210",
    "text_app_last_visited_time": 0,
    "profile_pic_url": "https://example.com/pic.jpg",
    "username": "zuck",
    "full_name": "Mark Zuckerberg",
    "transparency_label": null,
    "transparency_product": null,
    "transparency_product_enabled": null,
    "is_verified": true,
    "text_post_app_is_private": null,
    "has_onboarded_to_text_post_app": null
  },
  "text_post_app_info": {
    "is_post_unavailable": false,
    "pinned_post_info": null,
    "id": "123456789012345",
    "share_info": {
      "reposted_post": null,
      "is_reposted_by_viewer": false,
      "can_quote_post": true,
      "quoted_attachment_author_attribution_allowed": true,
      "quoted_attachment_post_unavailable": false,
      "quoted_attachment_post": null,
      "quoted_post": null
    },
    "show_header_follow": null,
    "self_thread_info": null,
    "is_spoiler_media": null,
    "is_markup": null,
    "special_effects_enabled_str": null,
    "reply_control": null,
    "can_reply": null,
    "can_private_reply": null,
    "is_ghost_post": null,
    "tag_header": null,
    "direct_reply_count": null,
    "ghost_post_exp_time_ms": null,
    "ghost_post_approximate_like_count_str": null,
    "ghost_post_approximate_reply_count_str": null,
    "ghost_post_reply_type": null,
    "repost_count": null,
    "quote_count": null,
    "reshare_count": null,
    "text_fragments": {
      "fragments": []
    },
    "custom_feed_preview_info": null,
    "platform_podcast_episode_info": null,
    "platform_podcast_info": null,
    "link_preview_attachment": null,
    "link_preview_response": null,
    "linked_inline_media": null,
    "snippet_attachment_info": null,
    "algo_tweaks_info": null,
    "is_reply": null,
    "reply_to_author": null,
    "reply_approval_info": null,
    "hush_info": null,
    "system_status_message": null,
    "private_reply_partner": null,
    "fediverse_info": {
      "is_federated": false,
      "enqueued_for_federation": null,
      "federated_like_count": null
    },
    "self_thread_count": null,
    "root_post_author": null,
    "is_liked_by_root_author": null,
    "related_trends_info": null,
    "post_unavailable_reason": null,
    "post_tombstone_info": null
  },
  "id": "123456789012345",
  "logging_info_token": null,
  "is_paid_partnership": null,
  "audio": null,
  "caption": {
    "text": "Excited to share what’s next…"
  },
  "caption_is_edited": null,
  "transcription_data": null,
  "carousel_media": null,
  "code": "AbCdEfGhIjK",
  "image_versions2": null,
  "original_height": 1080,
  "original_width": 1080,
  "accessibility_caption": null,
  "usertags": null,
  "video_versions": null,
  "has_audio": null,
  "media_type": 1,
  "caption_add_on": null,
  "has_liked": false,
  "like_count": 1523,
  "taken_at": 1714156800,
  "media_overlay_info": null,
  "sharing_friction_info": {
    "should_have_sharing_friction": false,
    "sharing_friction_payload": null
  },
  "canonical_url": "https://www.threads.com/@zuck/post/AbCdEfGhIjK",
  "giphy_media_info": null,
  "metaPlace": null,
  "meta_place": null,
  "gen_ai_detection_method": {
    "detection_method": "NONE"
  },
  "organic_tracking_token": null,
  "__token": null,
  "like_and_view_counts_disabled": null
}

Notes:

• All fields above come directly from the actor’s normalized post objects.
• Some fields may be null depending on the post (e.g., video_versions, audio, usertags).
• The actor saves one dataset item per post in the thread (root + replies), making it a precise Threads replies scraper and Threads post downloader for public data.

FAQ

Do I need to log in to use this Threads scraper?

No. The actor discovers credentials from the public Threads search page and fetches public data without login or cookies. It works as a Meta Threads scraper that relies on public endpoints.

Can I scrape by keyword or search phrase?

Yes. You can input a search phrase in urls, and the actor will resolve the first thread from that search’s HTML to fetch replies. This makes it useful as a Threads keyword search scraper and Threads search results scraper.

Does it support post URLs and numeric IDs?

Yes. Provide full post URLs (threads.com or threads.net) or a numeric post ID (10+ digits). The actor will resolve the post and download its replies.

How reliable is it on busy targets?

Very reliable. It starts with no proxy, escalates to SHADER (datacenter), and then switches to RESIDENTIAL (staying there) with up to 3 retries using fresh sessions. This tiered proxy strategy improves success rates on sensitive runs.

What exactly gets exported?

Flat post objects with fields like post_url, pk, user, caption, like_count, taken_at, media fields, and more. You can download the dataset and export to JSON, CSV, or Excel for analysis.

Can I integrate this with Python or APIs?

Yes. Results land in an Apify dataset as JSON, which you can fetch via Apify API or consume in your Threads Python scraper pipelines and automation workflows.

Is hashtag search supported?

You can treat hashtags as search phrases in urls. The actor resolves the first thread from that search page and collects replies, making it a practical Threads hashtag search scraper for public results.

Is it legal to scrape Threads with this?

Yes, when used responsibly. The actor accesses public data only. Always comply with applicable laws and Terms of Service, and consult your legal team for specific use cases.

Final thoughts

🧵 Threads Search Post Scraper is built to turn public Threads posts and replies into clean, flat JSON for analysis and automation. With public discovery, structured outputs, and a robust proxy strategy, it’s ideal for marketers, developers, analysts, and researchers who need to Scrape Threads posts at scale. Pull results into your data stack via API or Python, automate keyword-based monitoring, and start extracting smarter insights from Threads today.