threads-api/profile

Threads profile API — followers, bio, verified, private

Public Threads profile: followers, bio, avatar, verified, private. Same stack as Instagram — the logged-out page.

Parameters

Name	What it is
`handle`	The Threads handle, without the @.

Handle format and anchor

Handle: handle
Anchor: follower_count, unique in the document

What this endpoint does not return.

followingNull. The profile does not expose it, and a zero would read as an account following nobody.
posts_countNull. Same reason — not exposed on the profile.

A field we cannot read comes back null, never 0. A zero would be a claim about the account; null is a fact about our collection.

Where this goes wrong.

This is the clearest case of a scraper failing silently. Plain curl returns a 268 KB page with HTTP 200 and no follower_count anywhere in it. Nothing errors. You get a page and no number.

Measured

Requires TLS impersonation: plain curl brings back 268 KB WITHOUT follower_count; the fetch service brings 960 KB with the object.

Cost

1 credit per call. A call that finds nothing costs nothing.

Why does my own curl return a page with no follower count?

Threads needs TLS impersonation. Plain curl gets 268 KB and a 200, with the counter object absent.

Why are following and posts_count null?

The profile does not expose them. A null says we do not have it; a zero would say the account has none.

Other routes for this platform

threads-api/posts

← threads-api