threads-api/posts
Recent posts from the profile itself, read from the same kind of document as threads/profile.
| Name | What it is |
|---|---|
handle | The Threads handle, without the @. |
handleuser.usernameA 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.
No pagination and no limit parameter. It returns whatever came in the page — measured across three handles: 4, 5 and 10 posts. That is not the account's post count.
The document is downloaded AGAIN: the cache is keyed by endpoint plus params, so calling both routes for the same handle fetches twice. Measured 2026-09-15: 1.55s after profile against 1.60s without it, cached:false on both.
1 credit per call. A call that finds nothing costs nothing.
No. The cache is keyed by endpoint plus params, so the document is fetched twice. Measured: 1.55s against 1.60s.
No. There is no limit parameter and no pagination. You get what came in the page — 4, 5 and 10 across three measured handles.
Because Threads does not publish a quote count. The field keeps its place in the shape and stays null.