ナビゲーションにスキップ

Which Threads action takes a URL, shortcode or numeric post ID?

Pass a full Threads post URL in url, or the post’s shortcode in post_id, to threads.web.fetch_post_detail_v2. The shortcode is the part of the link after /post/. Only the older threads.web.fetch_post_detail takes a numeric post ID. In the V2 result, data.post is the post you requested, and the post’s own counters are under data.post.

Do I need a separate ID-resolution query for a complete post URL?

No. Put the full link in url of threads.web.fetch_post_detail_v2. threads.web.fetch_post_detail_v2 also accepts post_id, and in V2 post_id means the shortcode after /post/, not the numeric ID that the older action requires. Supply one known identifier, not a URL and a post_id that point to different posts.

Does post_id mean the same thing in the older detail action?

No. threads.web.fetch_post_detail requires a numeric post ID in post_id; threads.web.fetch_post_detail_v2 takes a shortcode in post_id. A profile @username is neither a numeric post ID nor a shortcode. A numeric author ID is the input for the user-post and user-reply list actions, not for post details.

Why do older catalogs contain action names with trailing spaces?

Legacy catalog entries for fetch_post_comments and search_profiles included trailing spaces. BeatAPI trims whitespace from public action names and accepts the canonical space-free names alongside legacy aliases. Do not copy trailing spaces into new requests, and check the published action reference before calling an endpoint. The archive workflow uses threads.web.fetch_post_detail_v2 rather than a legacy comment action.

Which grouped object is the post I requested?

threads.web.fetch_post_detail_v2 groups the response by role. data.post is the requested post. The four context arrays are replies, parent_thread, author_thread and pinned_replies. replies holds the replies returned with the first screen, a subset of the discussion, not the entire discussion.

Match data.post.code to the shortcode you requested. The requested post may itself be a reply, so is_reply: true on data.post does not make the post a comment under another target. The Threads post archive guide includes a role-splitting check that follows the documented V2 structure.

Where do I read the result?

  1. Check that status=succeeded.
  2. Save request_id and data. BeatAPI sanitizes and passes data through directly, with no uniform Threads post.text field.
  3. Archive the data object as returned. Do not apply Instagram or X field paths, and do not ask a model to reconstruct missing text.

When a teammate shares a reply link, first check that the reply’s shortcode matches data.post.code. Quote data.post for the reply itself, and use parent_thread to explain what the reply was responding to.

Read and archive a post

Which counters belong to the requested post?

Read data.post.like_count, direct_reply_count, repost_count and quote_count for the requested post. Do not sum counters across the four context arrays. The archive guide’s role splitter exports like_count, direct_reply_count, repost_count, and quote_count to main-post-metrics.csv with request and time provenance. The Threads response does not use metrics.views or metrics.shares fields.

direct_reply_count can exceed the number of objects in replies, because replies is only a subset. A missing count is not zero, and quotes and reposts are separate counters. If the requested post is itself a reply, the counters under data.post still belong to the requested post. main-post-metrics.csv records a counter snapshot at the observation time; the snapshot does not measure reach, unique commenters or campaign impact.