tiktok-api

作成者: fetcher-sh

fetcher.sh上のTikTok API代替 — x402経由でUSDCによる従量課金制、またはBearerkーによるプリペイドクレジット、ログイン不要、アプリレビュー不要。キーワードでTikTokの投稿を検索し、日付範囲内で「いいね数が多い順」または「新しい順」に並べ替えたい場合、共有URLまたはIDで投稿を検索したい場合、@usernameでTikTokプロフィールを取得したい場合、ユーザーの投稿・フォロワー・フォロー中を取得したい場合、ハッシュタグの投稿を取得したい場合、特定のサウンド/楽曲を使用した投稿を取得したい場合、特定の場所からの投稿を取得したい場合、または投稿の...を読みたい場合に使用します。

npx skills add https://github.com/fetcher-sh/fetcher-skills --skill tiktok-api

TikTok API

TikTok data on demand: keyword post search with sort/date filters, profile lookup by handle, followers and followings, hashtag and music/sound feeds, location-based posts, and comment threads — one plain HTTP GET per call, paid as you go. No login, no session cookies, no browser automation, no TikTok developer app review.

Base URL: https://tiktok.fetcher.sh

Quick reference

Base URLhttps://tiktok.fetcher.sh
AuthAuthorization: Bearer bby_live_... or x402 (USDC)
Price$0.004/call (flat)
Endpoints13, all GET
MCPhttps://tiktok.fetcher.sh/mcp
Machine-readable/openapi.json · /llms.txt · /skill.md

Which endpoint do I need?

I want to...Call
Search posts by keyword (optionally most-liked/recent)GET /api/post/search
Look up a post by its share URLGET /api/post?url=...
Look up a profile by @usernameGET /api/user/handle/{username}
Get a user's posts, followers, or followingsGET /api/user/{id}/posts / /followers / /followings
Get a post's commentsGET /api/post/{id}/comments
Find posts under a hashtagGET /api/hashtag/{id}/posts
Find posts using a specific soundGET /api/music/{id}/posts

Full param details for every row: references/endpoints.md.

Authentication

Two ways to pay, same data — full mechanics in the fetcher skill:

# 1. Prepaid credits (recommended — get a key at https://fetcher.sh/topup
#    or via POST /api/credits/topup, see the fetcher skill)
export FETCHER_API_KEY="bby_live_xxxxxxxxxxxx"
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://tiktok.fetcher.sh/api/post/search?keyword=hello"

# 2. x402 pay-per-call — omit the header; a GET with no payment returns 402
#    with machine-readable payment requirements (USDC on Base, Polygon,
#    Arbitrum, Monad, or Solana). @x402/fetch signs and retries automatically.

Every response is { "status": number, "message": string, "data": ... }; the HTTP status mirrors status.

Endpoints (13 — all GET, $0.004/call)

EndpointWhat it returns
/api/post/searchPosts matching a keyword; sort and date-range filters
/api/postA single post resolved from its share URL
/api/post/{id}A single post by ID
/api/post/{id}/commentsA post's comments
/api/post/{id}/comments/{commentId}/repliesReplies to a comment
/api/user/handle/{username}Profile by @username
/api/user/{id}/postsA user's posts
/api/user/{id}/followersA user's followers
/api/user/{id}/followingsAccounts a user follows
/api/hashtag/handle/{name}Hashtag metadata by name
/api/hashtag/{id}/postsPosts under a hashtag
/api/music/{id}/postsPosts using a sound/music track
/api/location/{locationId}/postsPosts tagged at a location

{id} / {username} / {name} are path parameters. Optional query params (cursor, region) paginate or geo-scope results; keyword (search) and url (post lookup) are required where they appear.

Scenarios

Most liked posts this month:

curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  --data-urlencode "keyword=ai agent" -G \
  --data-urlencode "sortType=MOST_LIKED" \
  --data-urlencode "dateRange=THIS_MONTH" \
  "https://tiktok.fetcher.sh/api/post/search"

