SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillslinkfox-tiktok-creator

linkfox-tiktok-creator

Data & analytics

View repository

Updated 10-16 06:23

About this skill

TikTok Creator data

This skill uses LinkFox gateway → Ziniao proxy → TikTok Shop creator (affiliate_creator) open API, providing TikTok affiliate creators' data queries (creator profile, bound shop products, showcase products) and shoppable video affiliate operations (upload, content pre-check, publish, status query). All APIs are listed in references/api.md。

📌 Prerequisites: This skill requires creator access_token (user_type=1）. Please first use linkfox-tiktok-auth with appType=creator to complete creator authorization and obtain accessToken, then pass it in as the ttsAccessToken for this skill's calls.

Core Concepts

  • Call chain: Business requests are uniformly forwarded through the LinkFox gateway's /tiktokShop/developerProxy : pass in appType=creator, the TikTok Shop API's relative path(e.g. affiliate_creator/202508/profiles）、method and the creator token ttsAccessToken; Ziniao automatically injects app_key / timestamp / sign, and passes through TikTok's original response. The creator API's appType must be creator(the script already defaults to this).
  • Creator token：ttsAccessToken is the creator access_token (user_type=1), from linkfox-tiktok-auth（appType=creator). When the token expires, return to that skill to refresh it.
  • Response passthrough: The gateway returns httpStatus / contentType / body, where body is TikTok's original JSON string; the TikTok business layer's success/failure is determined by its code / message .

API Usage

This skill is called through the LinkFox gateway proxy; see references/api.md。

Available Scripts

  • scripts/creator_proxy.py — Generic creator API proxy: calls any listed creator API by path + method + ttsAccessToken .

Listed APIs

Capability Upstream path Method
Get Creator Profile affiliate_creator/202508/profiles GET
Search for products of the shop bound to a creator (Get Shop Products) affiliate_creator/202509/shop_products GET
Creator showcase product list (Get Showcase Products) affiliate_creator/202405/showcases/products GET
Upload shoppable video file (Upload Shoppable Video File, multipart) affiliate_creator/202505/videos/video_files POST
Publish shoppable video (Post Shoppable Video) affiliate_creator/202603/videos POST
Query shoppable video publish status (Get Shoppable Video Status) affiliate_creator/202509/videos/{video_id}/status GET
Shoppable video content pre-check (Pre-check Shoppable Video) affiliate_creator/202511/videos/precheck_task POST
Query video pre-check result (Get Shoppable Video Pre-check Result) affiliate_creator/202511/videos/precheck_tasks/{task_id} GET

⚠️ Including multipart/form-data binary upload APIs (Upload Shoppable Video File) do not use the generic creator_proxy.py, and require a multipart chain; see references/api.md。

Typical orchestration flow

A. Product selection / creator data lookup

  1. Creator profile: Get Creator Profile (API 1)
  2. Products: Get Shop Products (API 2, search shop products by keyword) or Get Showcase Products (API 3, creator showcase/live bag) → get product_id

B. Shoppable video affiliate (full publish chain)

  1. Upload video: Upload Shoppable Video File (API 4) → get file_id(⚠️ multipart, see limitations)
  2. Content pre-check: Pre-check Shoppable Video (API 7, pass file_id + product_id) → get task_id
  3. Check pre-check result: Get Shoppable Video Pre-check Result (API 8, with task_id）→ result=SUCCESS only then continue;FAIL see issues[] to fix
  4. Publish: Post Shoppable Video (API 5, pass file_id + product_id + title/cover) → get video.id
  5. Check publish status: Get Shoppable Video Status (API 6, with video_id）→ post_status is SUCCESS/FAIL/PROCESSING

All calls must first go through linkfox-tiktok-auth（appType=creator) to get the creator's accessToken as ttsAccessToken。

Display Rules

  1. Present data only: Just display the creator profile fields, without subjective evaluation.
  2. Token security: Do not output the full ttsAccessTokenin plaintext; only show a masked version.
  3. Error explanation: On failure, explain the reason based on the TikTok business code / message and gateway httpStatus .
  4. Pre-check: When there is no creator token, first guide the user through linkfox-tiktok-auth（appType=creator) authorization.

Important Limitations

  • Creator token required: All APIs require the user_type=1 creator access_token; the shop (erp) token is not applicable.
  • Creator permissions: The creator must have the corresponding e-commerce (EC)/product selection region permissions, otherwise 16015006 / 16015007 / 16504002 etc. are returned.
  • Rate limiting: Too many requests in a short time will trigger 36009002; please back off and retry.

User Expression & Scenario Quick Reference

Applicable：

User Says Scenario
"Look up this TikTok creator's profile" / "Get TikTok creator profile" Get creator homepage/profile
"Search the products in the creator's shop" / "Get shop products of the creator" Search products in the shop bound to the creator
"See what products are in the creator's showcase" / "Get creator showcase products" Creator showcase product list
"Upload a shoppable video" / "Upload shoppable video" Upload a shoppable video file
"Post a shoppable video / bind the video to a product and publish it" / "Post shoppable video" Post a shoppable video
"Was the video published successfully? / Check the video publish status" / "Get shoppable video status" Check shoppable video publish status
"Check whether the video violates any rules before publishing" / "Pre-check shoppable video" Shoppable video content pre-check
"Is the pre-check result out? / Video violation check result" / "Get video pre-check result" Check video pre-check result
"Take a look at the creator's sales information" Creator data query (by included APIs)

Not applicable：

  • TikTok creator authorization itself → use linkfox-tiktok-auth（appType=creator）。
  • TikTok product selection / product sales (data sources such as EchoTik) → handled by the corresponding skill.

Feedback：

When any of the following occurs, automatically report feedback via the Feedback API:

  1. The functionality described by this skill does not match its actual behavior
  2. The skill's result does not match the user's intent
  3. The user expresses dissatisfaction with or appreciation for this skill
  4. Anything you think can be improved

According to references/api.md Call the Feedback API according to the specification in , without interrupting the user's main flow.

Handling Large Responses

To avoid overflowing the agent context, persist the response to disk and extract only the fields you need:

python scripts/response_io.py run --script scripts/creator_proxy.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>"   # or --path "<JMESPath>"

Pick --out-dir outside any git working tree (e.g. /tmp/... on Unix, %TEMP%/... on Windows). Persisted responses may contain PII, pricing, or auth-sensitive data — do not commit them. Files are not auto-deleted; clean up when the task is done.

run writes the full response to a file and emits only a schema preview + file path. read projects specific fields, with --limit/--offset for slicing and --format json|jsonl|csv|table for output.

When to prefer this pattern — apply your judgment based on the response characteristics, e.g.:

  • High field count per record, or fields you don't need
  • Batch/paginated results (multiple items per call)
  • Long-text fields (descriptions, reviews, HTML, time series)
  • Output reused across later steps rather than consumed immediately

For small, single-use responses, calling the main script directly is fine.

⚠️ The preview is a truncated schema + sample, not the full data. Any field-level decision must read from the persisted file via read.

For more high-quality, professional cross-border e-commerce skills, visit LinkFox Skills.