Threads

Threads Profile Scraper

Extracts public Threads profiles by username or URL: handle, display name, bio, bio links, follower count, verification and private status, profile picture, and the recent posts shown on the profile with their media, like count and reply count.

Run on Apify273 userson Apify, measured 2026-11-04

What it extracts

Every field below comes from the Actor’s published dataset schema.

FieldDescriptionType
user.profile_picProfile Pictureimage
user.is_verifiedIs Verifiedboolean
user.is_privateIs Privateboolean
user.usernameUsernametext
user.full_nameNametext
user.bioBiotext
user.bio_linksBio Linkstext
user.followersFollowersnumber
user.urlURLlink
threadsThreadsarray

Input parameters

Generated from the Actor’s input schema — the same fields the Apify console shows.

ParameterTypeRequiredDescription
startUrlsarrayRequiredThreads profile URLs to scrape
proxyConfigurationobjectOptionalProxies are included in the price and chosen automatically, so you can leave this as it is. To route requests through your own proxies, select "Own proxies" and enter their URLs.

API access

Run this Actor from your own code over the Apify API.

Inputjson
{
  "startUrls": [
    {
      "url": "https://www.threads.net/@zuck"
    }
  ]
}
REST — run and get resultsbash
curl -X POST \
  "https://api.apify.com/v2/acts/logical_scrapers~threads-profile-scraper/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"startUrls":[{"url":"https://www.threads.net/@zuck"}]}'
JavaScript — apify-clientjavascript
import { ApifyClient } from 'apify-client'

const client = new ApifyClient({ token: 'YOUR_API_TOKEN' })

const run = await client.actor('logical_scrapers~threads-profile-scraper').call({
  "startUrls": [
    {
      "url": "https://www.threads.net/@zuck"
    }
  ]
})

const { items } = await client.dataset(run.defaultDatasetId).listItems()
console.log(items)
Python — apify-clientpython
from apify_client import ApifyClient

client = ApifyClient("YOUR_API_TOKEN")

run = client.actor("logical_scrapers~threads-profile-scraper").call(run_input={
    "startUrls": [
        {
            "url": "https://www.threads.net/@zuck",
        },
    ],
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Runs are executed on Apify. Create an API token in your Apify account, then call the Actor over REST or with the official client for your language. The same input object works in the Apify console, so you can test interactively before automating.

Use cases

Creator scouting

Check follower count, verification and posting style for a list of accounts before outreach.

Competitor tracking

Follow a competitor’s profile and the posts shown on it by running the Actor on a schedule.

List enrichment

Add bios, bio links and verification status to a list of Threads usernames.

Follower-count monitoring

Re-run weekly to record how an account’s follower count changes over time.

Pricing

Pay per event — you are charged for each successfully scraped result item.

Current rates are published on the Apify listing and can change, so they are not duplicated here. See pricing on Apify

Reliability

99.7% run success rate

Measured across all public Goldmine Actors on Apify, 2026-11-04. This is an account-level figure, not a per-Actor benchmark — per-Actor speed and completeness benchmarks are not yet published. Source.

Limitations

What this Actor does not do, so you can tell before you run it whether it fits.

  • Takes usernames or profile URLs as input. `zuck`, `@zuck` and a full threads.com profile link all work.
  • Returns the posts Threads shows a logged-out visitor on the profile page, which the README puts at a handful up to about ten. There is no pagination for logged-out visitors, so schedule runs to follow an account over time.
  • `followers` is a count only. Threads does not publish follower or following lists, so none are returned.
  • A private account’s posts are not shown to logged-out visitors, so they are not returned; `is_private` reports the status.
  • Returns one item per profile, with the posts nested in a `threads` array.

Frequently asked questions

Do I need a Threads account, cookies or an API key?

No. The Actor reads only what Threads shows to visitors who are not logged in.

Can I get a follower or following list?

No. Threads shows the follower count publicly but not the list of accounts.

How is it different from the official Threads API?

Meta’s Threads API returns profile data for accounts that authorise your app, after app review. This Actor takes any public profile URL and needs no app, token or login.

How is it priced?

Pay per event: each profile saved counts as one result, with the account’s recent posts included at no extra charge. The README lists $0.00599 per result plus Apify platform usage. Current pricing is shown on the Apify listing.

Field and input tables are generated from this Actor's published schemas. Usage figures measured 2026-11-04 from the Apify listing.