Posted yesterday, most recent first:

curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  --data-urlencode "keyword=crypto payments" -G \
  --data-urlencode "sortType=DATE_POSTED" \
  --data-urlencode "dateRange=YESTERDAY" \
  "https://tiktok.fetcher.sh/api/post/search"

Other sortType values: RELEVANCE. Other dateRange values: ALL_TIME, THIS_WEEK, LAST_THREE_MONTHS, LAST_SIX_MONTHS.

Look up a post by its share URL, or directly by ID:

curl -H "Authorization: Bearer $FETCHER_API_KEY" -G \
  --data-urlencode "url=https://www.tiktok.com/@username/video/1234567890123456789" \
  "https://tiktok.fetcher.sh/api/post"

curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://tiktok.fetcher.sh/api/post/1234567890123456789"

A post's comments and comment replies:

curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://tiktok.fetcher.sh/api/post/1234567890123456789/comments"

curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://tiktok.fetcher.sh/api/post/1234567890123456789/comments/9876543210/replies"

A profile by @handle, then its posts, followers, and followings:

curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://tiktok.fetcher.sh/api/user/handle/khaby.lame"

curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://tiktok.fetcher.sh/api/user/6935741396776976390/posts"

curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://tiktok.fetcher.sh/api/user/6935741396776976390/followers"

A hashtag's metadata, then its posts:

curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://tiktok.fetcher.sh/api/hashtag/handle/fyp"

curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://tiktok.fetcher.sh/api/hashtag/1234567890/posts"

Posts using a specific sound, and posts from a location:

curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://tiktok.fetcher.sh/api/music/1234567890123456789/posts"

curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://tiktok.fetcher.sh/api/location/1234567890123456789/posts"

MCP

{
  "mcpServers": {
    "tiktok": {
      "url": "https://tiktok.fetcher.sh/mcp",
      "headers": { "Authorization": "Bearer bby_live_..." }
    }
  }
}

Free: search_endpoints, describe_endpoint, check_balance. Paid: fetch_data (any endpoint above), topup_credits, plus the named shortcut tiktok_post_search. Drop the headers block to pay per call with x402 instead — see the fetcher skill for the full flow.

Errors

  • 400 — missing/invalid parameter (message names it)
  • 401 — unknown or rotated key
  • 402 — payment required (x402 challenge) or topup_required (credits exhausted)
  • 404 — not a priced path
  • No rate limits; no refunds on upstream failures (settlement precedes delivery)

Reference

fetcher-shのその他のスキル

twitter-api
fetcher-sh
fetcher.sh上のTwitter API代替およびX API代替 — x402経由のUSDCによる従量課金、またはBearerキーによるプリペイドクレジット。OAuth不要、開発者アプリケーションも不要。キーワード、ハッシュタグ、または高度な演算子(from:、to:、since:、until:、min_faves:、filter:)によるツイート検索、ハンドルによるTwitter/Xプロフィールのスクレイピング、ユーザーのツイート、リプライ、フォロワー、フォロー中の取得、リプライやリツイート者を含む単一ツイートの取得、Twitterリストのメンバーやツイートの読み取りを行いたい場合に使用します。
instagram-api
fetcher-sh
fetcher.sh上のInstagram API代替 — x402経由のUSDC従量課金、またはBearerキーによるプリペイドクレジット。ログイン不要、セッションクッキー不要。ユーザーが@ハンドルでInstagramプロフィールを解決したい、キーワードでユーザーを検索したい、プロフィールの投稿、リール、ストーリー、タグ付けされた投稿、フォロワー、フォロー中を取得したい、ショートコードで単一の投稿を調べたい、投稿のコメントを読みたい、ハッシュタグまたはリール限定ハッシュタグフィードの投稿を取得したい、場所から投稿を取得したい、または投稿を取得したい場合に使用します。