탐색으로 건너뛰기

Threads guides

To keep a Threads post that a teammate shared, follow the Threads post archive guide: read the post with threads.web.fetch_post_detail_v2 and cite replies and surrounding context separately from the archived post. To collect feedback on a launch, run the same query through threads.web.search_recent and threads.web.search_top.

Choose a task

A feature just launched. What are Threads users asking now, and which discussions already drew attention?

Send the same query to threads.web.search_recent and to threads.web.search_top. For a new export feature, threads.web.search_recent surfaces questions that have just come up, and threads.web.search_top surfaces discussions that have already gained attention.

{"action":"threads.web.search_recent","params":{"query":"<product name + export feature>"}}
{"action":"threads.web.search_top","params":{"query":"<same search phrase>"}}
  1. POST each JSON body to https://api.beatapi.io/v1/social-data/call with BeatAPI Bearer authentication.
  2. In your sheet, save each post’s original link and the search that returned the post (recent, top or both).
  3. When a post appears in both results, keep a single row and mark both searches.
  4. Route each finding with its evidence. For example, for “The date changes after export,” send the excerpt, the post link and the affected version to the product team to check locale formatting.

To see what your team has already answered, read the team account’s batches from the account posts, replies and reposts lists. Use the author and the original link to tell original posts from reposts, and put the questions your team already answered in a separate sheet. To check public replies to one announcement, open the original launch post’s detail. Threads reply visibility controls

Threads questions