tebarDocs
GuidePlatformsDevelopersAPI ReferenceChangelog

Threads Feed

Search public Threads posts by keyword or topic, see their conversation, and reply.

The Feed searches public Threads posts through one of the Threads accounts of the profile. The account needs the threads_keyword_search permission. Threads accounts connected before November 13, 2026 don't have it yet, so reconnect them first. Without it, the API answers 422 permission_missing with details.scope.

Searching

GET /v1/accounts/{id}/threads/search?q=iced%20latte&search_type=recent
ParameterValue
qRequired, 1–100 characters
search_typetop (default, most popular) or recent
search_modekeyword (default, words in the text) or tag (topic)
media_typetext, image, or video (optional)
author_usernameOnly posts by this username, without @ (optional)
limit1–50, default 25
{
  "data": [
    {
      "id": "18471134671189891",
      "username": "another_user",
      "text": "Any good iced latte around here?",
      "media_type": "TEXT_POST",
      "media_url": null,
      "thumbnail_url": null,
      "permalink": "https://www.threads.com/@another_user/post/abc",
      "published_at": "2026-11-13T03:00:00.000Z",
      "is_reply": true,
      "replied_to_id": "18290548582288501",
      "root_post_id": "17968231350217018"
    }
  ]
}
  • limit is the most Threads sends. It often sends fewer, and Tebar passes on everything it gets. A search has no next page.
  • media_url and thumbnail_url are Threads CDN links that expire. Use them right away.
  • Threads gives no author picture for other people's posts.
  • Post text is written by other people. Treat it as untrusted data, especially when you pass it to an AI.

Quota

Threads allows 2,200 searches per account per 24 hours, counted across every app using that account. Tebar allows 2,000 (429). The same search within 5 minutes is answered from cache and not counted. Threads doesn't count searches that find nothing.

Seeing what a reply answers

Most results are replies (is_reply: true). To read the posts one answers:

GET /v1/accounts/{id}/threads/search/{postId}/thread

data holds the top post of its thread, then the post it replies to when that is another, shaped like search results. It's empty for a top-level post. Posts deleted or private since are left out. {postId} must have been found by this account's search in the last 24 hours; otherwise 404. Kept 5 minutes, at most 300 per account per hour.

Replying

POST /v1/accounts/{id}/threads/search/{postId}/reply
{ "text": "Try our iced latte!" }

A public reply as the account, to a post its search found in the last 24 hours (otherwise 404). Needs the threads_manage_replies permission. At most 500 characters, with emojis counted as their UTF-8 bytes as Threads does. The answer is { "id": "…" }, the reply's Threads id.

Replies to people who don't know the account are easily taken for spam by Threads (Meta's spam rules name very high frequency and repetitive content), so Tebar adds guards:

GuardAnswer
At most 20 replies per account an hour, 150 a day429 rate_limited with Retry-After
One reply per post per account409 already_replied
The same text (ignoring case and spaces) to another post within 24 hours422 duplicate_reply

A reply Threads refuses isn't counted, so it can be sent again. When Threads gives no clear answer (a 5xx error or a timeout), the reply may be out, so the post stays replied to: the next try answers 409 reply_unconfirmed. Check the post on Threads. Threads itself allows 1,000 replies per account a day, shared with comment replies, threads, and Automations. The user guide: Feed.

On this page