Skip to content

Throk API and MCP changelog

Changes to the Throk API (premium-api.throk.ai) and MCP tools, newest first. Entries marked MCP also apply to the matching MCP tools.

  • New: /post/inspiration and MCP get_inspiration accept language: zh (all Chinese: zh-Hant, zh-Hans and yue), zh-Hant (Traditional Chinese), zh-Hans (Simplified Chinese), yue (Cantonese), en (English), ja (Japanese) or ko (Korean). If you leave it out, results come from Chinese, Japanese and Korean posts together, without English, as before. Pricing is unchanged (30 credits per call, up to 10 posts). See Post language.
  • New: The inspiration library now includes English posts: root posts with 1,000+ likes and at least 300 characters (Chinese, Japanese and Korean posts still need 1,000+ likes and more than 200 CJK characters). English posts are included from 2026-10-09, and older English posts are being backfilled.
  • New: Semantic search supports English posts: /post/semantic-search and MCP semantic_search_posts accept language=en, with the same usage and pricing as the other languages. Semantic data for English posts starts building up with this release, so for the first few weeks less than 30 days of English posts can be searched. /post/inspiration (get_inspiration) still doesn’t include English posts.
  • Changed: Every endpoint and MCP tool that filters posts now uses one parameter, language, with ISO language codes (case-insensitive): zh (all Chinese, the default), zh-Hant (Traditional Chinese), zh-Hans (Simplified Chinese), yue (Cantonese), en (English), ja (Japanese) and ko (Korean). Leaderboards, ladders and power hours use language too, and each language is calculated separately. There’s no “all languages” option: query one language per call. See Post language.
  • New: English posts (language=en) are available in keyword search, keyword trend, hot posts, leaderboards, ladders and power hours. Keywords in English posts match singular, plural and other word forms together. See search rules. Semantic search doesn’t support English yet (returns 400).
  • New: /leaderboard/follower-growth and MCP get_follower_growth accept language, all 7 codes.
  • Webhooks: A rule’s language is one of zh (the default), zh-Hant, zh-Hans, yue, ja or ko, and responses always use these codes.
  • New: In the developer portal, you can rename and rotate API keys (rotating creates a new key with the same name and revokes the old one immediately), and see when each key was last used. Each account can have up to 20 active keys.
  • Improved: /post/inspiration and MCP get_inspiration now search high-engagement posts (1,000+ likes) refreshed daily. Results may include Japanese and Korean posts.
  • Changed: /user/{username}/interactions and MCP get_user_interactions return 10 accounts by default (was 20), costing 30 credits for up to 10 plus 2 credits per extra account (was 70 credits for up to 30). Still free when there are no interactions. MCP returns up to 100 accounts per call, the same as REST.
  • New: GET /user/{username}/interactions and MCP get_user_interactions: find who an account interacts with most. Lists the accounts it traded the most replies with over the last 7–90 days, with how many times each side replied and when they last interacted. Sort by two-way interaction, total, replies sent or replies received. 70 credits for 30 accounts, plus 2 credits per extra account; free when there are no interactions. See Find who an account interacts with most.
  • New: MCP supports signing in with your Throk account (OAuth) in Claude, ChatGPT, Codex and Cursor. No API key needed; calls still use the account’s API credits. See Use in AI assistants (MCP).
  • Changed: In the usage history, the “Key” (金鑰) column is now “Source” (來源). AI tools signed in with a Throk account show as “Account login · app name” (帳號登入 · 應用程式名稱).
  • Changed: /post/search searches the last 7 days when no time is set (was 3 hours). Any time filter can reach back at most 90 days.
  • Changed: Insufficient credits return HTTP 402 (was 400).
  • Changed: Parameter errors (including conflicting time filters) always return HTTP 400 in the format {"detail": "error message"} (some used to return 422).
  • Changed: /post/forecast takes up to 20 posts per call.
  • Improved: Keyword trend supports tw and cn.
  • Improved: post_type=thread no longer requires include_details.
  • Webhook: Events have a new rule field. You can test an endpoint as soon as it’s created. Keyword rules don’t accept lookbackHours. A rule’s language is returned the way you sent it, and fields also accept snake case (such as like_count).
  • Improved: The X-Throk-Signature header on webhook events carries a v1 signature, so you can verify that events really come from Throk.
  • New: Keyword trend (/post/keyword-trend, MCP get_keyword_trend) has a new include_engagement parameter. Besides the post count, each day also returns the total likes, replies, reposts and shares of those posts. With it on, each keyword costs 4 credits per day (instead of 3). With it off, the response and pricing are the same as before.
  • New: /post/search and MCP search_posts have new min_age_hours and max_age_hours parameters, so you can set the search range as “hours since posting” (up to 90 days).
  • Improved: /post/{code}/chain merges in replies fetched live, so posts that haven’t been collected yet can also be queried.
  • Improved: /user and batch account lookups fall back to live account data when stored data is incomplete.
  • Improved: /live/posts responses now include media_url and reshare_count. MCP get_live_posts always returns media URLs.
  • Improved: Post forecast (/post/forecast, MCP forecast_posts) can now forecast from 1 hour after posting (was 2 hours), with an updated forecast model. Posts that are 1–2 hours old are now also charged.
  • New: GET /live/posts, GET /live/users and MCP get_live_posts, get_live_users read a post’s or account’s current numbers live from Threads, for any publish time and any account. 3 credits per post or account; 1 credit when Threads hides the view count; failed reads are free.
  • Improved: /user/{username}/top-threads is much faster for long time ranges.
  • Changed: When the backend is temporarily unavailable, the API returns HTTP 503. Retry later.
  • Changed: post_timestamp in trending posts, post reply chains, semantic search, leaderboards and account posts is now a UTC Unix time (seconds), consistent with the other endpoints.
  • Improved: Post forecast accepts several comma-separated post codes and returns clearer error messages. Posts outside the forecast time window are free.
  • New: GET /post/forecast and MCP forecast_posts (post forecast): return a post’s current view count, plus the probability and estimated time of reaching each view threshold. 10 credits per post.
  • New: New region values zh, tw, hk, cn, jp, kr for the language parameter in search, trending posts, keyword trend and webhooks, and for the location parameter in leaderboards. tw and cn tell Traditional and Simplified apart. The old chinese, japanese and korean still work. See Regions and languages.
  • Improved: The semantic search REST API returns up to 3000 posts per call. Likes and replies thresholds are applied after semantic matching.
  • Improved (MCP): Each tool’s description shows its price. Ladder tools accept a region.
  • New: GET /post/semantic-search and MCP semantic_search_posts (semantic search): describe a topic in one sentence and find the posts from the last 30 days closest in meaning, each with a relevance score. 30 credits for the first 10 posts, then 2 credits per post. See Semantic search.
  • New: Webhook rules can set a views (view_count) threshold (07-23).
  • New: Webhook rules can filter by language or market (07-15).
  • Improved: Trending posts, post reply chains, search with details, account lookups and an account’s top posts return the view count impression_count (07-13).
  • Improved (MCP): Tool calls that take longer than 60 seconds return an explanatory message instead of hanging (07-11).
  • Changed: Creating webhooks requires API Standard or higher.
  • Changed: Webhook rules have minimum likes and replies thresholds.
  • New: Search, trending posts and keyword trend have a new language parameter (chinese, hk, japanese, korean).
  • New: REST leaderboard and stats endpoints: /leaderboard/cool-replies (top replies), /leaderboard/post-like-growth (viral posts), /leaderboard/follower-growth (follower growth), /stats/follower-ladder, /stats/like-ladder, /stats/power-hours, and /post/inspiration (inspiration search).
  • New (MCP): New tools get_cool_replies, get_post_like_growth, get_follower_growth, get_follower_ladder, get_like_ladder, get_power_hours, get_inspiration.
  • New (MCP): Launched the MCP server https://premium-api.throk.ai/mcp, with the same keys and prices as the REST API. First tools: search_posts, get_hot_posts, get_keyword_trend, get_user, get_user_top_threads, get_user_follower_history, get_balance. For setup, see Use in AI assistants (MCP).
  • New: Webhook “trending” rules: the keyword can be left empty, and the lookback window can be set to 1–72 hours.