Threads URL Extractor avatar

Threads URL Extractor

Pricing

from $5.00 / 1,000 results

Go to Apify Store
Threads URL Extractor

Threads URL Extractor

Extract Threads post details from one or more post URLs and save successful results to the Apify dataset.

Pricing

from $5.00 / 1,000 results

Rating

0.0

(0)

Developer

Giichi Arai

Giichi Arai

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Extract Threads Post Information from URLs

This Apify Actor extracts Threads post details from one or more Threads post URLs and stores successful results in the default dataset.

Features

  • Accepts a list of Threads post URLs.
  • Supports both threads.com and threads.net.
  • Supports both @username/post/... and /t/... URL formats.
  • Extracts post text, author details, engagement counts, hashtags, mentions, links, media, and timestamps.
  • Supports Apify proxy configuration when available on your account.
  • Pushes only successful items to the dataset, so the output schema stays consistent.

Input

Required

  • urls: list of Threads post URLs to extract.

Optional

  • retryTimes: maximum number of retries for transient request failures.
  • requestTimeoutSecs: timeout for each request in seconds.
  • delaySecs: delay between processing URLs. Set 0 to disable the delay.
  • proxyConfiguration: optional Apify proxy settings.

Example Input

{
"urls": [
"https://www.threads.com/@impatrickt/post/CvBIUAdrTOz",
"https://www.threads.net/t/CvBIUAdrTOz"
],
"retryTimes": 2,
"requestTimeoutSecs": 30,
"delaySecs": 1
}

Output

Each successful dataset item contains:

  • id
  • text
  • author
  • author_name
  • author_id
  • created_at
  • like_count
  • reply_count
  • repost_count
  • quote_count
  • view_count
  • is_reply
  • is_repost
  • hashtags
  • mentions
  • urls
  • media
  • lang
  • url
  • verified
  • follower_count
  • following_count

Failed URLs are skipped from the dataset and reported only through Actor logs.

Sample Output

{
"id": "3858180398661139708",
"text": "Question to the ad gurus out there: Why does Meta serve me my own ads?",
"author": "evelongfield",
"author_name": "Evelien Langeveld - How to grow on Instagram",
"author_id": "63100931207",
"created_at": 1774150966,
"like_count": 0,
"reply_count": 0,
"repost_count": 0,
"quote_count": 0,
"view_count": 0,
"is_reply": false,
"is_repost": false,
"hashtags": [],
"mentions": [],
"urls": [],
"media": [
{
"type": "image",
"width": 1284,
"height": 2160,
"url": "https://example.com/image.jpg"
}
],
"lang": "",
"url": "https://threads.com/t/DWLAqGNknz8",
"verified": true,
"follower_count": 0,
"following_count": 0
}

Notes

  • Results are stored in the default Apify dataset.
  • If proxy initialization is unavailable for your account, the actor continues without proxy instead of failing at startup.
  • Local storage/ output from apify run stays on your machine and is not automatically uploaded to Apify Console.
  • To charge per submitted URL, configure a pay-per-event event named input-url in Apify Console.
  • If you want pricing to be based only on submitted URLs, disable the synthetic default dataset item event apify-default-dataset-item in Apify Console to avoid double charging.